From: Martin Sebor <msebor@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Overseers mailing list <overseers@sourceware.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation
Date: Mon, 1 Jun 2020 16:33:18 -0600 [thread overview]
Message-ID: <b12a4208-4547-3262-70ea-67462900e089@gmail.com> (raw)
In-Reply-To: <20200601195301.GC16575@redhat.com>
On 6/1/20 1:53 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> ~/.ssh/known_hosts exists and ~/.ssh is rwx only by the owner.
>> Everything works fine if I add my key by running ssh-add. What's
>> not so great is the errors I get when I forget to do that: "agent
>> refused operation?"
>
> Yeah, there is something odd on your side. Maybe your ssh client is
> unable to find the right private key - maybe it's named non-default?
> If so, add it to your .ssh/config
>
> Host gcc.gnu.org sourceware.org
> IdentifyFile ~/.ssh/id_XYZ
>
>> It just feels like too much of a coincidence that I started having
>> these problems only after the recent server upgrade. [...]
>
> I'm afraid it does look like a coincidence.
So it sounds like you wouldn't expect the "agent refused operation"
error either, and it's not just a poor error message that I should
learn to live with. That makes me think I should try to figure out
what's wrong. I think the ~/.ssh/ contents are pretty standard:
$ ls -l ~/.ssh/
total 32
-rw-------. 1 msebor msebor 998 Jan 3 2019 authorized_keys
-rw-------. 1 msebor msebor 1381 Jan 3 2019 id_dsa
-rw-------. 1 msebor msebor 603 Jan 3 2019 id_dsa.pub
-rw-------. 1 msebor msebor 1876 Dec 18 2018 id_rsa
-rw-------. 1 msebor msebor 395 Dec 18 2018 id_rsa.pub
-rw-------. 1 msebor msebor 187 Jun 1 13:41 known_hosts
I'm not a Git or ssh power user so I don't change default settings
unless I absolutely have to. It's also been a while since I updated
my workstation so I can't think of anything that could be behind this.
Do you have any suggestions what else to look at?
Martin
next prev parent reply other threads:[~2020-06-01 22:33 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
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 [this message]
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=b12a4208-4547-3262-70ea-67462900e089@gmail.com \
--to=msebor@gmail.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--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).