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.
