On Mar 5, 2015, at 10:21, Hans Ottevanger <h...@beastielabs.net> wrote:
> On 03/05/15 13:21, Slawa Olhovchenkov wrote: >> On Thu, Mar 05, 2015 at 02:48:29PM +0300, Gleb Smirnoff wrote: >> >>> On Wed, Mar 04, 2015 at 10:01:45PM +0000, Baptiste Daroussin wrote: >>> B> Author: bapt >>> B> Date: Wed Mar 4 22:01:44 2015 >>> B> New Revision: 279603 >>> B> URL: https://svnweb.freebsd.org/changeset/base/279603 >>> B> >>> B> Log: >>> B> r* commands are not precious anymore >>> B> >>> B> Modified: >>> B> head/bin/rcp/Makefile >>> B> head/usr.bin/rlogin/Makefile >>> >>> I guess when they are going to be not precious enough to be removed? :) >>> >>> In modern world of ssh and https, does any OS require them in base? >> >> yes. >> Some telecom equipment require rlogin. >> _______________________________________________ > > Considering that the r-commands are not particularly large and also not > really a maintenance nightmare, a would just keep them. They are (still) more > or less part of the standard Unix toolbox, as perceived by end-users, and you > had better not make life too difficult for them. The same is true for telnet. > > I see these tools in use regularly, e.g. to control measurement equipment > programmatically. Due to the price tag of those instruments, that won't > change overnight. The usage is limited to a LAN however, nobody I know uses > these tools over the public Internet anymore. > > As far as I know only OpenBSD got rid of these tools up to now. Most other > Unix(-like) systems still have them. > > And if they absolutely have to go, what happens to the corresponding daemons > in /usr/libexec (rshd and rlogind)? Why not just move them to ports so the people that need them can have them…?
signature.asc
Description: Message signed with OpenPGP using GPGMail
