8 ms·
FreeBSD deprecates all r-cmds (rcp, rlogin, etc.)
- dijit 9y agoShould have been deprecated long ago in my opinion. I've never seen those commands used in my professional life.
- inopinatus 9y agoI have, and I'm sorry to report they may still be in use in healthcare, government, financial institutions.
- robin_reala 9y agoFor non-FreeBSD people, what do the r commands do?
- tptacek 9y agoTake "ssh" and replace the "s" for "secure" with "r" for "remote".
- zrail 9y agoRemote. They've all basically been superseded by ssh-based tools.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- SwellJoe 9y ago"r" stands for "remote". They predated ssh and were how things were done remotely in the (distant) past. You can pretty much just replace the "r" with an "s" and that's what they did, only without the "secure" provided by ssh/scp/etc. They were/are not exclusive to FreeBSD.
- bluejekyll 9y agoOnly in computers is the distant past 25 years ago...
- SwellJoe 9y ago25 years ago I was using an Amiga 3000 with a 25 MHz 68030 CPU and 8 MB of RAM. It feels pretty distant to me. A lot has changed in that time. And, OpenSSH isn't even 20 years old, so it's actually not been that long. SSH was 1995, that's probably the beginning of the ssh epoch and the beginning of the end of the rsh age.
- yjftsjthsd-h 9y ago25 years of longer than some of us have been alive;)
- r1ch 9y agoThink of them as wildly insecure versions of SCP / SSH. Trusted LAN only, trusted users only, etc. https://en.wikipedia.org/wiki/Rlogin https://en.wikipedia.org/wiki/Rlogin has more background information.
- ktRolster 9y agoThey've been out of date for nearly two decades now.
- peterwwillis 9y agoThey're not exactly insecure, they're just used for different things, like networks that are already secure. You can secure existing networks pretty well against things like MitM, and then it doesn't matter if you use rsh or ssh. (part of why so many routers still use telnet is it's supposed to only be enabled on management interfaces) Quite a few years ago I helped build the public terminal cluster for HOPE. That year we used a token ring network for all of the hosts. Nobody anywhere near the conference had any token ring gear whatsoever. It was impossible to break into the network, so you had to use existing nodes. And the nodes' adapters had their promiscuous modes disabled in hardware. That plus a hardened terminal server and an extremely limited thin client meant nobody could successfully hack the network. You could have used telnet all day and been totally secure. Though in conference environments, the network is not the biggest risk for targeted attacks. Carefully watching your target enter their password is simpler and more effective.
- gbrown_ 9y ago> They're not exactly insecure, they're just used for different things, like networks that are already secure. There is no such thing. I'd be pedantic and rephrase this to - used for networks which you trust.
- peterwwillis 9y agoI think the engineers setting up red/black networks for the military might disagree with you, but even in the enterprise 802.1X can result in a secure local network. I would say trust is a result of the operation of the network, as you may need to do something to establish it. And in this vein you're right, "networks you already trust" definitely would have been better wording.
- arca_vorago 9y agoBasically unencrypted straight remote connections, the predecessor of telnet, scp, etc. I always wondered back when FreeBSD was main daily why it was still there.
- chx 9y agoWhat? How could it predate telnet? That was RFC 15 from freakin' 1969 and before that, there isn't really anything. But even if you consider RFC 854 to be telnet, well that's https://tools.ietf.org/html/rfc854 https://tools.ietf.org/html/rfc854 May 1983, rlogin was released in 4.2BSD, that's July 1983 http://www.informatica.co.cr/bsd/research/acrobat/830721.pdf http://www.informatica.co.cr/bsd/research/acrobat/830721.pdf
- arca_vorago 9y agoWell they may not have technically predated then but what I meant is that as far as I know for a while r(etc) was used and then was generally replaced in actual usage by telnet, etc.
- tyingq 9y agoIt was the other way around. Rsh and rlogin appeared well after telnet, and displaced some telnet use because they were able to do password-free connections via .rhosts
- mrkrab 9y agoOh yes that file. The good old days when you would use social engineering on irc to have yourself added to your victim's .rhosts
- NamTaf 9y agoDespite using FreeBSD I had the same question as I had never really touched them. From reading up on it, it looks like they're old remote versions of various commands for interacting with a server/mainframe from a thin client. For example, rcp copies to a remote host, rlogin starts a terminal session on a remote host, etc. I could well be missing nuance though. My experience with FreeBSD is using it for my server for ZFS' gloriousness.
- deleted 9y ago[deleted]
- ams6110 9y agoThey are basically like http is to https. Unauthenticated, clear-text remote login, copy, etc.
- yeasayer 9y agoWhat about "rsync"? I use this command pretty often.
- SwellJoe 9y agoCompletely unrelated.
- 3131s 9y agoYep, rsync is still a relevant and awesome tool. The man page is one of the nicest I've seen too, 60+ pages in a small font and nicely structured with many examples.
- yrro 9y agoEvery time I read the man page for rsync, I find myself wishing thevdocumentation was in texinfo format.
- jethro_tell 9y agoI can't tell if your joking but Everytime I try to use that man page, I end up on stack overflow. I mean, why are all the options out of alphabetical order? You want me to page through all of them? Why are all the examples in the middle so I have to page past them to find out what options are available? It is such a mess. Maybe that was the point and I'm just joke_explainer. Or maybe we have a legit disagreement about what makes a good man page.
- Symbiote 9y agoType / which is the command for search in less, the usual pager that displays the man page.
- jethro_tell 9y agoWhat if I don't know what options are there so I have to read or skip the examples to find the options? Most manage use is skimming the terse options section to remember what flag matches with an option and to remember which options I want. I know how to search, it's the only man page I know that is formated this way and I find it to be a very poor design choice. As if I know what I wanted I wouldn't be looking in the man page.
- hendersoon 9y agoMy immediate reaction and maybe yours too was "woah, including rsync?" And no, while rsync does indeed begin with a letter R, it is not being removed.
- __s 9y agorm is also not being deprecated
- lsh 9y agothank goodness - I have no idea how I'd run m remotely.
- DonHopkins 9y agoThey did a cost benefit analysis, and it turns out that it's actually cheaper to buy new disk drives than to pay someone by the hour to remove files, so rm was just not worth it any more.
- JdeBP 9y ago
- titanomachy 9y agorsync is not one of the deprecated commands. I guess it's not considered an "r-command", although "sync" is also a command on its own.
- tptacek 9y agoRsync is implemented in terms either of rsh or ssh. It's not an r-command. It's unrelated to "sync".
- benchaney 9y agoTrue, but rsync is not the remote version of sync, so I don't think it counts.
- RJIb8RBYxzAMX9u 9y ago"r-commands" is to rsync as OpenSSL is to OpenSSH. That is, they share the same prefix, have somewhat overlapping usage cases, but are actually completely unrelated to each other.
- SwellJoe 9y agoI'm surprised they're still in there, at all. You can still get them on Linux, but that's just because of the way Linux distros are built; nobody is working on them as a core part of the OS. If they were in ports and just kinda stuck around due to inertia, that'd make sense. But, it seems like these are in the core FreeBSD installation, which is borderline crazy. One of the (few) things I like about the BSDs over Linux is that there is a core system that is maintained by a unified team working closely together in the same repos and with the same communication channels and the like, and following the same standards for docs, interfaces, etc. I like that aspect because people with good judgement are in charge of the platform itself and you can just sort of assume the default installation is cohesive, secure, and has reasonable defaults. This is sort of an argument against that theory; there's nothing reasonable about having rsh/rcp/etc. on a modern system. I mean, it's mostly harmless, as long as you know enough to never use them and never allow any software you run to use them, but still...why leave a bomb just laying around?
- ktRolster 9y agoIt's ok to have the commands in there, because you never know when you're going to have to connect to a legacy system (in a recent scan I found 250k open telnet ports). The thing that should be deprecated is the server.
- SwellJoe 9y agoI think it's something that should be sort of pushed by folks who are upstream. As long as people can continue to use dangerous protocols without friction, they'll keep doing it. I think it has value for users to say, "Oh, so I need to go install a package in order to continue using this protocol." Maybe that'll trigger a change on the server-side.
- marcosdumay 9y agoThere's no problem with exposing a rlogin or telnet server over an RS232 interface, or a USB port. There is no reason why clients for using those should be hard to install.
- spilk 9y agovery edge case, but you can't network-install an SGI machine without an rlogind on the other end.
- SwellJoe 9y agoYou're telling me that these machines need an rlogind to install over a network? http://www.sgi.com/products/servers/ http://www.sgi.com/products/servers/
- tyingq 9y agoProbably not. Those run linux. It was a requirement for Irix remote installs. http://techpubs.spinlocksolutions.com/irix/remote-irix-6.5-installation-from-linux.html http://techpubs.spinlocksolutions.com/irix/remote-irix-6.5-i...
- SwellJoe 9y agoSo FreeBSD should keep shipping rlogin in the default install to support people who might be installing an OS for which the last major version was released in 1998 and the last minor update was in 2005? Man, nerds really like to "Well, actually..."
- moonbug 9y agoNo SGI you've been able to buy from any of the last 3 incarnations of SGI.
- johnbellone 9y agoIt's about fucking time.
- stock_toaster 9y agoAbout damn time!
- notaplumber 9y agoI think OpenBSD completely removed them years ago; forget deprecation. https://www.openbsd.org/plus32.html https://www.openbsd.org/plus32.html (OpenBSD 3.2; rlogin/rlogind/rexecd) - 2002. http://marc.theaimsgroup.com/?l=openbsd-cvs&m=102072388123069&w=2 http://marc.theaimsgroup.com/?l=openbsd-cvs&m=10207238812306... (Edit: http://marc.info/?l=openbsd-cvs&m=102072388123069&w=2 http://marc.info/?l=openbsd-cvs&m=102072388123069&w=2) They removed telnetd a bit later, 2005~ish? I can't find commits, but rsh/rshd have no online man pages since 5.6 - 2014.
- stock_toaster 9y agoI really have to hand it to the OpenBSD folks. They really have their release and deprecation cycles nailed down pretty well. I also enjoy the fact that they seem (to me at least) to rip some of old and clunky bits out sooner than others. It would actually be pretty interesting to see a timeline of all the things OpenBSD has removed over the years.
- notaplumber 9y agoThey remove things like rlogin/rsh/telnetd and give you OpenSSH, or BSD window(1) and give you tmux. Or LibreSSL instead of OpenSSL (not an OpenBSD subproject). https://www.openbsd.org/innovations.html https://www.openbsd.org/innovations.html The various plusXX page give you a changelog style, but also the individual release pages are good at highlighting removed and replaced software. Also, the hackathon, t-shirt and release song artwork is great at showing what was going on at the time in the project. https://www.openbsd.org/lyrics.html https://www.openbsd.org/lyrics.html https://www.openbsd.org/hackathons.html https://www.openbsd.org/hackathons.html https://www.openbsd.org/tshirts.html https://www.openbsd.org/tshirts.html This one is surprisingly relevant: https://www.openbsd.org/images/tshirt-9b.jpg https://www.openbsd.org/images/tshirt-9b.jpg
- sigjuice 9y agoOpenBSD can do this and get away with it since its use and deployment is minuscule compared to other systems.
- notaplumber 9y ago"FreeBSD has deprecated rcp/rlogin/rsh in 2017. We're aiming for 2019 for telnetd and 2025 for SSHv1. No deletions planned at this time."
- raldi 9y agoI guess at this point I'm never going to learn the difference between rlogin, rsh, and rexec. Even googling it and reading the first page of results doesn't clear things up.
- killerbat00 9y agoA comment below explains exactly this: https://news.ycombinator.com/item?id=14699219 https://news.ycombinator.com/item?id=14699219
- raldi 9y agoNo it doesn't. It explains what the three as a group do; what I'm asking is, what's the difference between these three? Why did we need three separate commands? When (in the pre-SSH days) would you use one versus the others?
- the_mitsuhiko 9y agoSSH also brings these separate commands and a few more. ssh, slogin, scp, sshd, and sftp.
- raldi 9y agoOkay, but that's not the question I'm asking.
- sigjuice 9y agoEach of these FreeBSD commands have man pages which your googling should have shown.
- raldi 9y agoslogin is just a symlink to ssh, and sexec does not exist. So the s-commands' manpages tell me nothing about the difference between rsh, rlogin, and rexec, or why all three needed to be created.
- reacweb 9y agoThese commands have deprecated themselves because of many limitations that were hitting almost randomly (for example https://stackoverflow.com/questions/12677712/rsh-running-out-of-ports https://stackoverflow.com/questions/12677712/rsh-running-out...). We had to migrate all the scripts using r-cmds to ssh because of reliability issues when the number of hosts was increasing.
- mp3geek 9y agoMake a SVN commit to deprecate these commands, it also seems time to depreciate svn.
- gbrown_ 9y agoRecall these were never meant to live very long in the first place. With the internal restructuring completed and the TCP/IP protocols integrated with the prototype IPC facilities, several simple applications were created to provide local users access to remote resources. These programs, rcp, rsh, rlogin, and rwho were intended to be temporary tools that would eventually be replaced by more reasonable facilities (hence the use of the distinguishing "r" prefix). This system, called 4.1a, was first distributed in April 1982 for local use; it was never intended that it would have wide circulation, though bootleg copies of the system proliferated as sites grew impatient waiting for the 4.2 release. http://www.oreilly.com/openbook/opensources/book/kirkmck.html http://www.oreilly.com/openbook/opensources/book/kirkmck.htm...
- tachion 9y agoWhile you're here, have you donated[0][1] yet? :) You may or may not be aware, but FreeBSD runs your movies on Netflix, your games on PlayStation 4 and Nitendo Switch, your files on FreeNAS and ZFS, your friends on WhatsApp and OpenBSD runs everything else on OpenSSH. ;) So, you may or may not know that, but you need FreeBSD and OpenBSD and they also need you! Every cent counts and so does every contributor, that helps the foundations keep their non-profit status. [0] https://www.freebsdfoundation.org/donate/ https://www.freebsdfoundation.org/donate/ [1] https://www.openbsd.org/donations.html https://www.openbsd.org/donations.html
- simias 9y agoI do donate to FreeBSD and I encourage others to do so, but paying to give Netflix, Sony and Nintendo the privilege to use a free OS doesn't sound like a great incentive. They're not exactly nonprofits.
- tachion 9y agoRemember it is not about Netflix, Sony and Nintendo getting something for free, it is about ANYONE being able to get it for free, no matter who they are and what they want to do with it. Also, don't forget that some of these companies, like Netflix, for example, do contribute to the project, both in money and in code. But again, this is not the point - next time you'll be lucky and create Netflix 2.0, you'll be able to use FreeBSD code to your business advantage too!
- freehunter 9y agoThat was my thought too, not a great argument. I don't pay Oracle because my Bluray player runs Java, Sony pays Oracle to use Java and I pay Sony for the Bluray player. I don't even need to know it runs Java, it's included in the purchase price. Likewise I shouldn't need to know Netflix uses FreeBSD, or the PS4 uses it, or Nintendo uses it. My users don't know my software runs on Heroku, they're not being asked to give money to DHH for Rails or become a Postgres sponsor or donate to the Linux Foundation just because they use a product that uses that technology on the back end. If you make a product that directly profits from the work of a non-profit, you should consider a donation to keep the project around. But if you just use a product that's built on an open source project in a non-transparent way and don't actually use the open-source project yourself but you're still donating to it, you would be a very generous citizen. If FreeBSD didn't exist, Nintendo and Sony and Netflix would use something else. If companies that use FreeBSD want to keep using FreeBSD, they're the ones who should be paying for it. It's a little much to ask that everyone donate to every open-source project they happen to use in an incredibly incidental way. I'd be spending half my time hunting down projects and the other half cutting checks to them. I donate to projects I actually use.
- esbranson 9y agoImagine a world where all IP packets are indistinguishable from any other, where TCP cannot be exploited to block SSH connections, where even key exchange/agreement cannot be blocked without blocking all IP packets. In such a world, blocking Wikipedia would be all but impossible without taking the totalitarian country to ruin. But IPsec was sabotaged thoroughly. draft-ietf-ipsec-inline-isakmp was silenced. Now every protocol must implement a security policy and framework individually, without exception. SSH, TLS, EAP oh my (that is a lot of EAP methods.) Vae victis. Woe to the conquered. RIP IPsec.