Installation Manual
OvNWAAAAgFf6pvWaco3CDELmH0jT3yUkRSaDztpqtoo4D7ev7VrNPPjnKKKmpzHPmAKRxz3g5S80SfWSnWM3n/pekBa9QI9lH1r
3Lx4JoOVwTpkbwb0by4eZ2cqDw20KQ0A5J84iQE9TbPNecJ0HJtZH/K8YnFNwwYy2NSJyjLwA0TSmQEOW Administrator
iLO legacy format
The iLO legacy format keys are OpenSSH keys surrounded by the BEGIN/END headers needed
for RIBCL. This format must be one line between the BEGIN SSH KEY and END SSH KEY text.
-----BEGIN SSH KEY-----
ssh-dss
AAAAB3NzaC1kc3MAAACBANA45qXo9cM1asav6ApuCREt1UvP7qcMbw+sTDrx9lV22XvonwijdFiOM/0VvuzVhM9oKdGMC7sCGQr
FV3zWDMJcIb5ZdYQSDt44X6bvlsQcAR0wNGBN9zHL6YsbXvNAsXN7uBM7jXwHwrApWVuGAI0QnwUYvN/dsE8fbEYtGZCRAAAAFQ
DofA47q8pIRdr6epnJXSNrwJRvaQAAAIBY7MKa2uH82I0KKYTbNMi0o5mOqmqy+tg5s9GC+HvvYy/S7agpIdfJzqkpHF5EPhm0j
KzzVxmsanO+pjju7lrE3xUxojevlokTERSCM xLa+OVVbNcgTe0xpvc/cF6ZvsHs0UWz6gXIMCQ9Pk118VMOw/tyLp42YXOaLZzG
fi5pKAAAAIEAl7FsO7sDbPj02a5jO3qFXa762lWvu5iPRZ9cEt5WJEYwMO/ICaJVDWVOpqF9spoNb53Wl1pUARJg1ss8Ruy7YBv
8Z1urWWAF3fYy7R/SlQqrsRYDPLM5eBkkLO28B8C6++HjLuc+hBvj90tsqeNVhpCfO9qrjYomYwnDC4m1IT4= ASmith
-----END SSH KEY-----
Note the following when working with SSH keys:
• The previously listed sample formats are supported with the iLO web interface and the CLI.
Only the iLO legacy format is supported with RIBCL scripts.
• Any SSH connection authenticated through the corresponding private key is authenticated
as the owner of the key and has the same privileges.
• The iLO firmware provides storage to accommodate SSH keys that have a length of 1366
bytes or less. If the key is larger than 1366 bytes, the authorization might fail. If a failure
occurs, use the SSH client software to generate a shorter key.
• If you use the iLO web interface to enter the public key, you select the user associated with
the public key. If you use the CLI to enter the public key, the public key is linked to the user
name that you entered to log in to iLO. If you use HPQLOCFG to enter the public key, you
append the iLO user name to the public key data. The public key is stored with that user
name.
More information
Authorizing a new SSH key by using the web interface
Authorizing a new SSH key by using the CLI
Administering SSL certificates
SSL protocol is a standard for encrypting data so that it cannot be viewed or modified while in
transit on the network. This protocol uses a key to encrypt and decrypt the data. Generally, the
longer the key, the better the encryption.
A certificate is a small data file that connects an SSL key to a server. It contains the name of the
server and the server's public key. Only the server has the corresponding private key, and this
is how it is authenticated.
A certificate must be signed to be valid. If it is signed by a CA, and that CA is trusted, all certificates
signed by the CA are also trusted. A self-signed certificate is one in which the owner of the
certificate acts as its own CA.
By default, iLO creates a self-signed certificate for use in SSL connections. This certificate enables
iLO to work without additional configuration steps. Importing a trusted certificate can enhance
the iLO security features. Users with the Configure iLO Settings privilege can customize and
import a trusted certificate that is signed by a CA.
Viewing SSL certificate information
To view certificate information, navigate to the Administration→Security→SSL Certificate
page.
74 Configuring the iLO security features