ssh keys

ssh keys

[Eric Gallager]

Hello GCC Overseers, it's Eric Gallager here, and I'd like to get back
to committing to the GCC project again. The last time I committed was
back in the SVN days, and it was from a different computer than I
currently use, and I'm afraid my ssh keys from the old computer got
lost in the migration process somehow, so if I'm going to get back to
committing again, I'm going to need to be able to use a new ssh key
(since I haven't been able to find my old one). My "@gcc.gnu.org"
email address is egallager@gcc.gnu.org (it forwards to this address
egall@gwmail.gwu.edu that I'm currently writing from), and I have
mentioned this issue with my keys with that account on Bugzilla, for
example, here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56604
My original sponsor when I first applied for commit access was David
Malcolm, and I still have a copyright assignment on file with the FSF
(which I visited in person to deliver), so you can contact them if
necessary. Also I was asking about this issue on the #gcc IRC channel
on oftc.net, where Iain Sandoe recommended I email the overseers about
it, so he can vouch for me, too.
This is also something I've mentioned on my Twitter account:
https://twitter.com/cooljeanius/status/1413700314398666753?s=21
Let me know if there are any other ways I can verify my identity in
order to get my ssh keys switched, and I apologize for my
scatterbrainedness in letting this situation arise.
Thanks,
Eric Gallager

Re: ssh keys

[Mark Wielaard]

Hi, Eric,

On Sun, 2021-10-10 at 21:46 -0400, Eric Gallager via Overseers wrote:
> Hello GCC Overseers, it's Eric Gallager here, and I'd like to get
> back
> to committing to the GCC project again. The last time I committed was
> back in the SVN days, and it was from a different computer than I
> currently use, and I'm afraid my ssh keys from the old computer got
> lost in the migration process somehow, so if I'm going to get back to
> committing again, I'm going to need to be able to use a new ssh key
> (since I haven't been able to find my old one).
> [...]
> Let me know if there are any other ways I can verify my identity in
> order to get my ssh keys switched, and I apologize for my
> scatterbrainedness in letting this situation arise.

Please sent the ssh pubkey (the ~/.ssh/id_*.pub you are actually using)
and we'll install it for you if you promise to take good care of the
private part.

Cheers,

Mark

Re: ssh keys

[Eric Gallager]

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

ok, attached is my most recent elliptic curve pubkey (id_ed25519.pub);
I should have an easier time keeping track of this one because it's
the only one of its kind I have, unlike the RSA ones, where there are
a bunch to get confused with one another.
Thanks,
Eric Gallager

On Mon, Oct 11, 2021 at 7:48 AM Mark Wielaard <mark@klomp.org> wrote:
>
> Hi, Eric,
>
> On Sun, 2021-10-10 at 21:46 -0400, Eric Gallager via Overseers wrote:
> > Hello GCC Overseers, it's Eric Gallager here, and I'd like to get
> > back
> > to committing to the GCC project again. The last time I committed was
> > back in the SVN days, and it was from a different computer than I
> > currently use, and I'm afraid my ssh keys from the old computer got
> > lost in the migration process somehow, so if I'm going to get back to
> > committing again, I'm going to need to be able to use a new ssh key
> > (since I haven't been able to find my old one).
> > [...]
> > Let me know if there are any other ways I can verify my identity in
> > order to get my ssh keys switched, and I apologize for my
> > scatterbrainedness in letting this situation arise.
>
> Please sent the ssh pubkey (the ~/.ssh/id_*.pub you are actually using)
> and we'll install it for you if you promise to take good care of the
> private part.
>
> Cheers,
>
> Mark

[-- Attachment #2: id_ed25519.pub --]
[-- Type: application/x-mspublisher, Size: 102 bytes --]

Re: ssh keys

[Mark Wielaard]

On Mon, Oct 11, 2021 at 03:38:32PM -0400, Eric Gallager wrote:
> ok, attached is my most recent elliptic curve pubkey (id_ed25519.pub);

Installed. See https://sourceware.org/sourceware/accountinfo.html for
more info how to check it works and how to maintain your account/keys.

Cheers,

Mark

ssh keys

[Moore, Catherine]

[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]

It looks like I can no longer checkout out repositories with write access.
I'm attaching my two public key files (rsa/dsa).  Would you please update them?
Hopefully that will fix the problem, but if not, I'm going to need some help figuring out what's wrong.
Thanks,
Catherine


SVN_SSH="ssh -v" svn co svn+ssh://clm@gcc.gnu.org/svn/gcc/trunk gcc
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/cmoore/.ssh/config
debug1: /home/cmoore/.ssh/config line 4: Applying options for gcc.gnu.org
debug1: /home/cmoore/.ssh/config line 31: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Control socket "/tmp/ssh_clm@gcc.gnu.org:22" does not exist
debug1: Connecting to gcc.gnu.org [209.132.180.131] port 22.
debug1: Connection established.
debug1: identity file /home/cmoore/.ssh/internal_dsa type 2
debug1: identity file /home/cmoore/.ssh/internal_dsa-cert type -1
debug1: identity file /home/cmoore/.ssh/internal_rsa type 1
debug1: identity file /home/cmoore/.ssh/internal_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23
debug1: Host 'gcc.gnu.org' is known and matches the RSA host key.
debug1: Found key in /home/cmoore/.ssh/known_hosts:2
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering DSA public key: /home/cmoore/.ssh/internal_dsa
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /home/cmoore/.ssh/internal_rsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

[-- Attachment #2: internal_dsa.pub --]
[-- Type: application/x-mspublisher, Size: 1524 bytes --]

[-- Attachment #3: internal_rsa.pub --]
[-- Type: application/x-mspublisher, Size: 405 bytes --]

Re: ssh keys

[Frank Ch. Eigler]

Hi -

> It looks like I can no longer checkout out repositories with write access.
> [...]

Your previous pubkey was fine, though old; perhaps the private key
was lost on your side.  Anyway, installed the new rsa one.

- FChE

RE: ssh keys

[Moore, Catherine]

> -----Original Message-----
> From: Frank Ch. Eigler [mailto:fche@elastic.org]
> Sent: Thursday, October 13, 2016 9:05 PM
> To: Moore, Catherine <Catherine_Moore@mentor.com>
> Cc: overseers@gcc.gnu.org
> Subject: Re: ssh keys
> 
> Hi -
> 
> > It looks like I can no longer checkout out repositories with write access.
> > [...]
> 
> Your previous pubkey was fine, though old; perhaps the private key
> was lost on your side.  Anyway, installed the new rsa one.
> 


Thanks, all better now.

ssh keys

[bud davis]

hi,

i have a new computer (again!) and need help getting
svn write access. my account is bdavis@gcc.gnu.org.

tell me how to make a key with ssh-keygen that meets
the needs and i will do it !!!

thanks,
bud davis