* replacing an ssh key
@ 2008-04-18 18:29 Craig Silverstein
2008-04-18 18:35 ` Christopher Faylor
0 siblings, 1 reply; 4+ messages in thread
From: Craig Silverstein @ 2008-04-18 18:29 UTC (permalink / raw)
To: overseers
I just recently requested write access to sourceware, but then
accidentally gave my public key that I've lost the passphrase for. (I
don't know why I keep it around.) So I can't use the access I've been
granted. :-(
Can you replace my public key with the one below, which should
actually work?
Thanks!
craig
--cut here--
2048 35 24839553140946261904087187392304126168662403282429546572622368900166427478061753493109090668153752508667122153275855047122312122470138665443436272932481147966586258411710701230859746809160500332128452903813295380416911493991404380201328388971839456041243037620717623576579574488656695197718617858500296066814778307397642550046112063829428930370299548818140566048706967167803387175785079926004177737245047107440494270779870377306927494071464303597249451435935379274930853841502374384652713971676775218994359280087467722424771609313818739940345034684468298900479897417154958714298147800151369136618353816877732955351753 csilvers@meta.corp.google.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: replacing an ssh key
2008-04-18 18:29 replacing an ssh key Craig Silverstein
@ 2008-04-18 18:35 ` Christopher Faylor
2008-04-19 1:46 ` Craig Silverstein
0 siblings, 1 reply; 4+ messages in thread
From: Christopher Faylor @ 2008-04-18 18:35 UTC (permalink / raw)
To: overseers, Craig Silverstein
On Fri, Apr 18, 2008 at 11:29:31AM -0700, Craig Silverstein wrote:
>I just recently requested write access to sourceware, but then
>accidentally gave my public key that I've lost the passphrase for. (I
>don't know why I keep it around.) So I can't use the access I've been
>granted. :-(
>
>Can you replace my public key with the one below, which should
>actually work?
That looks like an sshv1 public key. You should generate a v2 version.
cgf
>--cut here--
>
>2048 35 24839553140946261904087187392304126168662403282429546572622368900166427478061753493109090668153752508667122153275855047122312122470138665443436272932481147966586258411710701230859746809160500332128452903813295380416911493991404380201328388971839456041243037620717623576579574488656695197718617858500296066814778307397642550046112063829428930370299548818140566048706967167803387175785079926004177737245047107440494270779870377306927494071464303597249451435935379274930853841502374384652713971676775218994359280087467722424771609313818739940345034684468298900479897417154958714298147800151369136618353816877732955351753 csilvers@meta.corp.google.com
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: replacing an ssh key
2008-04-18 18:35 ` Christopher Faylor
@ 2008-04-19 1:46 ` Craig Silverstein
2008-04-19 4:23 ` Christopher Faylor
0 siblings, 1 reply; 4+ messages in thread
From: Craig Silverstein @ 2008-04-19 1:46 UTC (permalink / raw)
To: overseers
} That looks like an sshv1 public key. You should generate a v2
} version.
Sure thing -- attached below.
Thanks,
craig
--cut here--
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwHDR0NOF29K/UT6S+ImfD6X0EJHyewUaH1zwF+1DchKHWs6n73JYoEk5IjpoYLA+9qFqeOqXA1aNK2gZLm+ve/lZU8dg0gQt7xOtzJBHSrmTca23a+fOX7Fg/CWgvwyR/j0CkqxK+PfufBGLcoTNfFyb9TUfCKRCC38gIRo46OicpsBdDiGOFBsA0WEHWKC7TN1x7TJlFq7r/HtQhxf1sqN0QdmcXZThXC+7avpw1gaKuQz3qV1G7nOvBcVojgFEK+CKR+zEkObQd70G8vnHEKaGWfrTgrXr2sbpbOxOVMrq8L0ndYD5kH/2iwa8cX/k0QWkywC3Ro6jhWHG8cPwtQ== csilvers@meta.corp.google.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-04-19 4:23 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-04-18 18:29 replacing an ssh key Craig Silverstein
2008-04-18 18:35 ` Christopher Faylor
2008-04-19 1:46 ` Craig Silverstein
2008-04-19 4:23 ` Christopher Faylor
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).