@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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 16 2017
May 25 2017
@gniibe , I'm not setting the max-passphrase-option. Currently, my gpg-agent.conf looks like this:
May 24 2017
What do you mean by connection error, @gniibe? I hope the user is not impacted by what you are suggesting.
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
Ok. To reproduce, I believe the key is to establish lots of connections (in my rig around 20) to (possibly different) ssh server(s) (possibly by going through a bastion) within a short timeframe.
Hm, it did not give us the location in the source unfortunately, only
the offset from the top of the function, which the original stack trace
already contains. Maybe the library does not contain debug information.
Depending on how you installed that software, there may be a way to
install the debug symbols too. That would make bug reports much more
helpful. Thanks anyway, maybe the log will help us trace the problem.
In T3027#97654, @justus wrote:Hi @landro, thanks for the stack trace. Could you please try to resolve this frame
4 libgcrypt.20.dylib 0x000000010d8b14d2 openpgp_s2k + 594to a source code location? I believe it can be done this way:
$ atos -o /usr/local/opt/libgcrypt/lib/libgcrypt.20.dylib -arch x86_64 -l 0x10d896000 0x000000010d8b14d2
I tried to reproduce this issue locally but failed.
Here is the output of the log file
May 22 2017
Just retested this with 2.1.21 - unfortunately gpg-agent is still crashing. Se new attached crash log.
Apr 19 2017
I finally got around to test this again - sorry for the long wait. I testet with 2.1.20 - same behaviour as in 2.1.19. Crash report attached.