* Public key update for GCC write access
@ 2006-05-28 19:31 Laurynas Biveinis
2006-05-28 19:37 ` Christopher Faylor
0 siblings, 1 reply; 7+ messages in thread
From: Laurynas Biveinis @ 2006-05-28 19:31 UTC (permalink / raw)
To: overseers; +Cc: dberlin
Hi,
I'd like to update my existing sourceware account (user name: lauras)
for GCC write access. Below is my current public key, any old keys
uploaded by me should be disregarded now.
TIA,
Laurynas
ssh-dss AAAAB3NzaC1kc3MAAACBAMWjIaPkkDg0B9bxN2ThdwqSxazA7JIWqhGG9IFSpKPfcDJ1VXZvyVPNuH0pLvI6r8ydFtiHUetac3czhZCFSS5edj5mIOtIzU5DJHOmWV58RubXleK2iCagtlNdzhstvHgJQIwCk6dXPbg2nPGNYLMoAXa8IrEpnYB9EimEUeaZAAAAFQCDnJ4dWtfjXTsDYyPduQWud5HezwAAAIARL0C7oCa4EP+G7amZz9yA89CWNfCxhqCK4HbUiIDUSQ33RsoEO30MVRUNdFXxMrQGUBIcrfdGehoklbLvSuVOX+GVP/A/vDb50eBrCXA41k7Es1aA/rs62/DVtGHb7JDRS9If0NShf1/zSGWi5H7rAdmbS/+U4fXETPtvMoDMkgAAAIB7c26vcwBBpMnrudhcC4VSUNhdotA0lanbJxV3bKrXGK0W3E/0mNZZn68tZt9EhTIaL31l7XHcX8AjAa7cdcTZj+WA38RlPj9oubHmyf7xcNmc/aSrHSQXTqlLFL4jDyZXYDtCelKHUN7xnL64FswJvDQiTHMwryEqcNnp5mtpiA==
imported-openssh-key
---------- Forwarded message ----------
From: Daniel Berlin <dberlin@dberlin.org>
Date: 2006.5.28 21.03
Subject: Re: Branches for you guys in the gcc repository
To: Laurynas Biveinis <laurynas.biveinis@gmail.com>
> I had GCC CVS write access a few years ago. Since that time I've
> changed my public key, so I cannot use it now (user name: lauras).
> Basically now I should provide my current public key, shouldn't I?
Yes, contact overseers with it, and it'll get done :).
--
Laurynas
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 19:31 Public key update for GCC write access Laurynas Biveinis
@ 2006-05-28 19:37 ` Christopher Faylor
2006-05-28 20:22 ` Laurynas Biveinis
0 siblings, 1 reply; 7+ messages in thread
From: Christopher Faylor @ 2006-05-28 19:37 UTC (permalink / raw)
To: overseers, Laurynas Biveinis, dberlin
On Sun, May 28, 2006 at 09:31:28PM +0200, Laurynas Biveinis wrote:
>Hi,
>
>I'd like to update my existing sourceware account (user name: lauras)
>for GCC write access. Below is my current public key, any old keys
>uploaded by me should be disregarded now.
>
>TIA,
>Laurynas
>
>ssh-dss
>AAAAB3NzaC1kc3MAAACBAMWjIaPkkDg0B9bxN2ThdwqSxazA7JIWqhGG9IFSpKPfcDJ1VXZvyVPNuH0pLvI6r8ydFtiHUetac3czhZCFSS5edj5mIOtIzU5DJHOmWV58RubXleK2iCagtlNdzhstvHgJQIwCk6dXPbg2nPGNYLMoAXa8IrEpnYB9EimEUeaZAAAAFQCDnJ4dWtfjXTsDYyPduQWud5HezwAAAIARL0C7oCa4EP+G7amZz9yA89CWNfCxhqCK4HbUiIDUSQ33RsoEO30MVRUNdFXxMrQGUBIcrfdGehoklbLvSuVOX+GVP/A/vDb50eBrCXA41k7Es1aA/rs62/DVtGHb7JDRS9If0NShf1/zSGWi5H7rAdmbS/+U4fXETPtvMoDMkgAAAIB7c26vcwBBpMnrudhcC4VSUNhdotA0lanbJxV3bKrXGK0W3E/0mNZZn68tZt9EhTIaL31l7XHcX8AjAa7cdcTZj+WA38RlPj9oubHmyf7xcNmc/aSrHSQXTqlLFL4jDyZXYDtCelKHUN7xnL64FswJvDQiTHMwryEqcNnp5mtpiA==
>imported-openssh-key
Dan's advice notwithstanding, if you still can use your old key, you can
update yourself to a new key using the instructions here:
http://gcc.gnu.org/wiki/SSH%20connection%20caching
See the "Note for old-time GCC hackers".
cgf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 19:37 ` Christopher Faylor
@ 2006-05-28 20:22 ` Laurynas Biveinis
2006-05-28 20:33 ` Christopher Faylor
0 siblings, 1 reply; 7+ messages in thread
From: Laurynas Biveinis @ 2006-05-28 20:22 UTC (permalink / raw)
To: overseers, berlin
> Dan's advice notwithstanding, if you still can use your old key, you can
> update yourself to a new key using the instructions here:
>
> http://gcc.gnu.org/wiki/SSH%20connection%20caching
>
> See the "Note for old-time GCC hackers".
I've tried this, but apparently the keys I have are not old enough, so
it didn't work...
--
Thanks,
Laurynas
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 20:22 ` Laurynas Biveinis
@ 2006-05-28 20:33 ` Christopher Faylor
2006-05-28 20:35 ` Christopher Faylor
2006-05-28 20:40 ` Laurynas Biveinis
0 siblings, 2 replies; 7+ messages in thread
From: Christopher Faylor @ 2006-05-28 20:33 UTC (permalink / raw)
To: overseers, Laurynas Biveinis, berlin
On Sun, May 28, 2006 at 10:22:24PM +0200, Laurynas Biveinis wrote:
>>Dan's advice notwithstanding, if you still can use your old key, you can
>>update yourself to a new key using the instructions here:
>>
>>http://gcc.gnu.org/wiki/SSH%20connection%20caching
>>
>>See the "Note for old-time GCC hackers".
>
>I've tried this, but apparently the keys I have are not old enough, so
>it didn't work...
The age of the key does not matter.
What was the error you received?
cgf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 20:33 ` Christopher Faylor
@ 2006-05-28 20:35 ` Christopher Faylor
2006-05-28 20:46 ` Laurynas Biveinis
2006-05-28 20:40 ` Laurynas Biveinis
1 sibling, 1 reply; 7+ messages in thread
From: Christopher Faylor @ 2006-05-28 20:35 UTC (permalink / raw)
To: Laurynas Biveinis, overseers, berlin
On Sun, May 28, 2006 at 04:33:50PM -0400, Christopher Faylor wrote:
>On Sun, May 28, 2006 at 10:22:24PM +0200, Laurynas Biveinis wrote:
>>>Dan's advice notwithstanding, if you still can use your old key, you can
>>>update yourself to a new key using the instructions here:
>>>
>>>http://gcc.gnu.org/wiki/SSH%20connection%20caching
>>>
>>>See the "Note for old-time GCC hackers".
>>
>>I've tried this, but apparently the keys I have are not old enough, so
>>it didn't work...
>
>The age of the key does not matter.
>
>What was the error you received?
And, actually, the key that you want to use is already in your authorized_keys
file.
cgf
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 20:33 ` Christopher Faylor
2006-05-28 20:35 ` Christopher Faylor
@ 2006-05-28 20:40 ` Laurynas Biveinis
1 sibling, 0 replies; 7+ messages in thread
From: Laurynas Biveinis @ 2006-05-28 20:40 UTC (permalink / raw)
To: overseers, Laurynas Biveinis, berlin
> >I've tried this, but apparently the keys I have are not old enough, so
> >it didn't work...
>
> The age of the key does not matter.
I should have been more clear: I have lost my old keys due to HDD
crash some time after their first upload to gcc.gnu.org few years ago.
> What was the error you received?
Cygwin's SSH and PuTTY, when configured to use this key and
authenticate with protocol version 1, go to the keyboard-interactive
authorization mode.
--
Laurynas
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Public key update for GCC write access
2006-05-28 20:35 ` Christopher Faylor
@ 2006-05-28 20:46 ` Laurynas Biveinis
0 siblings, 0 replies; 7+ messages in thread
From: Laurynas Biveinis @ 2006-05-28 20:46 UTC (permalink / raw)
To: overseers, dberlin, me
2006/5/28, Christopher Faylor <me@cgf.cx>:
> And, actually, the key that you want to use is already in your authorized_keys
> file.
Oh... It really is, and my authenticated SVN checkout is under way now.
I'm sorry for wasting your time.
--
Laurynas
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-05-28 20:46 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-28 19:31 Public key update for GCC write access Laurynas Biveinis
2006-05-28 19:37 ` Christopher Faylor
2006-05-28 20:22 ` Laurynas Biveinis
2006-05-28 20:33 ` Christopher Faylor
2006-05-28 20:35 ` Christopher Faylor
2006-05-28 20:46 ` Laurynas Biveinis
2006-05-28 20:40 ` Laurynas Biveinis
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).