Displaying And Maintaining Ssh Configuration - 3Com 5500-EI PWR Install Manual

Start the client to establish a
connection with an SSH server
When logging into the SSH server using public key authentication, an SSH client needs to read its local
private key for authentication. As two algorithms (RSA or DSA) are available, the identity-key keyword
must be used to specify one algorithm in order to get the correct private key.

Displaying and Maintaining SSH Configuration

To do...
Display the
information
switch's key pairs
Display information
locally saved public keys of
SSH peers
Display information about SSH
status and about sessions of
active connections with SSH
clients
Display information about all
SSH users
Display the current source IP
address or the IP address of
the source interface specified
for the SSH server.
ssh2 { host-ip | host-name }
[ port-num ] [ identity-key { dsa
| rsa } | prefer_kex
{ dh_group1 |
dh_exchange_group } |
prefer_ctos_cipher { 3des |
des | aes128 } |
prefer_stoc_cipher { 3des |
des | aes128 } |
prefer_ctos_hmac { sha1 |
sha1_96 | md5 | md5_96 } |
prefer_stoc_hmac { sha1 |
sha1_96 | md5 | md5_96 } ] *
public key
display public-key local { dsa | rsa }
of the current
public
about
display public-key peer [ brief | name
pubkey-name ]
display ssh server { session | status }
display
[ username ]
display ssh-server source-ip
Use the command...
ssh user-information
1-25
Required
In this command, you can also
specify the preferred
exchange algorithm, encryption
algorithms and
algorithms between the server
and client.
HMAC: Hash-based message
authentication code
Note that:
The identity-key keyword is
unnecessary in password
authentication and optional
in public key authentication.
Support for the
keyword depends on the
number of encryption bits of
the software version. The
168-bit version supports this
keyword, while the 56-bit
version does not.
Remarks
Available in any view
key
HMAC
3des