public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Martin Sebor <msebor@gmail.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	gcc mailing list <gcc@gcc.gnu.org>,
	 Overseers mailing list <overseers@sourceware.org>
Subject: Re: sign_and_send_pubkey: signing failed: agent refused operation
Date: Tue, 2 Jun 2020 13:00:09 -0700	[thread overview]
Message-ID: <CAFyWVabSPePmsy6zuDqTeTiXdYOyapLYBGPSNcBdWmow4+VpFg@mail.gmail.com> (raw)
In-Reply-To: <b12a4208-4547-3262-70ea-67462900e089@gmail.com>

On Mon, Jun 1, 2020 at 3:33 PM Martin Sebor via Gcc <gcc@gcc.gnu.org> wrote:
> 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:

My experience with Ubuntu 18.04 is that 2K bit keys aren't accepted by
something (gnome UI?) anymore.  I had to upgrade to 4K bit keys.
Though oddly ssh-keygen still generates 2K bit keys by default even
though they won't be accepted by the gnome UI (or whatever).  The work
around is to run ssh-add manually to register your 2K bit key, because
ssh-add will still accept 2K bit keys, and then ssh will work, and can
be used to install a 4K bit public key on the other side, and then
things will work normally again.  A web search suggested that there
was some security problem with 2K bit keys and apparently they are
trying to force people to upgrade, but the inconsistent approach here
between different packages makes this confusing as to what is actually
going on.

Jim

  reply	other threads:[~2020-06-02 20:00 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
2020-06-02 20:00             ` Jim Wilson [this message]
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=CAFyWVabSPePmsy6zuDqTeTiXdYOyapLYBGPSNcBdWmow4+VpFg@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=fche@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --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).