savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] [ 100767 ] Problem with CVS keys


From: nobody
Subject: [Savannah-hackers] [ 100767 ] Problem with CVS keys
Date: Fri, 19 Apr 2002 19:58:08 -0400

Support Request #100767, was updated on 2002-Apr-19 07:23
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=100767&group_id=11

Category: CVS
Status: Open
Priority: 5
Summary: Problem with CVS keys

By: T_E_D_
Date: 2002-Apr-19 18:58

Message:
Logged In: YES 
user_id=6186
Browser: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7) 
Gecko/20011221

Yes, I think that's it too. I noticed right after posting my
last message that ssh was getting the key from identity,
while ssh-keygen was putting it in id_rsa(.pub). Clearly two
different files.

I tried keygen again, but it still wanted to put the key in
id_rsa. However, when I changed the invocation of it to:
ssh-keygen -t rsa1

I got the same output as you, and it went into identity.
I've just updated my key via the web app, so I guess I get
to wait 6 hours to see if that fixes it. :-)

----------------------------------------------------------------------

By: yeupou
Date: 2002-Apr-19 18:44

Message:
Logged In: YES 
user_id=1896
Browser: Mozilla/5.0 Galeon/1.2.0 (X11 ; GNU / Linux 2.4.17 i686 ; fr_FR)

I'm not sure but I think your key is a Protocol 2 key.

In fact, you must create it once there's already a
~/.ssh/config with Protocol 1 as content.
When I type ssh-keygen , it starts with "Generating
public/private rsa1 key pair."

Your output is "Generating public/private rsa key pair." and
according to the others informations, you run a quite
similar software (openssl two, but different versions), so
it let me think that can be the problem.

You should remove the unproper key from your accout, create
a new one (with ~/.ssh/config as you have done), add it.

About the delay  explanation :
http://savannah.gnu.org/docs/?item=Is_there_some_delays_on_update.txt

In fact, you've a bad luck, you've probably changed your key
just after the cron job...

----------------------------------------------------------------------
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=100767&group_id=11



reply via email to

[Prev in Thread] Current Thread [Next in Thread]