Re: Error in 2.3 regarding reader-port (infinite loop)

2021-12-31 Thread Anze Jensterle
I made a PR to fix this: https://dev.gnupg.org/D547. Best, Anze On Thu, Dec 30, 2021 at 3:52 PM Werner Koch wrote: > > I have attached logs of the wrong and correct behavior I observed > > (debug-level guru, debug-all). > > Yes, this is an obvious bug. We have not yet seen it because on Unix

Re: Error in 2.3 regarding reader-port (infinite loop)

2021-12-30 Thread Werner Koch via Gnupg-users
> I have attached logs of the wrong and correct behavior I observed > (debug-level guru, debug-all). Yes, this is an obvious bug. We have not yet seen it because on Unix we prefer to use the CCID driver using a different code path and further with 2.3 there is not much need to specify a port.

Re: Error in 2.3 regarding reader-port (infinite loop)

2021-12-30 Thread Werner Koch via Gnupg-users
On Wed, 29 Dec 2021 14:55, Anze Jensterle said: > I just updated my Windows PC to 2.3. I used the "reader-port" option in Do you mean gnupg 2.3.4 for Windows or the gpg4win 4.0 ? > I have attached logs of the wrong and correct behavior I observed > (debug-level guru, debug-all). Thanks. We

Error in 2.3 regarding reader-port (infinite loop)

2021-12-29 Thread Anze Jensterle
Hey everyone, I just updated my Windows PC to 2.3. I used the "reader-port" option in scdaemon.conf to only use my Yubikey. Since updating I have found that with that option set, the scdaemon goes into an infinite loop when trying to access smart cards (for example Kleopatra hangs whi

Re: Infinite loop?

2019-06-25 Thread Daniel Kahn Gillmor via Gnupg-users
strong set showing where I've been over the years or the local > signatures for "yeah, I grabbed these fingerprints from a web-page, I'll > trust them locally but won't attest to them publicly". If the issue is just a large keyring, i can generate that myself pretty easily, thanks.

Re: Infinite loop?

2019-06-25 Thread Phil Pennock via Gnupg-users
On 2019-06-25 at 18:47 -0400, Daniel Kahn Gillmor via Gnupg-users wrote: > Interesting! my pubring.kbx is 147MiB, but GnuPG still should not run > forever when doing --list-keys. It takes 17s to complete the listing of > my pubring.kbx, as measured by "time gpg --list-keys > /dev/null" With

Re: Infinite loop?

2019-06-25 Thread Daniel Kahn Gillmor via Gnupg-users
On Tue 2019-06-25 12:02:13 -0700, James Moe via Gnupg-users wrote: > On 25/06/2019 8.30 AM, Daniel Kahn Gillmor wrote: > >> Is it possible that your pubring.gpg is corrupt? > > As it happens, yes. > The size of pubring.gpg was 20MB; the backup copy was 1.3MB. After > restoring from backup,

Re: Infinite loop?

2019-06-25 Thread James Moe via Gnupg-users
On 25/06/2019 8.30 AM, Daniel Kahn Gillmor wrote: > Is it possible that your pubring.gpg is corrupt? > As it happens, yes. The size of pubring.gpg was 20MB; the backup copy was 1.3MB. After restoring from backup, gpg2 performs normally. Thank you. -- James Moe moe dot james at sohnen-moe

Re: Infinite loop?

2019-06-25 Thread Daniel Kahn Gillmor via Gnupg-users
On Sun 2019-06-23 15:00:40 -0700, James Moe via Gnupg-users wrote: > On 23/06/2019 11.53 AM, James Moe via Gnupg-users wrote: > >> gnupg does appear in the update log >> > Sigh. Typo. > gnupg does NOT appear in the update log. Nor does libscrypt. Without having access to your pubring.gpg,

Re: Infinite loop?

2019-06-23 Thread James Moe via Gnupg-users
On 23/06/2019 11.53 AM, James Moe via Gnupg-users wrote: > gnupg does appear in the update log > Sigh. Typo. gnupg does NOT appear in the update log. Nor does libscrypt. The repetitive part of the log starts at line 475. -- James Moe moe dot james at sohnen-moe dot com 520.743.3936

Infinite loop?

2019-06-23 Thread James Moe via Gnupg-users
opensuse LEAP 15.0 linux 4.12.14-lp150.12.64-default x86_64 gpg2 seems to enter an infinite loop. The system recently updated; gnupg does appear in the update log. That is all I know. I executed the command $ gpg2 --debug-all --list-keys to get a debug output. The resulting file is really