Cisco Cisco Email Security Appliance C390 사용자 가이드
5-219
Cisco IronPort AsyncOS 7.3 for Email Daily Management Guide
OL-23080-01
Chapter 5 Logging
Log Subscriptions
Configuring Host Keys
Use the
logconfig -> hostkeyconfig
subcommand to manage host keys for use
with SSH when pushing logs to other servers from the IronPort appliance. SSH
servers must have a pair of host keys, one private and one public. The private host
key resides on the SSH server and cannot be read by remote machines. The public
host key is distributed to any client machine that needs to interact with the SSH
server.
servers must have a pair of host keys, one private and one public. The private host
key resides on the SSH server and cannot be read by remote machines. The public
host key is distributed to any client machine that needs to interact with the SSH
server.
Note
To manage user keys, see
The
hostkeyconfig
subcommand performs the following functions:
Table 5-35
Managing Host Keys - List of Subcommands
Command
Description
New
Add a new key.
Edit
Modify an existing key.
Delete
Delete an existing key.
Scan
Automatically download a host key.
Print
Display a key.
Host
Display system host keys. This is the value to place in the
remote system's ‘known_hosts’ file.
remote system's ‘known_hosts’ file.
Fingerprint
Display system host key fingerprints.
User
Display the public key of the system account that pushes the
logs to the remote machine. This is the same key that is
displayed when setting up an SCP push subscription. This is
the value to place in the remote system's 'authorized_keys'
file.
logs to the remote machine. This is the same key that is
displayed when setting up an SCP push subscription. This is
the value to place in the remote system's 'authorized_keys'
file.
In the following example, AsyncOS scans for host keys and add them for the host:
mail3.example.com> logconfig