Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Use the 

logconfig -> hostkeyconfig

 subcommand to manage host keys for use with SSH when 

pushing logs to other servers from the Email Security 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.

To manage user keys, see 

The 

hostkeyconfig

 subcommand performs the following functions:

In the following example, AsyncOS scans for host keys and add them for the host:

Mon Feb 21 12:25:10 2011 Info: PID 274: User system commit changes: Automated Update for 

Quarantine Delivery Host

Mon Feb 21 23:18:10 2011 Info: PID 19626: User admin commit changes:

Mon Feb 21 23:18:10 2011 Info: PID 274: User system commit changes: Updated filter logs 

config

Mon Feb 21 23:46:06 2011 Info: PID 25696: User admin commit changes: Receiving 

suspended.

mail3.example.com>

Description

Add a new key.

Modify an existing key.

Delete an existing key.

Automatically download a host key.

Display a key.

Display system host keys. This is the value to place in the remote system's 
‘known_hosts’ file.

Display system host key fingerprints.

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. 

mail3.example.com> logconfig

Currently configured logs: