Media Flow Controller CLI Commands
Media Flow Controller Administrator’s Guide
356
ssh client
Copyright © 2010, Juniper Networks, Inc.
•
ask
—Prompt the user to accept new host keys, but disallow connection if there is
already a known host entry that does not match the one presented by the host.
•
no
—Accept unknown keys and add them to the relevant known hosts file.
•
yes
—Only permit connections if a matching host key is in the known hosts file.
•
known-host <known_host_entry>
—Add or delete (with no) an entry to the global
known-hosts configuration file.
•
user <username>
—Configure an SSH user.
•
authorized-key sshv2 <public_key>
—The specified key is added to the list of
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. 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>
—Set SSH client identity options for the specified user.
•
generate
—Generate a new identity (private and public keys) for the specified
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
when the user connects from the system to another host with slogin. DSA and
RSA v2 keys for SSHv2 can be generated using dsa2 or rsa2 as the key-type.
•
private-key
—Set private key SSH client identity for the specified user. An
optional passphrase may be specified for the private key.
•
public-key
—Set public key SSH client identity for the specified user.
Set the public or private key of specified type for the specified user name. This is
an alternative to generating the key with the generate command and is also used
for reverse mapping generated keys. If the private-key command is used with no
key given, the user is prompted for the key. Entries made at this prompt echo the
asterisk (*) character, and the user must enter the same string twice. Use no ssh
client user <username> identity <key_type> to delete the public/private keys
for the specified user; any private key file in a valid user .ssh directory is deleted.
•
known-host <IP_address> remove
—Delete a known host from the specified
user's .ssh known_hosts file.
show ssh client
SSH client identities (public/private keys) and the per user list of authorized keys for the users.
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
