public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: gpg --gen-key : agent_genkey failed: Timeout
Date: Fri, 2 Dec 2022 11:41:53 -0800	[thread overview]
Message-ID: <d9b6cb7d-ea14-44df-6053-f006afeb087a@jhmg.net> (raw)
In-Reply-To: <cf7bbc53-643b-1113-43c9-2d324adc652c@jhmg.net>

On 12/02/22 11:23, Jim Garrison via Cygwin wrote:
> Fully updated cygwin64 on Win10 Pro x64; cygcheck.out attached.
> 
> If I attempt this in a regular mintty session, it hangs forever (until
> killed with ^C). If I run it in a priviliged session (Run As
> Administrator) it gives the below timeout message after about 90
> seconds.  And yes, I did as suggested: moving the mouse, running
> chkdisk in a CMD box, etc.
> 
> ===================================
> $ gpg --gen-key
> Note: Use "gpg2 --full-generate-key" for a full featured key generation 
> dialog.
> 
> GnuPG needs to construct a user ID to identify your key.
> 
> Real name: Jim Garrison
> Email address: [redacted]
> You selected this USER-ID:
>      "Jim Garrison [redacted]"
> 
> Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
> We need to generate a lot of random bytes. It is a good idea to perform
> some other action (type on the keyboard, move the mouse, utilize the
> disks) during the prime generation; this gives the random number
> generator a better chance to gain enough entropy.
> 
> gpg: agent_genkey failed: Timeout
> Key generation failed: Timeout
> ====================================

Running this on a Debian 10 system completes successfully in < 1 second.

-- 
Jim Garrison
jhg@acm.org


      reply	other threads:[~2022-12-02 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 19:23 Jim Garrison
2022-12-02 19:41 ` Jim Garrison [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9b6cb7d-ea14-44df-6053-f006afeb087a@jhmg.net \
    --to=jhg@jhmg.net \
    --cc=cygwin@cygwin.com \
    --cc=jhg@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).