Bug 6508

Summary: can no longer access svn via ssh
Product: Infrastructure Reporter: andré blais <andr55>
Component: Account requestAssignee: Sysadmin Team <sysadmin-bugs>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: andr999, sysadmin-bugs, thierry.vignaud
Version: unspecified   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: openssl-1.0.0d-2.5.mga1.src.rpm CVE:
Status comment:

Description andré blais 2012-06-19 05:46:20 CEST 
Description of problem:
Account = andre999
I have been assigned apprentice packager status, and svn access via ssh worked at first.
In the last few months, I haven't been able to access svn via ssh.
Although my public key seemed correct, I reloaded it, still unable to access svn via ssh, after waiting at least 30 minutes.  (Maybe a few hours.)
Then I generated a new key and loaded the new public key, same problem, again after waiting at least 30 minutes.  Retried the last several days with the same results.

I used the line suggested in the wiki to test :
  ssh login@svn.mageia.org
and every time it asks me for a password.
(I didn't use a passphrase for my ssh key.)

My private key is appropriately only read/writable by myself.

I have no problem logging into my account directly, and as well as the public key, my email address and other info is correct.

I don't know if this may be related, but I had an email address with a dot in it, and emails were being sent to the address with the dot up to just before the @ removed (which belonged to someone else).  I have since changed to another email address without a dot, which works correctly.

Could someone check that there is no problem server side ?

Thanks
Comment 1 Thierry Vignaud 2012-06-19 15:41:10 CEST 
There was a similar issue yesterday evening (18/06/2012) which delayed me uploading x11-driver-video-nouveau-1.0.0-1.mga3

CC: (none) => thierry.vignaud

Comment 2 andré blais 2013-04-17 07:45:23 CEST 
works now, but forgot to report it ...
The test I used in the ssh wiki gave a false negative
(Probably since I didn't have a passphrase on my ssh key.)
The final test at the end of the wiki page works nicely.

The initial problem could have been a corrupted key, or something transient.
(I ended up regenerating and reloading my ssh key a few times.)

closing

Status: NEW => RESOLVED
CC: (none) => andre999mga
Resolution: (none) => INVALID