savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] [support #103367] Still no cvs access


From: Michael J. Flickinger
Subject: [Savannah-hackers] [support #103367] Still no cvs access
Date: Tue, 14 Sep 2004 15:22:45 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #103367] Latest Modifications:

Changes by: 
                Michael J. Flickinger <address@hidden>
'Date: 
                Tue 09/14/2004 at 19:05 (America/New_York)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | mjflick


------------------ Additional Follow-up Comments ----------------------------
One of Savannah's backend scripts, the one that handles updating user ssh keys 
locally on the server, is not operational (currently it's under repair). Due to 
this, you will not be able to successfully use developer cvs until it's fixed.

We hope to have the backend script fixed ASAP.

We believe this is the source of your problem, if you still are having problems 
with ssh when the backend script is fixed, we will be glad to look into it.






/**************************************************************************/
[support #103367] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103367>
Project: Savannah Administration
Submitted by: Jay Belanger
On: Tue 09/14/2004 at 12:29

Category:  Savannah website
Priority:  5 - Normal
Severity:  1 - None
Resolution:  None
Privacy:  Public
Assigned to:  mjflick
Originator Email:  
Status:  Open


Summary:  Still no cvs access

Original Submission:  
As near as I can tell, cvs is supposed to be working again (I hope
I'm not jumping the gun), but there has been no change for me.
Is there anything I'm doing wrong?

>> Hi,
>>
>> As far as I can tell, I configured my cvs access for savannah
>> properly, but I still can't use cvs.
>> In my ~/.ssh directory, I have a file "config" containing
>>   Protocol 2
>> I typed "ssh-keygen -t dsa" at the prompt, and after entering a
>> passphrase, I get a file
>>   ~/.ssh/id_dsa.pub
>> I logged into savannah and copied the contents of ~/.ssh/id_dsa.pub to
>> https://savannah.gnu.org/account/editsshkeys.php
>> Over an hour later (enough time for the cron job to take effect), I am
>> unable to checkout using cvs.
>>   [~]> cvs -z3 -d address@hidden:/cvsroot/emacs co emacs
>>   address@hidden's password:
>> After entering my passphrase, I got
>>   Permission denied, please try again.
>> It asks for my password rather than a passphrase, so I guess it
>> doesn't like my ssh2 dsa key, but I don't know why.
>> Can anyone help me?
>>
>> Thanks,
>> Jay


Follow-up Comments
------------------


-------------------------------------------------------
Date: Tue 09/14/2004 at 19:05       By: Michael J. Flickinger <mjflick>
One of Savannah's backend scripts, the one that handles updating user ssh keys 
locally on the server, is not operational (currently it's under repair). Due to 
this, you will not be able to successfully use developer cvs until it's fixed.

We hope to have the backend script fixed ASAP.

We believe this is the source of your problem, if you still are having problems 
with ssh when the backend script is fixed, we will be glad to look into it.

-------------------------------------------------------
Date: Tue 09/14/2004 at 17:11       By: Jay Belanger <jpb>
Here's the output of ssh -v:

[~]> ssh -v -l jpb savannah.gnu.org cvs server
OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data /home/belanger/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to savannah.gnu.org [199.232.41.3] port 22.
debug1: Connection established.
debug1: identity file /home/belanger/.ssh/id_rsa type -1
debug1: identity file /home/belanger/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1 
Debian 1:3.4p1-1.woody.3.1
debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'savannah.gnu.org' is known and matches the RSA host key.
debug1: Found key in /home/belanger/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/belanger/.ssh/id_rsa
debug1: Offering public key: /home/belanger/.ssh/id_dsa
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Next authentication method: password
address@hidden's password: 





CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
belanger --AT-- truman --DOT-- edu  | 









For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=103367>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/







reply via email to

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