In short, you need to put the GPG key with the correct extension into a separate directory that is not searched by default, and point your repository configuration at that specific file. For more info on why you need a separate directory, see this answer to “Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d … Read more
default-cache-ttl max-cache-ttl This is the correct way to do this. The default timeout there is 10 minutes so if there are more then 10 minutes between your commits you would have to extend the time. C:\Users\SashaChernykh.gnupg\gpg-agent.conf This is not the correct path. This would be the path on a GNU/Linux system. The Home directory for … Read more
Commands run with sudo will be run as root. What you want to do is to own the files as your user dylan, right? Maybe so happens that root is owning your files now. This can be changed by: sudo chown -R dylan ~dylan/.gnupg and then as dylan: chmod 600 ~/.gnupg/gpg.conf chmod 700 ~/.gnupg To … Read more
Update Oct. 2018, as commented below by PHPirate: λ git –version git version 2.19.1.windows.1 λ gpg –version gpg (GnuPG) 2.2.9-unknown libgcrypt 1.8.3 Copyright (C) 2018 Free Software Foundation, Inc. No trace of that update in git-for-windows/git/releases Original answer (2017): By default, Git for Windows includes a gpg1, not gpg2 vonc@bvonc MINGW64 ~/.ssh $ gpg –version … Read more
After a lot of digging I found this command which disables the entry prompt on windows(works also for *nix systems): –pinentry-mode=loopback The full command would be: gpg –pinentry-mode=loopback –passphrase “PASSWORD” -d -o “PATH\TO\OUTPUT” “PATH\TO\FILE.gpg”
In order to use the gpg option –passphrase-fd in GnuPG v2, you must specify the –batch parameter. I will first explain how –passphrase-fd works, and then get to the examples. –passphrase-fd tells GnuPG which file descriptor (-fd) to expect the passphrase to come from. The standard file descriptors are STDIN (0), STDOUT (1) and STDERR … Read more
No, it isn’t necessary to keep it private. The secret key is not in git’s configs but in the GnuPG’s “keyring”, which is usually some file in your HOME. In theory it can also be in more secure locations, like hardware token, but I don’t know much about it. The value in git config only … Read more
If gpg –list-keys returns nothing, gpg –generate-key solves the problem.
I had the similar thing. I had the gpg and gpg2 binaries, both pointing to GPG version 2.0.30. I wasn’t being prompted for my passphrase. In your bash profile (I did it in my .zshrc file) add the following line: export GPG_TTY=$(tty)
You likely aren’t pointing the GPG Program setting (found in SourceTree -> Preferences -> Advanced) at the right bin. If you’re using GPGTools on OS X, it should be /usr/local/MacGPG2/bin. To navigate to the /usr/bin directory in the Open File dialog, click shift + command + g