Content deleted Content added
Bluelinking 1 books for verifiability.) #IABot (v2.1alpha3 |
Citation bot (talk | contribs) m Alter: title. Add: date, title-link. | You can use this bot yourself. Report bugs here. | Activated by User:AManWithNoPlan | All pages linked from User:AManWithNoPlan/sandbox2. |
||
Line 18:
}}
{{IPstack}}
The '''Berkeley r-commands''' are a [[Software suite|suite]] of [[computer program]]s designed to enable users of one [[Unix]] system to [[log in]] or issue [[Command (computing)|commands]] to another [[Unix]] computer via [[TCP/IP]] [[computer network]].<ref>{{cite book |title=Unix System Management: Primer Plus |last=Horwitz |first=Jeff |chapter=Using the Berkeley r-commands Without a Password |chapter-url=https://books.google.com/books?id=-sue_SyjuCMC&pg=PA339 |page=339 |year=2003 |orig-year=2002 |publisher=Sams Publishing |via=Google Books |isbn=978-0-672-32372-0 |access-date=2018-03-04}}</ref> The r-commands were developed in 1982 by the [[Computer Systems Research Group]] at the [[University of California, Berkeley]], based on an early implementation of [[TCP/IP]] (the [[protocol stack]] of the [[Internet]]).<ref name="McKusick">{{cite book |title=
The CSRG incorporated the r-commands into their [[Unix]] [[operating system]], the [[Berkeley Software Distribution]] (BSD). The r-commands premiered in BSD v4.1.<ref name="McKusick"/> Among the programs in the suite are: {{code|rcp}} (remote [[File copying|copy]]), {{code|rexec}} (remote [[Execution (computing)|execution]]), {{code|rlogin}} (remote [[login]]), {{code|rsh}} (remote [[Shell (computing)|shell]]), {{code|rstat}}, {{code|ruptime}}, and {{code|rwho}} (remote [[who (Unix)|who]]).<ref name="McKusick"/><ref>{{cite book |title=Guide to TCP/IP: IPv6 and IPv4 |first=James |last=Pyles |first2=Jeffrey L. |last2=Carrell |first3=Ed |last3=Tittel |chapter=Which IP Services Are Most Vulnerable? |chapter-url=https://books.google.com/books?id=sQevDAAAQBAJ&pg=PA659 |page=659 |publisher=Cengage Learning |year=2017 |edition=5th |isbn=978-1-305-94695-8 |via=Google Books}}</ref>
The r-commands were a significant innovation, and became ''de facto'' standards for Unix operating systems.<ref>Casad (2008), p. [https://books.google.com/books?id=q81cs5140_YC&pg=PT346 346]</ref><ref>{{cite book |title=Red Hat Fedora Linux 2 Bible |last=Negus |first=Christopher |publisher=Wiley |isbn=0-7645-5745-9 |oclc=441918216 |chapter=About "r" Commands |chapter-url=https://www.wiley.com/legacy/compbooks/negus/rhbf2/r-commands.html |access-date=2018-03-04|date=2004-07-02 }}</ref> With wider public adoption of the Internet, their inherent security vulnerabilities became a problem,<ref>http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.178.8497&rep=rep1&type=pdf</ref> and beginning with the development of [[Secure Shell]] protocols and applications in 1995, its adoption entirely supplanted the deployment and use of r-commands (and Telnet) on networked systems.<ref>https://dash.harvard.edu/bitstream/handle/1/16781951/sshVsTelnetWeb3.pdf?sequence=1</ref>
==Authentication==
Line 90:
* The common practice of mounting users' home directories via NFS exposes rlogin to attack by means of fake .rhosts files - this means that any of [[Network File System|NFS's]] security faults automatically plague rlogin.
Due to these problems, the r-commands fell into relative disuse (with many Unix and [[Linux]] distributions no longer including them by default). Many networks that formerly relied on rlogin and telnet have replaced them with [[Secure shell|SSH]] and its rlogin-equivalent ''slogin''.<ref name="Sobell">{{cite book|last=Sobell|first=Mark|title=A Practical Guide to Linux Commands, Editors, and Shell Programming|
==See also==
| |||