CVSNT and SSH work, but WinCVS and SSH doesn't !

[Philippe Bertin]

'Llo All,

I have a WinCVS configuration problem (I think). Could any-one help me
out on this ? (or point me to a link I'm helped with) ? Here's the problem:

I have a Windows CVS client, and a Linux CVS server. The
Windows client is using WinCVS; the server is started via xinetd, as
user cvs, with the correct --allow-root=<my_cvs_repository_dir> pserver
option.

Before, it has long time been working as :local: over a Samba share.
Yesterday, I started using :pserver: But I could not import a module
using this method; searching on Google turned up that I had to use ssh,
because pserver was too insecure to allow write access on the directory
"my_cvs_repository_dir" (see above).

So I switched to ssh (my ssh- client is putty), password based. But even
after a full day of tweaking settings, I did not come to the point of
being able to import a new module using ssh.

Then I started using the command line (on the Windows client): as CVSNT
is installed as part of WinCVS, I used that one's cvs.exe as a cvs
client, and set my CVSROOT to
:ssh:<myname>@<my_linux_box>:/<my_cvs_repository_dir>

Then I COULD (after being prompted for my password) import a new module.
SO MY SERVER seems to be working fine. SO MY CVSNT CLIENT seems to be
working fine TOO.

Now my question is : how come I can't seem to be using WinCVS as the
client (which is, after all, using cvsnt's cvs.exe as a client if I
understand well ???) to import a new module (and do other things), but
that I CAN use cvsnt's cvs.exe client on the command line ? With WinCVS,
I continue to get the error 'wrong port number'.

My WinCVS settings are (in WinCVS Settings window):
ssh as authentication (settings: pointing to my putty ssh- client,
additional ssh- option is "-ssh")
the rest is basically correctly filled in, but I currently have added to
CVSROOT ":ssh:" in front of the automatically composed CVSROOT.



Thanks for any helping hand or link :)

Kind regards,

PhB.




------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/z3wwlB/TM
--------------------------------------------------------------------~->


Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cvsgui/

<*> To unsubscribe from this group, send an email to:
cvsgui-***@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

[Oliver Giesen]

Post by Philippe Bertin
Then I started using the command line (on the Windows client): as CVSNT
is installed as part of WinCVS, I used that one's cvs.exe as a cvs
client, and set my CVSROOT to
Then I COULD (after being prompted for my password) import a new module.
SO MY SERVER seems to be working fine. SO MY CVSNT CLIENT seems to be
working fine TOO.
Now my question is : how come I can't seem to be using WinCVS as the
client (which is, after all, using cvsnt's cvs.exe as a client if I
understand well ???) to import a new module (and do other things), but
that I CAN use cvsnt's cvs.exe client on the command line ? With WinCVS,
I continue to get the error 'wrong port number'.
ssh as authentication (settings: pointing to my putty ssh- client,
additional ssh- option is "-ssh")
the rest is basically correctly filled in, but I currently have added to
CVSROOT ":ssh:" in front of the automatically composed CVSROOT.

Sounds like you're still using WinCvs 1.3.17 or earlier (which is of course
perfectly alright as it is the latest "recommended release"). You cannot
really use CVSNT's :ssh: protocol from the GUI with anything pre-1.3.18. If
you choose "ssh" authentication in WinCvs 1.3.17, what will get used
effectively is :ext: and that definitely could be a pain to set up (also see
http://cvsgui.sf.net/newfaq.htm#noAdditionalSshOpts). So, you either have to
do your imports and intitial checkouts from the commandline (FYI: the
Admin|Commandline dialog in WinCvs 1.3.17 already has an option for the
new-style protocol configuration) or upgrade to the latest development build
which will allow you to configure and use the :ssh: protocol properly. BTW:
you will not need PuTTY anymore in that case as :ssh: effectively is a
built-in client (incidentally also based on the PuTTY code). The other
alternative is of course to try to get :ext: working but I would advise
against that. :ssh: is simply so much easier to set up and it is also much
better integrated with WinCvs (for instance there will be a proper password
dialog and no more need to enter your password blindly into a console
window).

Hope this helps.

Oliver
------
In everybody's best interest, please do not post or CC technical questions
to me in private unless they are specifically about a macro/product of mine
that is NOT already bundled with WinCvs. I will generally forward my replies
to such posts to the CVSGUI list without further notice.
---- ------------------
JID: ***@jabber.org
ICQ: 18777742 (http://wwp.icq.com/18777742)



------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/z3wwlB/TM
--------------------------------------------------------------------~->


Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cvsgui/

<*> To unsubscribe from this group, send an email to:
cvsgui-***@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/