From: Martin Sebor <msebor@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>,
Overseers mailing list <overseers@sourceware.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation
Date: Mon, 1 Jun 2020 13:14:26 -0600 [thread overview]
Message-ID: <74ac89cb-31b7-770b-0e2a-c1256db64db1@gmail.com> (raw)
In-Reply-To: <20200601181037.GB16575@redhat.com>
On 6/1/20 12:10 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> git pull from the GCC and Glibc repos is failing for me with the error
>> below. It worked fine last week and I haven't made any changes to my
>> ssh keys.
>
> And are you logging in from the same workstation with access to the same
> set of ssh private keys?
Yes.
>
>> Is this a transient glitch or has something changed recently that I
>> need to make some adjustments for?
>
> I know of nothing relevant that has changed on the sourceware side.
>
>> sign_and_send_pubkey: signing failed: agent refused operation
>> msebor@gcc.gnu.org: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>
> The usual advice is to run % ssh -vv gcc.gnu.org alive
> and report the ssh level error.
>
> "agent refused operation" sounds like a problem on the client end.
Until last week, when I ran git pull from the GCC or Glibc repo
I'd get prompted for my password. I'd either type it in or hit
ctrl-C, enter ssh-add, and start over.
After deleting ~/.ssh/known_hosts to resolve the problem I asked
about last week (Re: ssh key conflicts), I'm no longer prompted
for my password. Instead, I get the error above.
Both of this is new (I think since the recent server changes). Now
that I've seen it and know what to expect I can adjust to it but it
seems like things have gotten worse. Certainly the errors I got
in both instances (i.e., last week as well as today) are not helpful.
I captured the ssh -vv gcc.gnu.org output below for a successful
invocation and a failed one if that sheds more light on why it's
failing in (to me) a mysterious way.
Successful authentication:
debug1: Will attempt key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
debug1: Will attempt key: /home/msebor/.ssh/id_ecdsa
debug1: Will attempt key: /home/msebor/.ssh/id_ed25519
debug1: Will attempt key: /home/msebor/.ssh/id_xmss
debug2: pubkey_prepare: done
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info:
server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
debug1: Authentication succeeded (publickey).
Authenticated to gcc.gnu.org ([8.43.85.97]:22).
Failed authentication (after ssh-add -D):
debug1: Will attempt key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
debug1: Will attempt key: /home/msebor/.ssh/id_ecdsa
debug1: Will attempt key: /home/msebor/.ssh/id_ed25519
debug1: Will attempt key: /home/msebor/.ssh/id_xmss
debug2: pubkey_prepare: done
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info:
server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: /home/msebor/.ssh/id_rsa RSA
SHA256:law7uJ+wmAP4krZHnB0tLJ8M+ySmMCclh7mRB9Dlja4 agent
sign_and_send_pubkey: signing failed: agent refused operation
debug1: Trying private key: /home/msebor/.ssh/id_ecdsa
debug1: Trying private key: /home/msebor/.ssh/id_ed25519
debug1: Trying private key: /home/msebor/.ssh/id_xmss
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
msebor@gcc.gnu.org: Permission denied (publickey).
Martin
next prev parent reply other threads:[~2020-06-01 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 17:43 Martin Sebor
2020-06-01 18:10 ` Frank Ch. Eigler
2020-06-01 19:12 ` Jonathan Wakely
2020-06-02 20:26 ` Martin Sebor
2020-06-02 20:43 ` Jonathan Wakely
2020-06-02 21:52 ` Martin Sebor
2020-06-01 19:14 ` Martin Sebor [this message]
2020-06-01 19:25 ` Jonathan Wakely
2020-06-01 19:46 ` Martin Sebor
2020-06-01 19:53 ` Frank Ch. Eigler
2020-06-01 22:33 ` Martin Sebor
2020-06-02 20:00 ` Jim Wilson
2020-06-01 22:30 ` Jonathan Wakely
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=74ac89cb-31b7-770b-0e2a-c1256db64db1@gmail.com \
--to=msebor@gmail.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@sourceware.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).