Secure Shell

From Wikipedia, the free encyclopedia

You have new messages (last change).
This article may require cleanup to meet Wikipedia's quality standards.
Please discuss this issue on the talk page or replace this tag with a more specific message.
This article has been tagged since April 2006.
The five layer TCP/IP model
5. Application layer

DHCP • DNS • FTP • HTTP • IMAP4 • IRC • NNTP • XMPP • MIME • POP3 • SIP • SMTP • SNMP • SSH • TELNET • BGP • RPC • RTP • RTCP • TLS/SSL • SDP • SOAP • L2TP • PPTP • …
4. Transport layer

TCP • UDP • DCCP • SCTP • GTP • …
3. Network layer

IP (IPv4 • IPv6) • ICMP • IGMP • RSVP • IPsec • …
2. Data link layer

ATM • DTM • Ethernet • FDDI • Frame Relay • GPRS • PPP • ARP • RARP • …
1. Physical layer

Ethernet physical layer • ISDN • Modems • PLC • SONET/SDH • G.709 • Wi-Fi • …
This box: view • talk • edit

In computing, Secure Shell or SSH is a set of standards and an associated network protocol that allows establishing a secure channel between a local and a remote computer. It uses public-key cryptography to authenticate the remote computer and (optionally) to allow the remote computer to authenticate the user. SSH provides confidentiality and integrity of data exchanged between the two computers using encryption and message authentication codes (MACs). SSH is typically used to log into a remote machine and execute commands, but it also supports tunneling, forwarding arbitrary TCP ports and X11 connections; it can transfer files using the associated SFTP or SCP protocols. An SSH server, by default, listens on the standard TCP port 22.

An ssh client program is typically used for establishing connections to an sshd daemon accepting remote connections. Both are commonly present on Unix-like systems, and implementations of SSH exist for most modern operating systems, including Sun OS, Mac OS, Linux-based distributions, Microsoft Windows, BSD operating systems (including Mac OS X), and OpenVMS. Commercial, freeware and open source versions of various levels of complexity and completeness exist.

Contents

[edit] History

In 1995, Tatu Ylönen, a researcher at Helsinki University of Technology, Finland, designed the first version of the protocol (now called SSH-1) prompted by a password-sniffing attack at his university network. The goal of SSH was to replace the earlier rlogin, TELNET and rsh protocols, which did not provide strong authentication or guarantee confidentiality. Ylönen released his implementation as freeware in July 1995, and the tool quickly gained in popularity. Towards the end of 1995, the SSH user base had grown to 20,000 users in fifty countries.

In December 1995, Ylönen founded SSH Communications Security to market and develop SSH. The original version of the SSH software used various pieces of free software, such as GNU libgmp, but later versions released by SSH Secure Communications evolved into increasingly proprietary software. SSH Communications Security subsequently relicensed SSH to F-Secure (formerly known as Data Fellows), who later sold it to WRQ (now Attachmate), who markets it under the name Reflection for Secure IT.[1] SSH Secure Communications has a USA subsidiary in Palo Alto, California.

In 1996, a revised version of the protocol, SSH-2, was designed, incompatible with SSH-1. SSH-2 features both security and feature improvements over SSH-1. Better security, for example, comes through Diffie-Hellman key exchange and strong integrity checking via MACs. New features of SSH-2 include the ability to run any number of shell sessions over a single SSH connection.[2]

In 1999, developers wanting a free software version to be available went back to the older 1.2.12 release of the original ssh program, which was the last released under an open source license. Björn Grönvall's OSSH was subsequently developed from this codebase. Shortly thereafter, OpenBSD developers forked Björn's code and did extensive work on it, creating OpenSSH, which shipped with the 2.6 release of OpenBSD. From this version, a "portability" branch was formed to port OpenSSH to other operating systems.

It is estimated that, at the end of 2000, there were 2,000,000 users of SSH.[3]

As of 2005, OpenSSH is the single most popular ssh implementation, coming by default in a large number of operating systems. OSSH meanwhile has become obsolete.[4]

In 2006, the aforementioned SSH-2 protocol became a proposed Internet standard with the publication by the IETF "secsh" working group of RFCs (see references).

[edit] Uses of SSH

Example of tunneling an X11 application (xeyes) over SSH.
Example of tunneling an X11 application (xeyes) over SSH.

SSH is most commonly used:

  • with an SSH client that supports terminal protocols, for remote administration of the SSH server computer via terminal (character-mode) console--can be used as an alternative to a terminal on a headless server;
  • in combination with SFTP, as a secure alternative to FTP which can be set up more easily on a small scale without a public key infrastructure and X.509 certificates;
  • in combination with rsync to backup, copy and mirror files efficiently and securely
  • in combination with SCP, as a secure alternative for rcp file transfers—more often used in environments involving Unix
  • for port forwarding or tunneling, frequently as an alternative to a full-fledged VPN. In this type of use, a (non-secure) TCP/IP connection of an external application is redirected to the SSH program (client or server), which forwards it to the other SSH party (server or client), which in turn forwards the connection to the desired destination host. The forwarded connection is encrypted and protected on the path between the SSH client and server only. Uses of SSH port forwarding include accessing database servers, email servers, securing X11, Windows Remote Desktop and VNC connections or even forwarding Windows file shares. This is primarily useful for tunneling connections through firewalls which would ordinarily block that type of connection, and for encrypting protocols which are not normally encrypted (e.g. VNC).
  • ssh and rdesktop. Three computers, the computer that will run rdesktop and ssh, a computer used to obtain access to a remote network, and the last will be the computer you want rdesktop to display. "ssh -L3389:<computer name of desktop to be displayed>:3389 <computer used to obtain remote network access>". Just log into the middle computer and do nothing on it. Open another shell from the first computer running ssh and type rdesktop localhost. This example uses the middle computer to port forward 3389 from the end computer to the first computer.
  • Sometimes you may log into one machine from your local host, then login from there to another machine, and run an X application (eg. xterm, matlab) on the last machine to display on your local display. This is especially useful for running X applications on a department host from off campus but to which you have had to connect through another department host which is available for ssh login through the campus firewall. Essentially, you want to channel the X-window through a series of logins back to the host at which you are sitting. The best way to do this is to make use of the X11-forwarding feature of ssh. For unix/linux to unix/linux, force an X11-forwarding request with the '-X' option (capitalized x). ssh -X host.com
  • X11-forwarding for through multiple hosts ssh -X hostA.com --> ssh -X hostB.com --> ssh -X hostC.com insure the tunnel is working every step of the way by running something like xterm on host B then C. If this does not work the -Y may be needed. ssh -X -Y hostA.com --> ssh -X -Y hostB.com --> ssh -X -Y hostC.com
  • with an SSH client that supports dynamic port forwarding (presenting to other programs a SOCKS or HTTP 'CONNECT' proxy interface), SSH can even be used for generally browsing the web through an encrypted proxy connection, using the SSH server as a proxy;
  • with an SSH client that supports SSH exec requests (frequently embedded in other software, e.g. a network monitoring program), for automated remote monitoring and management of servers.
  • Using just a normal ssh login on a server, the SSH Filesystem can securely mount a directory on the server as a filesystem on the local computer.

[edit] SSH architecture

Diagram of the SSH-2 binary packet.
Diagram of the SSH-2 binary packet.

The SSH-2 protocol has a clean internal architecture (defined in RFC 4251) with well-separated layers. These are:

  • The transport layer (RFC 4253). This layer handles initial key exchange and server authentication and sets up encryption, compression and integrity verification. It exposes to the upper layer an interface for sending and receiving plaintext packets of up to 32,768 bytes each (more can be allowed by the implementation). The transport layer also arranges for key re-exchange, usually after 1 GB of data has been transferred or after 1 hour has passed, whichever is sooner.
  • The user authentication layer (RFC 4252). This layer handles client authentication and provides a number of authentication methods. Authentication is client-driven, a fact commonly misunderstood by users; when one is prompted for a password, it may be the SSH client prompting, not the server. The server merely responds to client's authentication requests. Widely used user authentication methods include the following:
    • "password": a method for straightforward password authentication, including a facility allowing a password to be changed. This method is not implemented by all programs.
    • "publickey": a method for public key-based authentication, usually supporting at least DSA or RSA keypairs, with other implementations also supporting X.509 certificates)
    • "keyboard-interactive" (RFC 4256): a versatile method where the server sends one or more prompts to enter information and the client displays them and sends back responses keyed-in by the user. Used to provide one-time password authentication such as S/Key or SecurID. Used by some OpenSSH configurations when PAM is the underlying host authentication provider to effectively provide password authentication, sometimes leading to inability to log in with a client that supports just the plain "password" authentication method.
    • GSSAPI authentication methods which provide an extensible scheme to perform SSH authentication using external mechanisms such as Kerberos 5 or NTLM, providing single sign on capability to SSH sessions. These methods are usually implemented by commercial SSH implementations for use in organizations, though OpenSSH does have a working GSSAPI implementation.
  • The connection layer (RFC 4254). This layer defines the concept of channels, channel requests and global requests using which SSH services are provided. A single SSH connection can host multiple channels simultaneously, each transferring data in both directions. Channel requests are used to relay out-of-band channel specific data, such as the changed size of a terminal window or the exit code of a server-side process. The SSH client requests a server-side port to be forwarded using a global request. Standard channel types include:
    • "shell" for terminal shells, SFTP and exec requests (including SCP transfers)
    • "direct-tcpip" for client-to-server forwarded connections
    • "forwarded-tcpip" for server-to-client forwarded connections

This open architecture provides considerable flexibility, allowing SSH to be used for a variety of purposes beyond secure shell. The functionality of the transport layer alone is comparable to TLS; the user authentication layer is highly extensible with custom authentication methods; and the connection layer provides the ability to multiplex many secondary sessions into a single SSH connection, a feature comparable to BEEP and not available in TLS.

[edit] Security cautions

Since SSH-1 has inherent design flaws which make it vulnerable to, e.g., man in the middle attacks, it is now generally considered obsolete and should be avoided by explicitly disabling fallback to SSH-1. While most modern servers and clients support SSH-2, some organizations still use software with no support for SSH-2 making it hard to avoid the use of SSH-1.

In all versions of SSH, it is important to verify unknown public keys before accepting them as valid. Accepting an attacker's public key as a valid public key has the effect of disclosing the transmitted password and allowing man in the middle attacks.

As with any encrypted protocol SSH can be considered a security risk by companies or governments who do not trust their users. Furthermore SSH has built in tunneling features which make it easier for users to achieve passage of large volumes of information or to establish an entry point for unauthorized inward access over a SSH link than with other protocols.

[edit] How SSH uses public-key cryptography (with analogy)

Main article: Public-key cryptography

First, a pair of cryptographic keys is generated. One is the private key, the other is the public key. As an analogy, they can be thought of as a matching private-key and a public padlock. The public padlock is what is installed on the remote machine and is used by ssh to authenticate users which use the matching private key. As a user of the system, you don’t care who can see or copy the padlock (ie the public key), since only the secret private key fits it. The private key is the part you keep secret inside a secure box that can only be opened with the correct passphrase. When the user wants to access a remote system, he opens the secure box with his passphrase, and uses the private-key to authenticate him with the padlock on the remote computer. Neither the passphrase nor the private key leave the user's machine. However, the user still needs to trust the local machine not to scrape his passphrase or copy his private-key while it's out of the secure box.

[edit] See also

Portal:Cryptography
 Cryptography Portal

[edit] References

Wikibooks
Wikibooks has a book on the topic of
  1. ^ http://www.attachmate.com/en-US/Products/Security/Reflection+for+Secure+IT/
  2. ^ http://www.snailbook.com/faq/ssh-1-vs-2.auto.html
  3. ^ Nicholas Rosasco and David Larochelle. How and Why More Secure Technologies Succeed in Legacy Markets: Lessons from the Success of SSH. Quoting Barrett and Silverman, SSH, the Secure Shell: The Definitive Guide, O'Reilly & Associates (2001). Dept. of Computer Science, Univ. of Virginia. Retrieved on 2006-05-19.
  4. ^ https://www.kb.cert.org/vuls/id/MIMG-6L4LBL

[edit] External links

The external links in this article may require cleanup to comply with Wikipedia's content policies.
Please improve this article by removing excessive or inappropriate external links. Please remove this tag when this is done. (talk)

This article was originally based on material from the Free On-line Dictionary of Computing, which is licensed under the GFDL.

Retrieved from "http://en.wikipedia.org../../../s/e/c/Secure_Shell_c755.html"