2011 Ericsson AB. All Rights Reserved. The program may be used and/or copied only with the written permission from Ericsson AB, or in accordance with the terms and conditions stipulated in the agreement/contract under which the program has been supplied. SSH OTP A ssh_ug.xml
Introduction

The Secure Shell (SSH) is a transport protocol. For more detailed information, see the following RFCs:

RFC 4250 - Protocol Assigned Numbers. RFC 4251 - Protocol Architecture. RFC 4252 - Authentication Protocol. RFC 4253 - Transport Layer Protocol. RFC 4254 - Connection Protocol. RFC 4255 - Key Fingerprints. RFC 4344 - Transport Layer Encryption Modes. RFC 4716 - Public Key File Format.

The SSH application is an implementation of the SSH protocol in Erlang. Conceptually it can be partitioned into four layers:

SSH Protocol Dependencies
Overview

The SSH application supports:

Subsystem - user-named services such as ssh_sftp. The user can also add other subsystems (e.g. NETCONF). Shell - interactive shell. Exec - one-time remote execution (i.e. SCP). See ssh_connection:exec/4
Configuration and Start

Before the SSH application can be used, there are two things that must be fulfilled:

The Crypto application is started before SSH is. The Public_key application is loaded when running an embedded system.
Server Side

When SSH is supposed to run as server, the function ssh:daemon/[1, 2, 3] needs to be used to start the daemon.

Client Side

The client.