Table of Contents
Advertisement
Media Flow Manager Administrator's Guide
ssh
Configure your SSH client and server.
ssh client
Configure SSH (secure sockets shell) client options.
ssh client
global
host-key-check {ask | no | yes}
known-host <known_host_entry>
user {<username> | admin | cmcrendv | monitor}
authorized-key sshv2 <public_key>
identity {<key_type> | rsa2 | dsa2}
known-host <IP_address> [remove]
Notes:
•
global
•
host-key-check
done. Use no to disable host key checking. Arguments:
•
•
•
•
known-host <known_host_entry>
known-hosts configuration file.
•
user <username>
•
authorized-key sshv2 <public_key>
authorized SSHv2 RSA or DSA public keys for this user account. These keys can be
used to log into the user's account. The specified user must be a valid account on the
system. As keys are added, an implicit ID is associated with the key; this is to make
key deletion easier. Note if a key is pasted from a cut buffer and displayed with a
paging program, it is likely that newline characters have been inserted, even if the
output was not long enough to require paging; most show command output is
displayed this way, as paging is enabled by default in the CLI. Specify no cli session
paging enable before doing the show command to prevent the newlines from being
inserted. Use no ssh client user <username> authorized-key sshv2 <key_id> to
delete a public key from the specified user's authorized key list. The key identifier can
be found with show ssh client.
•
identity <key_type>
•
generate
private-key [<key>]
public-key <key>
—Configure global SSH client settings.
—Set SSH client configuration to control how host key checking is
—Prompt the user to accept new host keys, but disallow connection if there is
ask
already a known host entry that does not match the one presented by the host.
—Accept unknown keys and add them to the relevant known hosts file.
no
—Only permit connections if a matching host key is in the known hosts file.
yes
—Configure an SSH user.
—Set SSH client identity options for the specified user.
—Generate a new identity (private and public keys) for the specified
generate
user name. The given user name must correspond to a valid local user account.
When the keys are generated, the private key is written to the user's .ssh directory
in an appropriately named file (for example, id_dsa). This identity can be used
—Add or delete (with no) an entry to the global
—The specified key is added to the list of
CHAPTER 5 CLI Commands
ssh
139
Advertisement
Table of Contents
