Secure Shell (ssh)
Return to Linux commands, Cloud shells
- Snippet from Wikipedia: Secure Shell
The Secure Shell (SSH) Protocol is a cryptographic network protocol for operating network services securely over an unsecured network. Its most notable applications are remote login and command-line execution.
SSH was designed for Unix-like operating systems as a replacement for Telnet and unsecured remote Unix shell protocols, such as the Berkeley Remote Shell (rsh) and the related rlogin and rexec protocols, which all use insecure, plaintext methods of authentication, like passwords.
Since mechanisms like Telnet and Remote Shell are designed to access and operate remote computers, sending the authentication tokens (e.g. username and password) for this access to these computers across a public network in an unsecured way, poses a great risk of 3rd parties obtaining the password and achieving the same level of access to the remote system as the telnet user. Secure Shell mitigates this risk through the use of encryption mechanisms that are intended to hide the contents of the transmission from an observer, even if the observer has access to the entire data stream.
Finnish computer scientist Tatu Ylönen designed SSH in 1995 and provided an implementation in the form of two commands, ssh and slogin, as secure replacements for rsh and rlogin, respectively. Subsequent development of the protocol suite proceeded in several developer groups, producing several variants of implementation. The protocol specification distinguishes two major versions, referred to as SSH-1 and SSH-2. The most commonly implemented software stack is OpenSSH, released in 1999 as open-source software by the OpenBSD developers. Implementations are distributed for all types of operating systems in common use, including embedded systems.
SSH applications are based on a client–server architecture, connecting an SSH client instance with an SSH server. SSH operates as a layered protocol suite comprising three principal hierarchical components: the transport layer provides server authentication, confidentiality, and integrity; the user authentication protocol validates the user to the server; and the connection protocol multiplexes the encrypted tunnel into multiple logical communication channels.
Terminals: CLI - Command-Lines Interfaces, Shell (Bash Shell, ZShell), Linux Terminals (SSH, Secure Shell, Telnet, Fedora Terminal, Ubuntu Terminal), Windows Terminals (Microsoft Windows Terminal, PowerShell Terminal, Windows Command Prompt - cmd.exe), macOS Terminals (Warp.dev Warp Terminal, iTerm2, tmux, macOS Terminal,), IBM Mainframe Terminals, (3270, TN3270), GitHub Terminals, Awesome Terminals. (navbar_terminal - see also navbar_commandline)
Command-Line: Shell, Shell Hacks, Console, Terminal, Shell, Command-Line Tools, Docker Command-Line, Podman Command-Line, Kubernetes Command-Line, Linux Command-Line, Unix Command-Line, macOS Command-Line, Windows Command-Line, Windows Server Command-Line, Android Command-Line, Linux Terminal, macOS Terminal, Windows Terminal, Package Manager Command-Line, PowerShell Core, PowerShell, SSH, Command Prompt - Command Line - Command Line Interface - CLI, Cloud Shell - Azure Cloud Shell - AWS Cloud Shell - GCP Cloud Shell, Azure CLI, Azure PowerShell, AWS PowerShell, GCP PowerShell, Linux PowerShell, macOS PowerShell, REPL, Python interactive shell (navbar_commandline - see also navbar_terminal)
© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers
SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.