If you do make any changes, cycle through each of the above steps again until you click Install. Wait for the installation to finish, then you will be brought to the completion page. Click Finish to complete Thunderbird’s installation. Setting up Thunderbird. Thunderbird should launch by itself. Installing on Windows. This section tells you how to install, change the home directory, and uninstall on Windows. Using PGP Command Line and PGP Desktop on the same system. PGP Command Line and PGP Desktop can be installed on the same system at the same time.
- Another easy way to get Git installed is by installing GitHub Desktop. The installer includes a command line version of Git as well as the GUI. It also works well with PowerShell, and sets up solid credential caching and sane CRLF settings. We’ll learn more about those things a little later, but suffice it to say they’re things you want.
- At least for Ubuntu 18.04, now, and for me: (1) The gnupg2 package wasn't available, (2) the command in the answer reported However the following packages replace it: gpgv gpgsm gnupg-l10n gnupg dirmngr, and (3) sudo apt-get install gpgv gpgsm gnupg-l10n gnupg dirmngr reported that all those packages were already current. Perhaps they came with my Ubuntu image.
Active4 months ago
I installed Git for Windows including Git Bash on Windows 10 and Gpg4win. By default, I had to re-import all keys I created via Kleopatra into the GPG version built into the Git Bash, and it won't allow me to setup an agent. What I need to do is to automate singing such that I don't need to enter the password every single time, but rather only the first time in a given period of time. How is that possible?
I tried to follow this tutorial, but gpg2 does not use the correct charset when executed from within Git Bash, so it does not recognize keys which contain non-ASCII characters.
Is there any way to solve this problem? What is the best way to use PGP signing with Git on Windows?
just.mejust.me61311 gold badge66 silver badges1919 bronze badges
2 Answers
Update Oct. 2018, as commented below by PHPirate:
No trace of that update in
git-for-windows/git/releases
Original answer (2017):By default, Git for Windows includes a gpg1, not gpg2
Using a different gpg is indeed recommended:
Try again with the latest Git for Windows with UTF-8 set in locale.
Try a Git simplified path to rule out any interference from other programs.
VonCVonCTry a Git simplified path to rule out any interference from other programs.
896k330330 gold badges29132913 silver badges35033503 bronze badges
Since (at least) git 2.19.1, git includes gpg2!
That means you are not required to install gpg4win anymore just for git signing.You ask how to setup commit signing such that you only have to enter your passphrase after a certain timeout:
gpg-agent
can handle that, and I tested that it works with git's gpg (but not with gnupg's gpg). Although it doesn't always work for me, it should work in general. Below is a short summary of the full instructions I have written down here, assuming you have signing set up:
Gpg Download For Windows
- Make sure you are using git's gpg
- Update the cache time, in
C:Usersusername.gnupggpg-agent.conf
(create the file if it doesn't exist), adddefault-cache-ttl 34560000
andmax-cache-ttl 34560000
. These times are in seconds, choose whatever you want. - Restart gpg-agent using
gpgconf --kill gpg-agent
.
Install Gpg For Windows 10
2,33933 gold badges2323 silver badges4747 bronze badges