WinCVS SSH - set pwd authentication first

Tjeerd Kaastra

unread,

Jul 4, 2000, 3:00:00 AM7/4/00

to

Hi,

I am trying to set up WinCVS with a SSH connection.

I have already established it with port-forwarding through TeraTerm. But now
I am trying to use a direct SSH client (commandline driven).
The commandline SSH client works fine (I can login etc.). CVS through the
oldfashioned passwd file also works fine.

But when I try to use the ssh client from within CVS I get the following
error when clicking login: "Set the password authentication first in the
preferences!"

My preferences in WinCVS are the following:
CVSROOT = myus...@host.nl:/cvs
Authentication = SSH server
RSA identity = c:\kaastra\.ssh\identity
Use version: cvs 1.10 (Standard)

On my ports tab, nothing is selected (but I have also tried ssh as the
alternative rsh name).

I have set the following environment variables:
HOME=c:\kaastra (my home directory, it contains a dir called .ssh and that
in turn contains my identity and identity.pub)
CVS_RSH=ssh
PATH=c:\program files\gnu\wincvs 1.1\ (and ofcourse all other paths)

Furthermore the server also has my identity and identity.pub in the ~/.ssh
and I have added the identity.pub to the authorized_keys. (TeraTerm works
fine with the RSA key).

Can someone please tell me what I am doing wrong?

Thanks in advance.

Regards,

Tjeerd Kaastra

Jesús M. NAVARRO

unread,

Jul 5, 2000, 3:00:00 AM7/5/00

to

Tjeerd Kaastra wrote:
>
> Hi,
>
> I am trying to set up WinCVS with a SSH connection.
>
> I have already established it with port-forwarding through TeraTerm. But now
> I am trying to use a direct SSH client (commandline driven).
> The commandline SSH client works fine (I can login etc.). CVS through the
> oldfashioned passwd file also works fine.
>
> But when I try to use the ssh client from within CVS I get the following
> error when clicking login: "Set the password authentication first in the
> preferences!"
>

That's just OK. The 'login' option only works with a pserver. When
using SSH (or rsh, for that matter) you don't 'log in', you just send
the command to the remote system. You can try, for instance, just to
checkout a module then, if RSA or something simmilar is in use, the
command will just success, if not, try starting wincvs from a command
prompt (instead of, let's say a shortcut) and you will see there the
password prompt (I didn't tested it, but it might be that the password
prompt appears at the 'log' window).

--
SALUD,
Jesús
***
jesus_...@geocities.com
***

David Gravereaux

unread,

Jul 5, 2000, 3:00:00 AM7/5/00

to

[WinCVS 1.1 beta 14]

Jesús M. NAVARRO <jesus_...@geocities.com> wrote:

>You can try, for instance, just to
>checkout a module then, if RSA or something simmilar is in use, the
>command will just success, if not, try starting wincvs from a command

you meant cvs.exe here, right? --^

>prompt (instead of, let's say a shortcut) and you will see there the
>password prompt (I didn't tested it, but it might be that the password
>prompt appears at the 'log' window).

Yeah, I get that too if my key requires a password. There isn't a way currently
to have WinCVS popup a prompt (that I know of) when cvs.exe is shelling out to
ssh.exe during the connection phase. That'll need to get added to the code by
someone, someday.

And that 'RSA identity' checkbox in preferences doesn't appear to do anything
(?) Maybe I should read through Alexandre's code and see what it does :)

Using the ssh.bat technique @ http://www.wincvs.org/ssh.html (technique #2), I
can do the following given that when I made my key, I didn't set a password for
it:

C:\Dev\WinCvs>set CVS_RSH=ssh.bat

C:\Dev\WinCvs>cvs -d :ext:davy...@cvs.tomasoft.sourceforge.net:/cvsroot/tomasof
t co -c
Ctk Ctk
Mcl Mcl
MclHelp MclHelp
XiRC_hack XiRC_hack
all -a Ctk Mcl MclHelp macros serverlist tcl8.1.0 tomahawk XiRC_hack
macros macros
serverlist serverlist
tcl8.1.0 tcl8.1.0
tomahawk tomahawk

C:\Dev\WinCvs>

--
David Gravereaux <davy...@ajubasolutions.com> Yet Another Tcl Guy
Sustaining Engineer (Tech Support) Ajuba Solutions
(650) 230-4079

Tjeerd Kaastra

unread,

Jul 6, 2000, 3:00:00 AM7/6/00

to

Hi,

Well, the solution was indeed quite simple. I was so focused on logging in
that I never tried the commands directly. Thanks a lot!
It is working very well...

BTW: As far as I know, the RSA identity checkbox is used so you can enter
your RSA key (the file called 'identity').

There are 3 ways to do the SSH login:
- If you do not use the RSA identity, you will always have to enter your
password (with every transaction: commit, update, checkout, etc.).
- If you use RSA with a key that has a passphrase you will also have to type
your password on every transaction.
- If you use RSA with a key that has NO passphrase you can do every
transaction without any password typing.
(you can make the key with ssh-keygen).

If I have to type a password, a command-prompt is started (it is minimalised
and the window is completely black). In this window I have to type my
password. Rather vague, but it is working.

Regards,

Tjeerd Kaastra

David Gravereaux <davy...@ajubasolutions.com> wrote in message
news:0js6ms4sampmhtgpf...@4ax.com...