Berkeley r-commands: Difference between revisions

Revision as of 07:11, 28 November 2023

Revision as of 23:03, 28 November 2023

Line 46:

|}

The original Berkeley package that provides rlogin also features rcp (remote-copy, allowing files to be copied over the network) and [[Remote Shell|rsh]] (remote-shell, allowing commands to be run on a remote machine without the user logging into it). These share the hosts.equiv and {{code|.rhosts}} access-control scheme (although they connect to a different daemon, rshd).

{{Expand section|date=March 2018}}

The original Berkeley package that provides rlogin also features rcp (remote-copy, allowing files to be copied over the network) and [[Remote Shell|rsh]] (remote-shell, allowing commands to be run on a remote machine without the user logging into it). These share the hosts.equiv and .rhosts access-control scheme (although they connect to a different daemon, rshd).

==Commands==

Line 86 ⟶ 84:

* All information, including passwords, is transmitted unencrypted (making it vulnerable to interception).

* The {{code|.rlogin}} (or {{code|.rhosts}}) file is easy to misuse. They are designed to allow logins without a [[password]], but their reliance on remote usernames, hostnames, and IP addresses is exploitable. For this reason many corporate system administrators prohibit {{code|.rhosts}} files, and actively scrutinize their networks for offenders.

* The protocol partly relies on the remote party's {{code|rlogin}} client to provide information honestly, including source port and source host name. A corruptmalicious client is thus able tocan forge this and gain access, as the {{code|rlogin}} protocol has no means of [[Authentication|authenticating]] otherthe machines'client identities,is orrunning ensuringon thata trusted machine. It also cannot check if the requesting client on a trusted machine is the real {{code|rlogin}} client, meaning that malicious programs may pretend to be a standard-conforming {{code|rlogin}} client by using the same protocols.

* The common practice of mounting users' home directories via [[Network File System]] exposes rlogin to attack by means of fake {{code|.rhosts}} files - this means that any of its security faults automatically plague {{code|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 {{code|rlogin}} and {{code|telnet}} have replaced them with [[Secure shell|SSH]] and its {{code|rlogin}}-equivalent ''{{code|slogin''}}.<ref name="Sobell">{{cite book|last=Sobell|first=Mark|title=A Practical Guide to Linux Commands, Editors, and Shell Programming|isbn=978-0-13-136736-4|date=2010|publisher=Pearson Education, Inc}}</ref><ref name="iu">{{cite web|title=Unix job control command list|publisher=Indiana University|url=https://kb.iu.edu/d/afnw|accessdate=20 December 2014}}</ref>

==See also==