gpg: 跳过 "N": 无法使用私钥

Question

gpg: 跳过 "N": 无法使用私钥

gitgnupg

29

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：

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: SashaChernykhEmpressOfTheUniverse@kristinita.ru
Comment: gpg key for Sasha Chernykh
You selected this USER-ID:
    "Sasha Chernykh (gpg key for Sasha Chernykh) <SashaChernykhEmpressOfTheUniverse@kristinita.ru>"

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) <SashaChernykhEmpressOfTheUniverse@kristinita.ru>
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) <SashaChernykhEmpressOfTheUniverse@kristinita.ru>
sub   2048R/95232DD5 2017-02-08

2. GitHub账户

我按照这篇文章和这篇文章中所写的步骤，将我的GPG密钥添加到了GitHub账户中。

GitHub账户

3. 提交(commit)

现在，我尝试向我测试的远程GitHub存储库提交(commit)。

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) <SashaChernykhEmpressOfTheUniverse@kristinita.ru>
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 Enterprise LTSB 64位英文版
git：
版本 2.11.1.windows.1
gpg：
(GnuPG) 2.0.30 (Gpg4win 2.3.3)

- Саша Черных

2个回答

4

在Windows上配置与Git一起使用GPG密钥比在Mac OS或Linux上更难配置。以下是设置方法：

下载并安装 GPG4Win
使用 this GitHub 指南创建一个GPG密钥。
接下来，打开新的Powershell窗口并运行 where.exe gpg 以获取安装有GPG4Win的GPG程序的准确位置。
将前一个命令的输出放入：git config --global gpg.program [PATH_HERE]中（请确保用前一个命令的输出替换“PATH_HERE”）

太好了！现在你已经配置好了GPG密钥并告诉Git使用哪个程序打开它。

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

首先，强制Git对此项目中的所有提交进行签名：git config --local commit.gpgsign true
然后，获取您的GPG密钥的ID：gpg --list-secret-keys --keyid-format LONG。
将上述ID添加到您的Git配置中：git config --local user.signingkey "[GPG_KEY]"，（请确保在上一个命令中用您的GPG密钥的ID替换“GPG_KEY”）

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

- user15079311

网页内容由stack overflow 提供, 点击上面的

可以查看英文原文，
原文链接

- Саша Черных · Accepted Answer

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) <SashaChernykhEmpressOfTheUniverse@kristinita.ru>"
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