Is the test svn repository working fine?
Hi, I'm having troubles with non-anonymous check outs: paolo:~/test-svn svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Permission denied (publickey,gssapi-with-mic). svn: Connection closed unexpectedly I have svn1.2.3 and the latest openssh, of course cvs works fine for me. Any hint? Thanks in advance, Paolo.
Re: Is the test svn repository working fine?
Paolo Carlini wrote: ... of course cvs works fine for me. This is not really relevant, however, because uses ssh1... Sorry. Paolo.
Re: Is the test svn repository working fine?
Paolo Carlini wrote: I'm having troubles with non-anonymous check outs: By now I'm pretty sure that it's not (completely, at least) my fault, because I tested my svn+ssh setup with 3-4 servers around the world and all asked a password, as expected. Paolo.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: By now I'm pretty sure that it's not (completely, at least) my fault, because I tested my svn+ssh setup with 3-4 servers around the world and all asked a password, as expected. This is configurable in the ssh server. Ok. I tried using my old-good ssh1 (which I'm usually using for gcc's cvs), setting SVN_SSH, as suggested privately by Daniel. Now what happens is that I'm indeed requested a password, exactly as happens for cvs, but for some reason the usual password which I'm using together with cvs is not ok, keeps asking: paolo:~/test-svn svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Enter passphrase for RSA key '[EMAIL PROTECTED]': Enter passphrase for RSA key '[EMAIL PROTECTED]': ... ... Of course, I would rather prefer using the new openssh4.2p1: if I configure it to use Protocol 1, same behavior... Paolo.
Re: Is the test svn repository working fine?
Paolo Carlini wrote: I tried using my old-good ssh1 (which I'm usually using for gcc's cvs), setting SVN_SSH, as suggested privately by Daniel. Now what happens is that I'm indeed requested a password, exactly as happens for cvs, but for some reason the usual password which I'm using together with cvs is not ok, keeps asking: paolo:~/test-svn svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Enter passphrase for RSA key '[EMAIL PROTECTED]': Enter passphrase for RSA key '[EMAIL PROTECTED]': This is *totally* crazy: if I enter the password *3* times, then it works! If someone is curious and wants more debug info to figure out how this could even be possible, just let me know... Paolo.
Re: Is the test svn repository working fine?
paolo:~/test-svn svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Enter passphrase for RSA key '[EMAIL PROTECTED]': Enter passphrase for RSA key '[EMAIL PROTECTED]': This is *totally* crazy: if I enter the password *3* times, then it works! If someone is curious and wants more debug info to figure out how this could even be possible, just let me know... See previous threads about how svn makes multiple connections to the server, each requiring authorization. Paul
Re: Is the test svn repository working fine?
Paul Brook wrote: See previous threads about how svn makes multiple connections to the server, each requiring authorization. Argh! I glanced briefly over those threads... While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? Thanks, Paolo.
Re: Is the test svn repository working fine?
Paul Brook wrote: paolo:~/test-svn svn co svn+ssh://[EMAIL PROTECTED]/svn/gcc/trunk Enter passphrase for RSA key '[EMAIL PROTECTED]': Enter passphrase for RSA key '[EMAIL PROTECTED]': This is *totally* crazy: if I enter the password *3* times, then it works! If someone is curious and wants more debug info to figure out how this could even be possible, just let me know... See previous threads about how svn makes multiple connections to the server, each requiring authorization. I guess it is the SSH connection caching thing?!? I tought it was for performance not also for finger saving... ;) Paolo.
Re: Is the test svn repository working fine?
On Friday 21 October 2005 15:59, Paolo Carlini wrote: Paul Brook wrote: See previous threads about how svn makes multiple connections to the server, each requiring authorization. Argh! I glanced briefly over those threads... While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? Use ssh-agent(1) and/or ssh connection caching http://gcc.gnu.org/wiki/SSH%20connection%20caching Paul
Re: Is the test svn repository working fine?
On 10/21/05, Paolo Carlini [EMAIL PROTECTED] wrote: Paul Brook wrote: See previous threads about how svn makes multiple connections to the server, each requiring authorization. Argh! I glanced briefly over those threads... While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? Make use of ssh-agent. Richard.
Re: Is the test svn repository working fine?
Paolo Carlini [EMAIL PROTECTED] wrote: See previous threads about how svn makes multiple connections to the server, each requiring authorization. Argh! I glanced briefly over those threads... While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? http://gcc.gnu.org/wiki/SSH%20connection%20caching -- Giovanni Bajo
Re: Is the test svn repository working fine?
See previous threads about how svn makes multiple connections to the server, each requiring authorization. I guess it is the SSH connection caching thing?!? I tought it was for performance not also for finger saving... ;) I think it's configurable via the ControlMaster option. The default is to allow secondary connections without asking for a password. Paul
Re: Is the test svn repository working fine?
Paolo Carlini [EMAIL PROTECTED] wrote: While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? http://gcc.gnu.org/wiki/SSH%20connection%20caching Ok. The only problem is that, for some reason, I can use only Protocol 1, not Protocol 2. Anyone knows why? Maybe I have to send to the overseers a new public key? Probably. I can never remember which is which, so I always provide both the keys (generated with -tdsa and -trsa option of ssh-keygen). BTW: I just simplified that Wiki page a little. -- Giovanni Bajo
Re: Is the test svn repository working fine?
Giovanni Bajo wrote: Ok. The only problem is that, for some reason, I can use only Protocol 1, not Protocol 2. Anyone knows why? Maybe I have to send to the overseers a new public key? Probably. I can never remember which is which, so I always provide both the keys (generated with -tdsa and -trsa option of ssh-keygen). Ok, just sent to overseers both, as you suggest, generated with openssh4.2p1. BTW: I just simplified that Wiki page a little. Thanks. To my best knowledge, at least 'til a couple of years ago, many people accessed gcc's cvs with Protocol 1, and now have to upgrade to use subversion at its best. Paolo.
Re: Is the test svn repository working fine?
Richard Guenther wrote: Argh! I glanced briefly over those threads... While you are at it, are you willing to summarize the solution for this annoyance and/or point me to the relevant subthread? Make use of ssh-agent. By the way, time ago, while becoming acquainted with ssh, I read about ssh-agent but decided not to use it: usually I don't like too much happening automatically ;) and, seriously, having to type a password gives me one more chance to stop a commit and avoid mistakes. But now, with svn, something is definitely necessary, and the best solution seems in fact Protocol 2 + connection caching... I'm waiting for overseers to install my new rsa and dsa Protocol 2 public keys... Paolo.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: Ok, just sent to overseers both, as you suggest, generated with openssh4.2p1. You don't need to generate a new one, just convert your RSA key for protocol 1 with ssh-keyconvert(1) to the format used with protocol 2. Ah! This is *so* nice! Really puzzling, however, that the public one, at gcc, is still ok... Thanks! Paolo.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: You don't need to generate a new one, just convert your RSA key for protocol 1 with ssh-keyconvert(1) to the format used with protocol 2. Sorry, dumb question: are you really sure openssh4.2p1 still installs that utility? I cannot find it... Paolo.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: Sorry, dumb question: are you really sure openssh4.2p1 still installs that utility? I cannot find it... Sorry, I mistyped, it is called ssh-keyconverter. Nope. I think that utility has been removed in the openss3.8 time frame... I can find it, of course, worst case I ask Olaf directly ;) Paolo.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: Note that it is still needed to send your converted public key to overseers@ for installation into your account. Ah, ok, like this makes sense. Then, after all, I can just wait having the new Protocol 2 key installed, no? Paolo.
Re: Is the test svn repository working fine?
Paolo Carlini [EMAIL PROTECTED] writes: Nope. I think that utility has been removed in the openss3.8 time frame... It's still part of openssh 4.1p1. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different.
Re: Is the test svn repository working fine?
Andreas Schwab wrote: Nope. I think that utility has been removed in the openss3.8 time frame... It's still part of openssh 4.1p1. Ah, ok, good to know. Anyway, in the meanwhile my keys have been installed and everything works very well here! Paolo.
