Re: cvs remote: rsh vs. ssh protocols

[Richard Cobbe]

Lo, on Thursday, December 28, address@hidden did write:

> We had been using rsh and CVS to remotely update our Web site between 
> two Solaris boxes (staging server to live server) with no problem. 
> Now that we are using shh as opposed to telnet for remote login, rsh 
> does not work in the same way. That is, even though we can use rsh 
> without a specified command to login, and then are able to run 
> commands, we cannot do the two in one step. We keep 
> getting 'permission denied' returned. 
> We have tried every conceivable modifications of permissions but have 
> come to the conclusion that instituting 'ssh' is preventing us from 
> utilizing rsh completely as is needed for CVS to work between 
> machines.
> Do we now need to use 'ssh' as the protocol for CVS updates? If so, 
> what would be the best way to implement this? I saw an earlier thread 
> that described this somewhat but haven't had luck in getting the two 
> machines to communicate yet.

I don't know if you *need* to use ssh, but it can't hurt.  Simply configure
ssh to allow your users to log into the CVS server machine---I prefer
without passwords using ssh-agent and ssh-askpass, but your preferences may
vary.  After that works, simply have everyone set CVS_RSH to ssh on the
client machines.  I've used this method for a while now (on Linux), and it
works seamlessly.

Richard