Это сбивало с толку. Я ожидаю, что git не сможет найти gpg.exe без пути. Я видел эти ответы, но не было никакого смысла добавлять путь, но да, это работает таким образом.
зюме
Я не могу начать использовать 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
I установить 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: [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
Я добавляю свой ключ GPG в свою учетную запись GitHub при записи вэтот а такжеэтот статьи.
Теперь я пытаюсь сделать коммит в моем тестовом удаленном репозитории 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
Операционная система и версия:
Windows 10 Enterprise LTSB 64-разрядная версия EN
мерзавец:
версия 2.11.1.windows.1
GPG:
(GnuPG) 2.0.30 (Gpg4win 2.3.3)