Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Authentication >>
    File Transfer Using SFTP >>
    Secure File Transfer Using Transparent FTP Security >>
    Tunneling >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Man Pages and Default Configuration Files >>
    Log Messages
        Log Message Reference >>
            User Authentication - Common
            User Authentication - Host-Based
            User Authentication - Keyboard-Interactive Password
            User Authentication - Keyboard-Interactive
            User Authentication - Password
            User Authentication - Public Key
            Certificate-Specific Code
            Agent Forwarding
            Session Channels
            SSH1 Agent Forwarding
            Port Forwarding
            Common Code
            Host Key I/O
            General Server Log Messages
            SFTP

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

.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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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

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

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

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

Certificate does not contain the client hostname 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 hostname.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_NOTICE

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_NOTICE

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

Verifying the signature failed in host-based authentication

Hostbased authentication failed for <loginname>.

Verifying the signature failed in host-based authentication.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

Host-based authentication successful

Hostbased authentication for user <loginname> accepted.

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

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_NOTICE

Could not decode packet in host-based authentication

Error decoding "hostbased" packet.

Decoding the host-based authentication protocol packet failed.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

The hostname 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 hostname checking and the hostname obtained using reverse DNS lookup does not match the one in the host-based authentication packet.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

The hostname 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 hostname obtained using reverse DNS lookup does not match the one in the host-based authentication packet, but the server does not require a match.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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

The public key stored in <filename> 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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

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.

Facility: SSH_LOGFACILITY_AUTH

Level: SSH_LOG_WARNING

PreviousNextUp[Contents] [Index]


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

Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice

===AUTO_SCHEMA_MARKUP===