public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Overseers mailing list <overseers@sourceware.org>,
	"Frank Ch. Eigler" <fche@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation
Date: Tue, 2 Jun 2020 14:26:27 -0600	[thread overview]
Message-ID: <ead72a77-46a4-a3d2-fb86-96df4849601e@gmail.com> (raw)
In-Reply-To: <CAH6eHdQ-W1=pfw0Dp3qdK4yaJy7oDVMfrk==Pvw96vAMpfqc9w@mail.gmail.com>

On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote:
> On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc <gcc@gcc.gnu.org> 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?
>>
>>> 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.
> 
> Yes, it is. "agent" refers to the ssh-agent program.
> 
> Martin, what does 'ssh-add -l' show?
> 
> Is there only one ssh-agent process shown by 'ps -ef | fgrep
> [s]sh-agent'? Does its PID match $SSH_AGENT_PID?
> 
> Another possible cause is that the file permissions are not strict
> enough on the private key, or on the ~/.ssh directory that contains
> it. Key files should be 600 and ~/.ssh should be 700.

We solved the problem over IRC last night so just to close the loop
on it here: it turned out to be caused by Gnome keyring setting
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh.  With the environment
variable undefined I get prompted for the password as expected.

Thank you both again for your help in getting to the bottom of it!

Martin

  reply	other threads:[~2020-06-02 20:26 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 [this message]
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
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=ead72a77-46a4-a3d2-fb86-96df4849601e@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).