Resending with a compressed log file since it ended up way bigger than I expected.
-------- Forwarded Message --------
Subject: Re: GPGME status callback not working for need entropy
Date: Thu, 23 Aug 2018 16:54:13 -0400
From: Jacob Adams <tookm...@gmail.com>
To: gnupg-users@gnupg.org
On 08/22/2018 04:38 AM, Werner Koch wrote:
> On Wed, 1 Aug 2018 21:28, tookm...@gmail.com said:
>> generating a key without enough randomness, the whole application just
>> locks up with no indication of what is happening. Is there anything else
>> I could query to inform the user of what's occurring in this scenario?
>
> You need to install a progress callback. Something like:
I have a progress callback installed but it's not reporting anything.
My progress callback currently looks like this:
def _progress(what, type, current, total, prog):
if what == "primegen":
prog.inc()
else:
_log.info(what+" "+type+" "+current+" "+total)
if prog.gk.redraw:
prog.screen.finish()
prog.screen = newt.Screen()
prog.recreate()
(_log is a Logger that logs to a file, and prog is a progress bar I
setup earlier)
But I don't have anything logged when the application runs out of
entropy. The progress callback is simply not called as far as I can
tell. So I was hoping I could maybe get something out of status, but I
guess not. Any idea why progress wouldn't be called?
I've captured a GPGME debug log from an affected system and attached it
below. It seems _gpgme_io_select is just waiting on some file
descriptor, probably for randomness that never arrives. This same test
system completely locked up on shutdown and had to be forced off. Not
sure if that's related but seems likely.
Thanks,
Jacob
gpgme.log.gz
Description: application/gzip
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
