3Com Switch 8800 Advanced Software V5 Configuration Guide

SSH2.0 Overview 939
n
Besides password authentication and RSA authentication, SSH2.0 provides
another two authentication methods:
■ password-publickey: Performs both password authentication and publickey
authentication of the client. A client running SSH1 client only needs to pass
either type of the two, while a client running SSH2 client must pass both of
them to login.
■ all: Set the authentication mode to either "password" or "RSA". Clients will
attempt to log in through RSA first.
Session request
After passing authentication, the client sends a session request to the server, while
the server listens to and processes the request from the client. If the client passes
authentication, the server sends back to the client an SSH_SMSG_SUCCESS packet
and goes on to the interactive session stage with the client. Otherwise, the server
sends back to the client an SSH_SMSG_FAILURE packet, indicating that the
processing fails or it cannot resolve the request.
Interactive session
After a session is assigned successfully, the connection enters the interactive
session mode. In this stage, the server and the client exchanges data in this way:
■ The client encrypts and sends the command to be executed to the server.
■ The server decrypts and executes the command, and then encrypts and sends
the result to the client.
■ The client decrypts and displays the result on the terminal.
n
■ During interactive session, the client can send the commands to be performed
by pasting the text, which must be within 2000 bytes (including spaces). It is
recommended that the text pasted be commands in the same view; otherwise,
the server may not be able to perform the commands.
■ If the text exceeds 2000 bytes, you can upload the configuration file to the
server and use the configuration file to restart the server so that the server
executes the commands.