Re: [Savannah-hackers] subversion.gnu.org SSH confusion

[Jaime E. Villate]

Oops; sorry, in my previous message I was confusing you with Josh Gay, because
you were trying to access Savannah as address@hidden who is not
you.

The key you entered has already been put in place by the Savannah cron
job. what happens is that you are not using the correct username that you
registered in Savannah: "NedTheAlpaca" the correct ssh command you should
issue is:
  ssh -v address@hidden
and not:
  ssh -v address@hidden
(josh is someone else)

Cheers,
Jaime

On Fri, Dec 06, 2002 at 08:35:40AM +0000, Jaime E. Villate wrote:
> On Thu, Dec 05, 2002 at 09:09:45PM -0800, Josh Hoyt wrote:
> > Hi, I'm trying to get started with ssh cvs access to savannah.
> ...
> > debug1: Trying RSA authentication via agent with 'address@hidden'
> > debug1: Server refused our key.
> ...
> > >From my account page, here's my public key, which has been there for 
> > >several hours, so I expect that the cron job would have found it by now.
> > 1024 35
> > 116380040749735065718004911331210658186796097397805817423389901482226362371604402915330530790970464812336552438192090247391601405282099327805666699241667298794011324199334836619230677260157058518729889758811008877183574902400785512878850927066451607972679447203494344842369600773973563094911171192040234640257
> >  address@hidden
> > 
> > Any idea what's happening?
> 
> Hi,
> In your ~/.ssh/authorized_keys I see two keys: one for address@hidden
> and another one for address@hidden, but no key for address@hidden
> That file has not been changed since June 3rd, which means that the cron job
> that updates your keys is not doing its job (perhaps you put a new-line
> character in your key?).
> 
> While I investigate the problem, I have copied manually your address@hidden 
> key.
> You should now have access. Please try it out.
> 
> Cheers,
> Jaime