Dec 11 2017
I'm seeing something quite similar - same setup, osx and it only shows when using ansible. I'm on gnupg 2.2.3, also saw same using "GPG Suite 2017.2".
Oct 20 2017
This patch was released with 1.4.22
Aug 31 2017
Given no feedback, I'm closing this issue.
If there is still problem, please reopen.
Jul 31 2017
A new installer is now available:
GnuPG 2.1.22 in Homebrew is out: https://github.com/Homebrew/homebrew-core/commit/39a392ffd6ac20a36ea8a4aec5c4dc5febcfc1d6
Please check it out.
Jul 27 2017
Also a lot of redirects, for example this bounces you from https to http.
Jul 26 2017
FWIW, using a Debian specific thing is not portable and Unix sockets won't work on Windows. Thus using the standard localhost connection is simpler than adding extra complexity.
Okay, I implemented the second part and Tor is now used if availabale.
--no-use-tor disables Tor.
--use-tor forces use Tor and can't be reset.
Jul 17 2017
Should be resolved. Reopen if it is still an issue.
Jul 16 2017
@marcus sure, but I am currently away on vacation and won't be back until mid August. Also, I'd need some detailed build instructions (I'm on mac os) since I'm not very familiar with building C code - I brew installed gpg.
Jul 13 2017
It is fine to close this. Reworking the parser is not going to happen anytime soon.
Because werner says he fixed the memory access, I am closing here. werner, if you want to keep track of the invalid encoding issue with the asn.1 parser, please open a new task with some details. pascal, if you find anything missing, please open new tickets (as you said, it's easier to keep track of issues in separate tickets).
Landed in 67cd81ed90ad88cbe607b7f7d1a0b1e08b8ac1f1.
@landro Would you like to do one more round of testing?
Jul 10 2017
We have to check what happens here, because list-sigs should be fast.
Jul 5 2017
It's unclear from the discussion if this issue has been resolved. @werner can you please comment on this?
Jul 3 2017
No I don't recall any such problems, sorry.
Jul 1 2017
Jun 30 2017
Still an issue in gpg 2.1.21.
Jun 28 2017
Jun 27 2017
I'm going to close this task now. If we need more options to be configurable, it is easy to open another task for them.
Jun 23 2017
Libgcrypt 1.6 reaches EOL in 7 days, so we won't fix it.
Jun 2 2017
I released libgcrypt 1.7.7
and nPth 1.6
libgcrypt secmem fix is not that in hurry, I think. nPTh bug for macOS sounds more severe.
Jun 1 2017
So, should we do a new libgcrypt release RSN?
There is another bug with solution also pending and it might not be too late for Squeeze if we hurry.
I managed to replicate this issue by preparing artificial nPth on x86 GNU/Linux.
I fixed a bug in nPth: rPTH4fae99976c31: Fix busy_wait_for.
During this debug, I also found a bug and fixed in libassuan: rA62f3123d3877: Use gpgrt_free to release memory allocated by gpgrt_asprintf.
Also, I fixed two related bug in GnuPG:
rGc03e0eb01dc4: agent: Fix error from do_encryption.
rG996544626ea4: agent: Fix memory leaks.
May 25 2017
@gniibe , I'm not setting the max-passphrase-option. Currently, my gpg-agent.conf looks like this:
@landro , Do you have any key which might require passphrase update for its expiration?
I mean, do you have an gpg-agent option of "max_passphrase_days" set (default is not set).
(Since I was writing by phone, the sentence was terse. Sorry. This time, by PC.)
May 24 2017
What do you mean by connection error, @gniibe? I hope the user is not impacted by what you are suggesting.
For smartcard, yes. The feature for ssh with smartcard has been available more than ten years. I recently apply the approach to gpg frontend.
"landro (Stefan Magnus Landrø)" <firstname.lastname@example.org> writes:
Just noticed one more thing - I'm not trying to use a smartcard at this time (I plan on moving to yubikeys in future though) - why is "new connection to SCdaemon established" all over the logs?
So I'm using pinentry-mac in my gpg-agent.conf:
May 23 2017
So I noticed your log contains lot's of "starting a new PIN Entry", I assume you are using some kind of password manager integration, so that you don't need to enter it each time (sorry, I'm not familiar with how pinentry works on macOS).