SSH Communications Security
Previous Next Up [Contents] [Index]

    About This Document>>
    Introduction to SSH Secure Shell >>
    Configuring SSH Secure Shell >>
    Authentication >>
    Log Messages
        Log Message Reference >>
            User Authentication - Common
            User Authentication - Host-Based
            User Authentication - Keyboard-Interactive PAM
            User Authentication - Keyboard-Interactive Password
            User Authentication - Keyboard-Interactive
            User Authentication - Kerberos TGT
            User Authentication - Kerberos
            User Authentication - PAM
            User Authentication - Password
            User Authentication - Public Key
            User Authentication - SecurID
            Certificate-specific code
            SFTP Server
            Agent Forwarding
            Session Channels
            SSH1 Agent Forwarding
            Port Forwarding
            X11 Forwarding
            Common Code
            Host Key I/O
            General Server Log Messages
            SFTP
    Using SSH Secure Shell >>
    Tool Syntax>>
    Technical Specifications >>

User Authentication - Host-Based

Using host-based authentication denied for a host

Use of <filename> denied for <hostname>

Use of host-based authentication is denied for the host in server configuration.

Configuration files missing for host-based authentication

hostbased-authentication (rhosts) refused for <loginname> no .shosts 
or .rhosts files and no system-wide files (ie: /etc/shosts.equiv)

The required files for host-based authentication are missing.

Home directory missing in host-based authentication

hostbased-authentication (rhosts) refused for <loginname>: no
home directory <directory>

The user's home directory does not exist.

Home directory ownership or permissions invalid in host-based authentication

hostbased-authentication (rhosts) refused for <loginname>: bad
ownership or modes for home directory.

If the StrictModes option for the server is switched on, then this message means that the user's home directory is not owned by either the user or the root, or that its permission bits are not correct.

.rhosts file ownership or permissions invalid in host-based authentication

hostbased-authentication (rhosts) refused for <loginname>: bad
modes for <file>

If the StrictModes option for the server is switched on, then this message means that the user's .rhosts file is not owned either by the user or by the root, or that its permission bits are not correct.

Host-based authentication refused for user

hostbased-authentication (rhosts) refused: client user
<loginname>, server user <loginname>, client host <hostname>.

The host-based authentication attempt has failed.

Client's host certificate is not valid in host-based authentication

Hostbased: User <loginname>'s client host certificate not
valid.

The host certificate sent by the client during host-based authentication could not be successfully validated.

Client's host certificate does not contain host names in host-based authentication

Certificate does not contain any hostnames.

The host certificate sent by the client during host-based authentication does not contain any host names.

Certificate does not contain the client host name in host-based authentication

Certificate does not contain client hostname <hostname>.

The host certificate sent by the client during host-based authentication does not contain the client's host name.

Certificate could not be decoded in host-based authentication

Received certificate could not be decoded

The host certificate sent by the client during host-based authentication could not be decoded.

Public key could not be extracted from the received certificate in host-based authentication

Could not extract public key from received certificate

Extracting the public key from the received certificate failed during host-based authentication.

Cryptographic operation failed in host-based authentication

Hostbased: Crypto operation failed for public key (for user
<loginname>).

Changing the hashing scheme in the public key failed in host-based authentication.

Verifying the signature failed in host-based authentication

Hostbased authentication failed for <loginname>.

Verifying the signature failed in host-based authentication.

Host-based authentication successful

Hostbased authentication for user <loginname> accepted.

Authentication using the host-based authentication method succeeded for the user.

Root logins not permitted in host-based authentication

Root logins are not permitted.

The server has been configured not to allow root logins.

Could not decode packet in host-based authentication

Error decoding "hostbased" packet.

Decoding the host-based authentication protocol packet failed.

The host name given by the client does not match the one given by the client in host-based authentication

Client gave us a hostname (<hostname>) which doesn't match the
one we got from DNS (<hostname>) (sending failure)

The server has been configured to use strict host name checking and the host name gotten using reverse DNS lookup does not match the one in the host-based authentication packet.

The host name given by client does not match the one given by the client in host-based authentication, ignored

Client gave us a hostname (<hostname>) which doesn't match the
one we got from DNS (<hostname>) (trusting that client is valid, if
signature verification succeeds)

The host name gotten using reverse DNS lookup does not match the one in the host-based authentication packet, but the server does not require a match.

Invalid packet received in host-based authentication

Invalid packet. (extra data at end)

The received packet in host-based authentication contains extra data and will be discarded as invalid.

Client is using a public-key algorithm not supported by server in host-based authentication

Client's public key algorithms are not supported by us. (client
sent <algorithmname>)

The public key sent by the client in host-based authentication uses a public key algorithm not supported by the server.

User's .ssh2 directory is missing in host-based authentication

Couldn't find or create user <loginname>'s .ssh2 directory.

The user's .ssh2 directory could not be found or created in host-based authentication.

Received host key and stored host key differ in host-based authentication

The public key stored in %s and the one given by the client were
different.

The host key sent by the client and the one stored in the known host keys directory differ in host-based authentication.

Invalid client host key in host-based authentication

Importing client pubkey failed.

There was an error when decoding the host key sent by the client during host-based authentication.

Previous Next Up [Contents] [Index]


[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2003 SSH Communications Security Corp.
All rights reserved.
Copyright Notice