From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8539 invoked by alias); 18 Jan 2008 15:52:55 -0000 Received: (qmail 8531 invoked by uid 22791); 18 Jan 2008 15:52:55 -0000 X-Spam-Check-By: sourceware.org Received: from virtual.bogons.net (HELO virtual.bogons.net) (193.178.223.136) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jan 2008 15:52:26 +0000 Received: from jifvik.dyndns.org (jifvik.dyndns.org [85.158.45.40]) by virtual.bogons.net (8.10.2+Sun/8.11.2) with ESMTP id m0IFplf05815; Fri, 18 Jan 2008 15:51:47 GMT Received: from [192.168.7.9] (unknown [87.127.20.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jifvik.dyndns.org (Postfix) with ESMTP id 751DF4009; Fri, 18 Jan 2008 15:51:48 +0000 (GMT) Message-ID: <4790CB13.7020000@jifvik.org> Date: Fri, 18 Jan 2008 20:49:00 -0000 From: Jonathan Larmour User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Jan Beulich Cc: overseers@sourceware.org Subject: Re: public/private key change/addition References: <478B682C.76E4.0078.0@novell.com> <478F2CCD.1010402@jifvik.org> <478F5520.76E4.0078.0@novell.com> <20080117160140.GA8879@ednor.casa.cgf.cx> <478F8C0F.76E4.0078.0@novell.com> In-Reply-To: <478F8C0F.76E4.0078.0@novell.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00036.txt.bz2 Jan Beulich wrote: >>>> Christopher Faylor 17.01.08 17:01 >>> >> On Thu, Jan 17, 2008 at 12:16:16PM +0000, Jan Beulich wrote: >>>> I have added the above key in addition to the existing one. Note that your >>>>> ssh connections to sourceware are not intended to provide you with a shell, >>>> if that's what you were expecting - instead they are expected to be used >>>> with cvs/svn/git/hg etc. >>> Yes, I had hoped that I could help myself here rather than having to ask >>> someone to do the addition... >>> >>> It's working fine now, thanks! >> Actually, if you can already access sourceware, you can update your key via: >> >> ssh sourceware.org updatekey < key > > Which would replace or add the new key? Is this documented somewhere > that I have missed? It would replace. It's documented on the GCC project's pages, but if it's documented for sourceware then I don't know where. I'm not sure where I'd document it even if I wanted to. For now, I'll add it to the new user instructions I think. Jifl -- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine