SSH
In 1995, at the University of Helsinki, Tatu Ylönen had just experienced a network attack on his institution’s systems. Passwords were circulating in plain text, intercepted by attackers exploiting the glaring vulnerabilities of protocols like Telnet, rlogin, or rsh. Faced with this concrete threat, the Finnish researcher decided to design a radically different solution: a protocol capable of encrypting communications and robustly authenticating the parties involved. SSH, for Secure Shell, was born from this immediate necessity to protect exchanges over the Internet.
The first version was released in July 1995 as free software. The success was immediate in academic and technical circles. Everyone understood the urgency of securing remote connections, and SSH met this need. Given this enthusiasm, Ylönen founded SSH Communications Security in December 1995. The company commercialized professional versions while maintaining a free version for non-commercial uses, a delicate balance between economic logic and broad dissemination of the protocol.
The following year marked a turning point with SSH-2, a complete redesign of the initial version. This new iteration adopted a three-layer architecture: the transport protocol handled encryption and server authentication, the authentication protocol verified user identity, and the connection protocol multiplexed communication channels within a single secure tunnel. This modularity brought increased flexibility and robustness.
The IETF launched a working group dedicated to SSH standardization in 1997. Between 2004 and 2006, several RFCs specified SSH-2 standards. This standardization promoted interoperability between implementations and established SSH as the de facto standard for remote system administration. But an event would disrupt the ecosystem in 1999: the appearance of OpenSSH, a free implementation developed within the OpenBSD project. This free and open alternative accelerated the universal adoption of the protocol. OpenSSH quickly became the reference, integrated by default into most UNIX and Linux systems.
On the technical level, SSH relies on a hybrid approach combining asymmetric and symmetric cryptography. When establishing the connection, public-key mechanisms authenticate and exchange keys. Once the link is established, symmetric encryption takes over to protect data with better performance. The protocol introduced the "known hosts" mechanism: clients memorize the public keys of contacted servers, thus detecting any man-in-the-middle attack attempts. SSH also enabled tunneling of other TCP/IP protocols via port forwarding, considerably extending its scope of application.
The flexibility of SSH-2 allowed support for various authentication methods: passwords, public keys, host-based authentication. This adaptability made it possible to calibrate security according to contexts. Data compression and channel multiplexing optimized bandwidth usage, making the protocol even more efficient.
In the 2000s, SSH established itself as a key building block of Internet infrastructure. Its use extended far beyond remote access to encompass secure file transfer with SFTP, entire system management, and application deployment. Companies massively adopted it to secure their administrative operations. The protocol continued to evolve, integrating more recent cryptographic algorithms such as AES and elliptic curves. The developer community remained mobilized to adapt SSH to emerging threats and use cases.
SSH’s impact on modern computing remains considerable. As a practical and secure solution for remote administration, the protocol has accompanied the growth of the Internet and the explosion of cloud computing. Its modular design has inspired other security protocols. SSH remains ubiquitous in development environments, data centers, and cloud services. It illustrates how a technical response born from a specific incident can become an indispensable international standard.
SSH’s lasting success lies in its ability to combine robust security with ease of use. By automating cryptographic complexity while remaining accessible, the protocol has democratized security best practices in system administration.