Re: CVS access using SSH

[Sheldon Samuels]

Yes, :ext: is required.  It simply sits and appears to be doing nothing if I remove the :ext:.  I also tried to change CVS_RSH to garbage and then it merely errors out unable to execute the command.   Here is the trace on the CVS command if all is set properly:   C:\WINDOWS>cvs -t co panjasource CVS.EXE checkout: notice: main loop with CVSROOT=:ext:[EMAIL PROTECTED] ource.sourceforge.net:/cvsroot/panjasource  -> Starting server: ssh cvs.panjasource.sourceforge.net -l sheldon_samuels cvs server Password: S-> do_module (panjasource, Updating, , ) You'll notice that it asks for a password.  It does appear to be doing the update thing, but it required that I enter my password first.   If I try to use WinCVS to do the same thing, WinCVS (Ver 1.1b13) just gives me -BASH errors after it creates an interactive session.  (I assume this means that SSH did autologin properly.)  Don't know if this is something that is related or not, but I thought I might mention it.   Thanks. Sheldon Samuels >>> "Noel L Yap" <[EMAIL PROTECTED]> 06/06/00 09:19AM >>> I didn't realize you were running on Windows.  I've noticed that the Windows version of CVS 1.10.8 doesn't use CVS_RSH unless CVSROOT is prefixed by :ext:. To verify that this is the case, try setting CVS_RSH to garbage.  I think this is a bug, but I'm not sure (ie it might've been changed to this behaviour on purpose). Anyway, try prefixing CVSROOT with ":ext:". Noel [EMAIL PROTECTED] on 06/06/2000 10:01:28 AM To:   [EMAIL PROTECTED] cc:   [EMAIL PROTECTED] Subject:  Re: CVS access using SSH Here is the response I get if I type in SSH just like CVS is executing: C:\WINDOWS>ssh cvs.panjasource.sourceforge.net -l sheldon_samuels Password: Last login: Tue Jun  6 06:50:09 2000 from 216.216.209.7 No mail. Welcome to cvs1.sourceforge.net This is a restricted Shell Account You cannot execute anything here. Connection to cvs.panjasource.sourceforge.net closed. However, if I type in without the "cvs.", then I autologin properly.  Again, the SSH command that works is as follows: C:\WINDOWS>ssh panjasource.sourceforge.net -l sheldon_samuels With this second command, I get right into my repository with no password. Does CVS use the CVSROOT to fire off the SSH command?  Can CVS be instructed to use a location for SSH other than CVSROOT?  Or is there a way to get CVS to drop the "cvs." when executing SSH, but to include "cvs." for everything else? Thanks. Sheldon Samuels Panja Software Product Manager >>> "Noel L Yap" <[EMAIL PROTECTED]> 06/06/00 08:43AM >>> I'm not sure what's going on here, but I do see that, when you use ssh to autologin, you specify the address without the "cvs." prefix.  It would make sense that if you're able to autologin with one address, CVS shouldn't prompt for a password with the same address.  Are you able to autologin using ssh to cvs.projectname.sourceforge.net?  Are you sure their side is configured properly? Noel [EMAIL PROTECTED] on 06/06/2000 09:22:33 AM To:   [EMAIL PROTECTED] cc:   [EMAIL PROTECTED] Subject:  Re: CVS access using SSH My variables are set as follows: SET CVSROOT=cvs.projectname.sourceforge.net SET CVS_RSH=ssh An interesting thing occurs as follows:  If I remove the "cvs." from the above, then SSH autologs in, but CVS is pointing to the wrong location on Sourceforge's servers and I'm not allowed to do anything.  It seems that CVS is using the value of CVSROOT to autolog in using SSH, but doing it incorrectly.  I haven't tried to look into the actual source code for CVS to see why, but I strongly suspect that somehow its purposely doing this. I've used CVS -t to view the commands and have confirmed that this is occuring. I can attach the specifics if it would help. Thanks for the assistance. Sheldon Samuels Panja Software Product Manager >>> "Noel L Yap" <[EMAIL PROTECTED]> 06/06/00 08:07AM >>> Hmmm.  That's strange.  How do you have your CVS environment variables defined (ie env | grep CVS)?  Do you have CVS_RSH set? Noel [EMAIL PROTECTED] on 06/05/2000 05:42:29 PM To:   [EMAIL PROTECTED] cc:   [EMAIL PROTECTED] Subject:  Re: CVS access using SSH I have run SSH directly and gotten through to the CVS Server without entering a password.  I didn't enter a passphrase when creating the key and am fairly confident that the keys were created and uploaded properly. If I enter:      ssh -v projectname.sourceforge.net I can go right in without a password or passphrase. It's only when I try to use CVS that it seems to require a password.  It seems that CVS requires the CVSROOT to be defined one way, which works if you enter a password, but doesn't work if you try to go without one. Thanks for the assistance. Sheldon Samuels >>> "Noel L Yap" <[EMAIL PROTECTED]> 06/05/00 04:29PM >>> Are you able to setup ssh-agent and cvs-add your private key to it?  This will allow ssh not to require the passphrase each and every time you or CVS uses it. I'm not sure how this works on 95, though. Noel [EMAIL PROTECTED] on 06/05/2000 03:27:52 PM To:   [EMAIL PROTECTED] cc:   (bcc: Noel L Yap) Subject:  CVS access using SSH It seems that CVS is trying to send an inaccurate command when attempting to use SSH and authorized keys.  I am trying to configure my CVS so that it doesn't require a password each and every time I run it.  I have also used the -t trace option to determine what CVS is trying to do.  Here is what I found: CVS tries to execute the following SSH command:   "ssh cvs.projectname.sourceforge.net -l username cvs server" If I try to run this very same command at a DOS Prompt (I'm on a Win95 machine), I get an error that this is a protected shell acount that I cannot access.  If I remove the "cvs." and the "cvs server" then all works well. Is there a way to define the specific command sent?  I know that my shared keys are also set up correctly. Thanks in advance for the help. Sheldon Samuels This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its subsidiaries and affiliates. This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its subsidiaries and affiliates. This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its subsidiaries and affiliates.