Description of problem: Please give "ngompa" (= Neal Gompa / Son_Goku) an SVN commit bit/packagers' padawan status. He has completed the assignments as an initiate, and I am his mentor. Reproducible: Steps to Reproduce:
CC: (none) => ngompa13
Hi all! Any news?
Account promoted rmember to add ssh key on identity
Status: NEW => RESOLVEDResolution: (none) => FIXEDCC: (none) => tmb
(In reply to Thomas Backlund from comment #2) > Account promoted > > rmember to add ssh key on identity Thanks!
I added my SSH key to the system, but I remain unable to use svn+ssh protocol. I cannot checkout, import, nor commit anything.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Hi Neal, (In reply to Neal Gompa from comment #4) > I added my SSH key to the system, but I remain unable to use svn+ssh > protocol. I cannot checkout, import, nor commit anything. sorry to hear that - can you paste your SSH log?
Created attachment 7143 [details] ssh -v output
Created attachment 7144 [details] mgarepo co output
I've attached outputs from ssh and mgarepo. I don't know of any other logs to give...
This continues to be a problem. At this point, I've completely stalled on my efforts to complete my work[0] because I have no idea why I can't use svn+ssh protocol... [0]: https://wiki.mageia.org/en/Feature:Add_DNF_as_Alternate_Repository_Manager
Created attachment 7154 [details] ssh -vvv output
Usually it's an issue with our fail2ban being overly zealous and outright banning new SSH users, at least that's how I understand it. Colin has had to unban every other new SSH committer for years, and it's probably still what has to be done here.
CC: (none) => mageia, mageia, pterjanPriority: Normal => High
I'm not so sure about fail2ban here.. debug1: Connecting to svn.mageia.org [212.85.158.147] port 22. debug1: Connection established. Connection is established.. Neal, can you specify exact key and try then? You seem to have a lot of keys there..
CC: (none) => mageia
I only have one key. SSH evaluates for all supported ones, but it returns -1 for all the ones that it doesn't find.
Created attachment 7155 [details] "ssh -vvv -i id_rsa" output Here's what the output looks like when I specify the identity file.
I don't see any log from your user on the server so would need your ip. It seems indeed the problem is likely to be your ip being banned after a few failed attempts.
Found it in older logs: Oct 13 17:12:26 valstar sshd[27919]: Invalid user ngompa from [...] And indeed that IP was banned.
(In reply to Pascal Terjan from comment #16) > Found it in older logs: > > Oct 13 17:12:26 valstar sshd[27919]: Invalid user ngompa from [...] > > And indeed that IP was banned. FYI, see ~/colin/denyhosts-purge-ip to purge IPs from denyhosts. Not sure if there is a better way. Sometimes you need to use hostnames too. We'll hopefully get something a bit more robust and controllable when the new valstar comes up.
Thanks, stopping it *before* removing the line would have saved me some "file was modified since reading it" failed attempts :)
It seems to be working now
Status: REOPENED => RESOLVEDResolution: (none) => FIXED