Date: Tue, 9 Apr 2002 23:58:26 -0400 From: Carl Schmidt <cschmidt@slackerbsd.org> To: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/bin Makefile src/share/examples/etc make.conf src/usr.bin Makefile Message-ID: <20020410035825.GA7883@carbon.slackerbsd.org> In-Reply-To: <200204100318.g3A3IXOF013706@hak.lan.Awfulhak.org> References: <20020410025230.GA8927@roughtrade.net> <200204100318.g3A3IXOF013706@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2002 at 04:18:33AM +0100, Brian Somers wrote: > > I don't know how standard the practise is, but part of my standard > > server-hardening procedure is to remove the rsh/rcp tools. I don't > > allow my users to even think about risking their use: they have > > been fully superseded in functionality in every way by ssh. I would > [.....] > > I think ssh needs a ``-c none'' option before it can claim to have > superseded rsh. Until then, ssh isn't the right tool to transfer > across a fast, trusted network. Perhaps it is just -current but: oxygen# rsh -c rsh: illegal option -- c oxygen# rcp -c rcp: illegal option -- c The one machine i have running -stable does not have the 'r' tools installed so I can't test but I do have the manual pages for each command and neither rcp nor rsh have this "-c" option documented. Could you explain what it is supposed to do? -- Carl Schmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410035825.GA7883>