GPG slows git commit
erikrtn at gmail.com
Tue Apr 6 18:44:39 CEST 2021
Thank you for the response.
If I run the same command again, I am prompted to enter my passphrase. Subsequently, I get:
gpg: using "581F6A88B3F58A4E94A26040153F263741C51DC1" as default secret key for signing
-----BEGIN PGP SIGNED MESSAGE-----
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
-----END PGP SIGNATURE-----
gpg --clearsign 0.01s user 0.02s system 0% cpu 7.230 total
Note I am on macOS 11.2.3 and zsh 5.8.
Regarding your other suggestions, I don't have a command called "log-file". Is the full suggested syntax "log-file /somewhere/gpg.log"?
Sorry if I'm missing obvious things here.
> On Mar 27, 2021, at 5:01 PM, Ingo Klöcker <kloecker at kde.org> wrote:
> On Freitag, 26. März 2021 15:16:15 CET Erik Reinertsen via Gnupg-users wrote:
>>> Moreover, let's time gpg signing without git. Run
>>> echo Hello | time gpg --clearsign
>> gpg --clearsign 0.01s user 0.01s system 0% cpu 6.696 total
> I'm not sure that I understand the result. (The time command on my system has
> a different output format.) Does the "6.696 total" mean that clearsigning took
> almost 7 seconds? gpg didn't ask you for your passphrase, right?
> Try putting
> log-file /somewhere/gpg.log
> debug ipc,lookup
> into ~/.gnupg/gpg.conf
> Then make a signed test commit and check the log file.
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
More information about the Gnupg-users