1-4
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. After successfully processing the request, the server sends
back to the client an SSH_SMSG_SUCCESS packet and goes on to the interaction 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.
Interaction
In this stage, the server and the client exchanges data in the following way:
z The client encrypts and sends the command to be executed to the server.
z The server decrypts and executes the command, and then encrypts and sends the result to the
client.
z The client decrypts and displays the result on the terminal.
z In the interaction stage, you can execute commands from the client by pasting the commands in
text format (the text must be within 2000 bytes). It is recommended that the commands are in the
same view; otherwise, the server may not be able to perform the commands correctly.
z If the command text exceeds 2000 bytes, you can execute the commands by saving the text as a
configuration file, uploading the configuration file to the server through Secure FTP (SFTP), and
then using the configuration file to restart the server.
Configuring the Device as an SSH Server
SSH Server Configuration Task List
Complete the following tasks to configure an SSH server:
Task Remarks
Generating a DSA or RSA Key Pair Required
Enabling the SSH Server Function Required
Configuring the User Interfaces for SSH Clients Required
Configuring a Client Public Key
Required for public key authentication users and
optional for password authentication users
Configuring an SSH User Optional
Setting the SSH Management Parameters Optional
Generating a DSA or RSA Key Pair
In the key and algorithm negotiation stage, the DSA or RSA key pair is required to generate the session
ID and for the client to authenticate the server.
To Next Page
Loading...
