gpg：跳过“N”：密钥不可用

Question

1.总结

我无法开始使用Gpg4win。

---

2.预期行为

提交成功。

---

3.实际行为

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git commit -m "[Test] gpg4win"
gpg: skipped "DBA8E7A2": secret key not available
gpg: signing failed: secret key not available
error: gpg failed to sign the data
fatal: failed to write commit object

---

4.重现步骤

1.设置

我安装Gpg4win→我将Gpg4win设置为this和this答案：

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ gpg --list-key
gpg: keyring `C:/Users/SashaChernykh/AppData/Roaming/gnupg/pubring.gpg' created
gpg: C:/Users/SashaChernykh/AppData/Roaming/gnupg/trustdb.gpg: trustdb created

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ gpg --gen-key
gpg (GnuPG) 2.0.30; Copyright (C) 2015 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

gpg: keyring `C:/Users/SashaChernykh/AppData/Roaming/gnupg/secring.gpg' created
Please select what kind of key you want:
   (1) RSA and RSA (default)
   (2) DSA and Elgamal
   (3) DSA (sign only)
   (4) RSA (sign only)
Your selection? 1
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 2048
Requested keysize is 2048 bits
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 0
Key does not expire at all
Is this correct? (y/N) y

GnuPG needs to construct a user ID to identify your key.

Real name: Sasha Chernykh
Email address: [email protected]
Comment: gpg key for Sasha Chernykh
You selected this USER-ID:
    "Sasha Chernykh (gpg key for Sasha Chernykh) <[email protected]>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a Passphrase to protect your secret key.

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: key DBA8E7A2 marked as ultimately trusted
public and secret key created and signed.

gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
pub   2048R/DBA8E7A2 2017-02-08
      Key fingerprint = B4F2 6F1B 876F 980E 1C99  BA16 9A72 4724 DBA8 E7A2
uid       [ultimate] Sasha Chernykh (gpg key for Sasha Chernykh) <[email protected]>
sub   2048R/95232DD5 2017-02-08

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git config --global user.signingkey DBA8E7A2

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ gpg --list-keys
C:/Users/SashaChernykh/AppData/Roaming/gnupg/pubring.gpg
--------------------------------------------------------
pub   2048R/DBA8E7A2 2017-02-08
uid       [ultimate] Sasha Chernykh (gpg key for Sasha Chernykh) <[email protected]>
sub   2048R/95232DD5 2017-02-08

2. GitHub 帐号

我将我的 GPG 密钥添加到我的 GitHub 帐户，如 this 和 this 文章中所述。

3.提交

现在我尝试提交到我的测试远程 GitHub 存储库。

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git add .

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git commit -m "[Test] gpg4win"
gpg: skipped "DBA8E7A2": secret key not available
gpg: signing failed: secret key not available
error: gpg failed to sign the data
fatal: failed to write commit object

我做错了什么？

---

5.没有帮助

长格式的 GPG 密钥，如本文中所写：

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ gpg --list-secret-keys --keyid-format LONG
C:/Users/SashaChernykh/AppData/Roaming/gnupg/secring.gpg
--------------------------------------------------------
sec   2048R/9A724724DBA8E7A2 2017-02-08
uid                          Sasha Chernykh (gpg key for Sasha Chernykh) <[email protected]>
ssb   2048R/7CCD6FC495232DD5 2017-02-08


SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git config --global user.signingkey 9A724724DBA8E7A2

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git commit -m "[Test] gpg4win"
gpg: skipped "9A724724DBA8E7A2": secret key not available
gpg: signing failed: secret key not available
error: gpg failed to sign the data
fatal: failed to write commit object

---

6.环境

操作系统及版本：
Windows 10 企业版 LTSB 64 位 EN
git：
版本 2.11.1.windows.1
gpg：
(GnuPG) 2.0.30 (Gpg4win 2.3.3)

Answer 1

1.示范

---

2.解决方案

我必须在git设置中手动设置gpg2的路径。

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ where gpg2
C:\Program Files (x86)\GNU\GnuPG\pub\gpg2.exe

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git config --global gpg.program "C:/Program Files (x86)/GNU/GnuPG/gpg2.exe"

现在我可以成功提交了：

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git commit -m "[Test] gpg4win"

You need a passphrase to unlock the secret key for
user: "Sasha Chernykh (gpg key for Sasha Chernykh) <[email protected]>"
2048-bit RSA key, ID DBA8E7A2, created 2017-02-08

[master 1321c09] [Test] gpg4win
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 100644 desktop.ini

SashaChernykh@DESKTOP-EEOT0TN D:\SashaGitHub
$ git push
Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 817 bytes | 0 bytes/s, done.
Total 4 (delta 0), reused 0 (delta 0)
To https://github.com/Kristinita/SashaGitHub.git
   a2aec74..1321c09  master -> master

Answer 2

在 Windows 上使用 Git 设置 GPG 密钥可能比在 Mac OS 或 Linux 上更难配置。设置方法如下。

1. 下载并安装GPG4Win

2. 使用this GitHub 指南创建 GPG 密钥。

3. 接下来，打开一个新的Powershell窗口并运行

   where.exe gpg

   以获取使用GPG4Win安装的GPG程序的确切位置。
   

4. 获取上一个命令的输出并将其放入：

   git config --global gpg.program [PATH_HERE]

   ，（确保将“PATH_HERE”替换为上一个命令的输出）。

太棒了！现在您已经配置了 GPG 密钥并告诉 Git 使用什么程序来打开它。

在提交之前，您需要告诉 Git 该项目使用 GPG 密钥进行代码签名。

1. 首先，强制 Git 签署此项目中的所有提交：

   git config --local commit.gpgsign true

2. 然后，获取您的 GPG 密钥的 ID：g

   pg --list-secret-keys --keyid-format LONG

   。
3. 将该 ID 从上面添加到您的 Git 配置中：

   git config --local user.signingkey "[GPG_KEY]"

   ，（确保将“GPG_KEY”替换为上一个命令中 GPG 密钥中的 ID）

现在项目已配置为使用 GPG 密钥来签名代码，您可以像平常一样提交代码！

Answer 3

如果遇到这个问题的话：

GPG 版本不匹配是我的问题。添加：

{ 
...
"gpgProvider": "gpg2",   
"gpgCmd": "/usr/bin/gpg2",
...
}

到

/home/aptly/.aptly.conf

解决了问题。