From rlogin to SSH: The Evolution of Secure Remote Login

1. History of Remote Login

In the early days of computing, remote usage was realized through distributed systems where users accessed a mainframe via terminals (keyboard and CRT display) connected by cables; the mainframe could serve multiple users simultaneously, physically separating terminal and host, constituting remote use.

Any two hosts on the Internet can establish a connection via network protocols; for example, web browsing involves a client computer and a server communicating over HTTP, which is fundamentally host‑to‑host communication.

As the Internet and LANs proliferated, remote access shifted to TCP/IP‑based connections, moving away from serial lines or telephone lines. Terminals evolved into PCs and smart devices, and protocols such as rlogin and Telnet were used on UNIX/Linux systems. Due to Telnet’s insecurity, SSH became the dominant secure remote‑login protocol, with built‑in client ssh and server sshd.

2. History of SSH

SSH (Secure Shell) is an application‑layer protocol that defines secure remote communication, encryption, and authentication.

Differences between SSH and HTTP

Both require a TCP three‑way handshake.

SSH establishes an encrypted channel and performs authentication after the connection is made.

Standard HTTP transmits data in clear text; only HTTPS adds TLS encryption, which negotiates encryption without mandatory authentication.

SSH’s most widely used implementation is OpenSSH, written in C. It includes the client ssh, the server daemon sshd, file‑transfer tools scp and sftp, all compiled from C source.

Java implementations also exist; the jsch library provides a pure‑Java SSH client for applications.

3. IP Access vs SSH Access

IP access involves opening an IP address and port, allowing connections without authentication, subject only to firewall rules, typically used for services like HTTP.

SSH port forwarding requires a user password or key, establishing an encrypted tunnel that can bypass firewalls to access internal services, enabling administrators to manage remote systems securely.

4. SSH Functions

Remote login for controlling remote servers.

File transfer to upload files to a server.

Port forwarding to access internal network services.