From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <overseers-return-9699-listarch-overseers=sources.redhat.com@sourceware.org>
Received: (qmail 2991 invoked by alias); 9 Nov 2007 16:52:51 -0000
Received: (qmail 2982 invoked by uid 22791); 9 Nov 2007 16:52:49 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.oarcorp.com (HELO mail.oarcorp.com) (216.186.189.5)
    by sourceware.org (qpsmtpd/0.31) with SMTP; Fri, 09 Nov 2007 16:52:46 +0000
Received: (qmail 1871 invoked by uid 507); 9 Nov 2007 16:52:44 -0000
Received: from 192.168.1.3 by mail.oarcorp.com (envelope-from <joel.sherrill@oarcorp.com>, uid 501) with qmail-scanner-1.25st 
 (spamassassin: 3.1.1. perlscan: 1.25st.  
 Clear:RC:1(192.168.1.3):. 
 Processed in 0.042432 secs); 09 Nov 2007 16:52:44 -0000
X-Qmail-Scanner-Mail-From: joel.sherrill@oarcorp.com via mail.oarcorp.com
X-Qmail-Scanner: 1.25st (Clear:RC:1(192.168.1.3):. Processed in 0.042432 secs Process 1865)
Received: from unknown (HELO ?192.168.1.3?) (192.168.1.3)
  by mail.oarcorp.com with SMTP; 9 Nov 2007 16:52:44 -0000
Message-ID: <4734905A.6030904@oarcorp.com>
Date: Fri, 09 Nov 2007 16:52:00 -0000
From: Joel Sherrill <joel.sherrill@oarcorp.com>
User-Agent: Thunderbird 2.0.0.5 (X11/20070727)
MIME-Version: 1.0
To: Ian Lance Taylor <ian@airs.com>
CC:  overseers@gcc.gnu.org
Subject: Re: joel's key broken
References: <473388DE.6000002@oarcorp.com> <m3bqa3ucb1.fsf@gossamer.airs.com>
In-Reply-To: <m3bqa3ucb1.fsf@gossamer.airs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact overseers-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <overseers.sourceware.org>
List-Archive: <http://sourceware.org/ml/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-help@sourceware.org>,
	<http://sourceware.org/ml/#faqs>
Sender: overseers-owner@sourceware.org
X-SW-Source: 2007-q4/txt/msg00048.txt.bz2

Ian Lance Taylor wrote:
> Joel Sherrill <joel.sherrill@oarcorp.com> writes:
>
>   
>> My key is broken.  I don't know whether I have
>> changed it or just been stupid and forgotten the
>> pass phrase.
>>
>> What is the best way to proceed?  I am happy to
>> generate a new key if you can point me to instructions.
>>     
>
> You can use ssh-keygen to generate a new key.  Then send us the new
> SSH public key.
>   
Is an RSA key OK?  Hopefully this cut and paste worked.

ssh-rsa 
AAAAB3NzaC1yc2EAAAABIwAAAQEAsUhArh5Aq2MMHThbmltjV6hrH8w8/G3RomZUJ3ldiXPmEKGYX1XxBFeZRbXjwDJHf9eI9uceyg8RMag/z41reKFBCWza8P1RWpZ/eWa5hPmJPPV6Ohql1Yt2RvbB480U79to0ojYuWwcadqXfjPx+YnWcwfv9xJAZC2OOTngIml6Vg2E+wlliXEKOXAYpdaVSiAF5ts34RT2wtRaeTyupf5GXcpElfLyPFwrU7w7FXftAE9dBbIy0WNkSHb8rXVWys/D6vHN+qGXmJcaxVk0WsFLh6h4xaG0J9yuP5v4nStR8s7WJCXz0woqVeYwJgQsPrd2m2hdAolhp8iZVRcNRw== 
joel@rtems

Thanks.

--joel
> Ian
>