SSH

User Authentication - Public Key

Certificate not authorized for login

Authorization check for user <login-name>'s certificate rejected[, reason: <error-message>].

Level: warning

Facility: AUTH

The server's authorization check for the certificate produced a negative result, meaning that public-key authentication with this certificate is denied.

Error in public key decoded from certificate

Couldn't get info from certificate public key used by user <login-name>.

Level: warning

Facility: AUTH

After extracting the public key from the received certificate, the server could not get the public key information from the public key.

Key length too small in certificate

Use of certificate for user <login-name> is not allowed, because public key is too small (pk size <key-size>, min size <minimum-size>).

Level: warning

Facility: AUTH

The server has rejected the authentication using the certificate sent by the client, because the public key in the certificate is too short.

Key length too large in certificate

Use of certificate for user <login-name> is not allowed, because public key is too large (pk size <key-size>, max size <maximum-size>).

Level: warning

Facility: AUTH

The server has rejected the authentication using the certificate sent by the client because the public key in the certificate is too long.

Signature check failed

Signature verify failed for certificate from user <login-name>.

Level: warning

Facility: AUTH

The signature verification failed for the user in certificate authentication.

Certificate authentication accepted

Certificate authentication for user <login-name> accepted.

Level: notice

Facility: AUTH

The server has accepted the certificate authentication for the user.

Certificate authentication rejected

Certificate authentication for user <login-name> rejected.

Level: warning

Facility: AUTH

The server has rejected the certificate authentication for the user.

Public key options prohibit using the key

Use of public key <key-name> is not allowed in public key options for the host the user <login-name> is logging in from.

Level: notice

Facility: AUTH

Using the public key for the user and host has been denied based on the public key options set on the server for the key.

Error in public key

Couldn't get info from public key <key-name> used by user <login-name>.

Level: warning

Facility: AUTH

The server could not get the public key information from the public key.

Key length too small

Use of public key <key-name> by user <login-name> is not allowed, because public key is too small (pk size <key-size>, min size <minimum-size>).

Level: warning

Facility: AUTH

The server has rejected the authentication using the public key sent by the client because the key is too short.

Key length too large

Use of public key <key-name> by user <login-name> is not allowed, because public key is too large (pk size <key-size>, max size <maximum-size>).

Level: warning

Facility: AUTH

The server has rejected the authentication using the public key sent by the client because the key is too long.

Cryptographic operation failed for RSA key

Crypto operation failed for RSA key of user <login-name>.

Level: warning

Facility: AUTH

A cryptographic operation failed for an RSA key.

Root login permitted for forced command

root login permitted for forced command.

Level: notice

Facility: AUTH

The server has been configured to not allow root (administrator) logins, but will allow forced commands as root.

Public-key authentication accepted

Public key authentication for user <login-name> accepted.

Level: notice

Facility: AUTH

The server has accepted the public-key authentication for the user.

Bad packet when verifying key

got bad packet when verifying user <login-name>'s publickey.

Level: warning

Facility: AUTH

The server received an invalid packet when trying to verify the user's public key.

Public key is authorized

Public key <filename> authorized for user <login-name>, verifying signature.

Level: notice

Facility: AUTH

The server has determined that the public key supplied by the client is authorized for logging in, and will now verify the signature supplied by the client.

User's public key logged with fingerprint

User authorized by public key: <key-comment>, fingerprint: <key-fingerprint>

Level: informational

Facility: AUTH

The server logs the user's public key fingerprint.

User's public key logged, fingerprint not created

User authorized by public key (could not create a fingerprint): <key-comment>: <key-data>

Level: informational

Facility: AUTH

The server was unable to create the user's public key fingerprint when logging the user's public key.