public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Martin Sebor <msebor@gmail.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 15:53:01 -0400	[thread overview]
Message-ID: <20200601195301.GC16575@redhat.com> (raw)
In-Reply-To: <fb03dcec-95d8-eda4-729f-3743db896a93@gmail.com>

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.

- FChE


  reply	other threads:[~2020-06-01 19:53 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 [this message]
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=20200601195301.GC16575@redhat.com \
    --to=fche@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=msebor@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).