Re: [savannah-help-public] [sr #109445] Developer download using CVS fails

[Laurence Finston]

Hello Bob,

> Lastly if you can't configure the system to avoid rsh for whatever reason then
> in your specific environment you can set the CVS_RSH variable to use ssh.
> 
> For sh, bash, ksh, zsh:
> 
> CVS_RSH=ssh
> export CVS_RSH

This worked.  I'm using public computers at a library, so I can't make changes 
to the system.

Thank you very much for your help!

Laurence

> Gesendet: Montag, 15. Januar 2018 um 20:38 Uhr
> Von: "Bob Proulx" <address@hidden>
> An: "Laurence Finston" <address@hidden>, "Bob Proulx" <address@hidden>, 
> address@hidden
> Betreff: [sr #109445] Developer download using CVS fails
>
> Follow-up Comment #1, sr #109445 (project administration):
> 
> Hello Laurence, You appear to be using rsh instead of ssh trying to access
> CVS.  You may not be familiar with rsh but that is one of the classic BSD
> 'r'commands along with rlogin and rcp.  But the web is a hostile place and
> those commands use the trust model from 1985 and are no longer safe for use on
> the hostile Internet.
> 
> Please use the ssh command to access CVS and for any other remote access on
> the net.  It's safe and uses authenticated encrypted access.  Savannah only
> allows use of SSH.
> 
> You didn't say what system you are using for your client access.  If it were a
> Debian system (or derived from Debian) then I would suggest this following:
> 
> apt-get purge rsh-client
> 
> That will purge rsy, rcp, and rlogin client programs from your system.  They
> are not safe on the hostile Internet and are never appropriate there.  They
> are only useful on a private LAN for use with a historical legacy
> environment.
> 
> If you can't remove it then you can configure it away.  Use the
> update-alternatives command.
> 
> update-alternatives --display rsh
> 
> sudo update-alternatives --config rsh
> 
> If you can't remove rsh then you can use update-alternatives --config to
> configure it to select ssh instead of netkit-rsh.
> 
> Lastly if you can't configure the system to avoid rsh for whatever reason then
> in your specific environment you can set the CVS_RSH variable to use ssh.
> 
> For sh, bash, ksh, zsh:
> 
> CVS_RSH=ssh
> export CVS_RSH
> 
> For csh, tcsh:
> 
> setenv CVS_RSH ssh
> 
> Please let me know if this helps you with your access. :-)
> 
> 
> 
> 
>     _______________________________________________________
> 
> Reply to this item at:
> 
>   <http://savannah.gnu.org/support/?109445>
> 
> _______________________________________________
>   Message sent via/by Savannah
>   http://savannah.gnu.org/
> 
>