public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Vineet Gupta <vineet.gupta@linux.dev>
Subject: Re: Fwd: Fwd: Welcome to sourceware.org
Date: Tue, 29 Nov 2022 11:19:42 +0100	[thread overview]
Message-ID: <Y4Xcvj3ysj61DuNe@wildebeest.org> (raw)
In-Reply-To: <05e065ac-eb5c-2c08-1947-0f1c75940031@linux.dev>

Hi Vineet,

On Mon, Nov 28, 2022 at 05:09:47PM -0800, Vineet Gupta via Overseers wrote:
> Sorry for bothering again with this. I had to reinstall my laptop so my ssh
> key changed.

Note that we now have the private admin-requests@sourceware.org list
for these kind of issues.

> I did backup my old ssh keys and trying to use it to add the new key as
> follows seems to be failing.
> 
> ssh -l vgupta  -i ~/old-keys/id_rsa.pub  sourceware.org appendkey <
> ~/.ssh/id_rsa.pub
> Load key "~/old-keys/id_rsa.pub": error in libcrypto
> vgupta@sourceware.org: Permission denied (publickey).

You need to use your private key with -i:

  -i identity_file
  
     Selects a file from which the identity (private key) for public
     key authentication is read.  The default is ~/.ssh/id_dsa,
     ~/.ssh/id_ecdsa, ~/.ssh/id_ecdsa_sk, ~/.ssh/id_ed25519,
     ~/.ssh/id_ed25519_sk and ~/.ssh/id_rsa.

You are trying to use you public (.pub) key part.

Cheers,

Mark

  parent reply	other threads:[~2022-11-29 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200310183342.35494395A062@sourceware.org>
2022-07-27 20:23 ` Vineet Gupta
2022-07-27 20:35   ` Frank Ch. Eigler
2022-07-27 21:36     ` Vineet Gupta
2022-07-27 21:57       ` Frank Ch. Eigler
2022-07-28  0:38         ` Vineet Gupta
2022-07-28  0:41           ` Frank Ch. Eigler
2022-07-28  0:45             ` Vineet Gupta
     [not found]   ` <05e065ac-eb5c-2c08-1947-0f1c75940031@linux.dev>
2022-11-29 10:19     ` Mark Wielaard [this message]
2022-11-29 19:55       ` Fwd: " Vineet Gupta
2022-11-29 21:49         ` Mark Wielaard

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=Y4Xcvj3ysj61DuNe@wildebeest.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=vineet.gupta@linux.dev \
    /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).