[Savannah-hackers] [support #103370] more details on CVS developer access failure

[Michael J. Flickinger]

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

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

Changes by: 
                Michael J. Flickinger <address@hidden>
'Date: 
                Thu 09/16/2004 at 21:31 (America/New_York)

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


------------------ Additional Follow-up Comments ----------------------------
This should work now for you, the problem was server-related.

Let us know if this works for you.






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

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103370>
Project: Savannah Administration
Submitted by: Paul Eggert
On: Wed 09/15/2004 at 03:40

Category:  Developer CVS
Priority:  5 - Normal
Severity:  7 - Major
Resolution:  Done
Privacy:  Public
Assigned to:  mjflick
Originator Email:  address@hidden
Status:  Open


Summary:  more details on CVS developer access failure

Original Submission:  CVS developer access is still not working, for me and I 
believe for others. I verified that my ~/.ssh/id_rsa.pub matches the first key 
listed in my account (neither has changed for some time). When I enable ssh 
debugging, things work fine until here:

debug1: authentications that can continue: 
publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try pubkey: /home/eggert/.ssh/id_rsa
debug1: authentications that can continue: 
publickey,password,keyboard-interactive
debug1: try privkey: /home/eggert/.ssh/id_dsa
debug1: next auth method to try is keyboard-interactive

which means that my id_dsa was not accepted by Savannah.

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


-------------------------------------------------------
Date: Thu 09/16/2004 at 21:31       By: Michael J. Flickinger <mjflick>
This should work now for you, the problem was server-related.

Let us know if this works for you.












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

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