[Ccvssh-users] Problems using ccvssh with WinCVS

[Chris H. <ch...@ow...>]

> > 1. I'm having problems using it with the rhosts
> authentication in WinCVS
> > (important for the kind of user base I have). The ccvssh usage prompt is
> > always returned. Havent tried too hard with this yet. Could be just my
> > ignorance regarding WinCVS or how logins for ccvssh work (are they
> > persistant across processes?).
>
> Sorry, I have no experience with WinCVS. I've just now downloaded the
> source code and I'll try to make it run. I am not even sure that you
> should use rhosts authentication, but I'll try out and tell you.
>
> After a short look at the wincvs code, I think either WinCVS or ccvssh
> will have to be modified -- WinCVS tries to be too smart and replaces
> some environment variables. More info next week...
>
> Oh, one more thing: Logins for ccvssh are persistant, actually they are
> saved in a file (~/.cvspass) or registry
> (HKEY_CURRENT_USER\Software\GNU\ccvssh). That is the way cvs works
> (although cvs supports only .cvspass file).

I have just found the mechanism for failure.
ccvssh checks the command line for 5 arguments. This seems to work fine for
command line cvs but WinCVS passes 6 arguments!

The last argument from the command line cvs client is "cvs server", WinCVS
seems to split this into two separate parameters i.e. "cvs", "server". Thats
why ccvssh reports the usage error, too many arguments!

Not sure whats at fault here. It suggests that either nobody has attempted
to use the rhosts feature or rsh can handle this difference.