SSH Reference Manual

Recovery: Reduce the number of identities (private keys) for the user presented by the SSH client. Usually,

this involves adding fewer keys to an SSH agent.

<session id>: public key authentication failed, invalid signature

Cause: The signature presented by the SSH client does not match the public key.

Effect: The authentication is rejected.

Recovery: Check the SSH client that presented the invalid signature.

<session id>: <authentication method> for user <user name> not supported

Is the authentication method requested by the SSH client

Is the name of the remote user.

Cause: The SSH client requested an authentication method that is not supported by SSH2 or has been

disallowed for this user.

Effect: The authentication is rejected.

Recovery: Use a supported authentication method with the SSH client. Check the settings for this user in the

SSH2 user base.

<session id>: channel request for subsystem sftp denied

Cause: SFTP is administratively disallowed for this user.

Effect: The channel request for the SFTP subsystem is rejected.

Recovery: Have the SSH client not use SFTP or grant SFTP access by setting the SFTP-SECURITY attribute

for the user to a value other than NONE.

<session id>: SFTPSERV process initialisation failed, could not chdir or chroot to

user's SFTP-INITIAL-DIRECTORY, error <error number>

Is the error number that was raised by the chdir or chroot operation.

Cause: Chdir or chroot failed when setting the user’s SFTP-INITIAL-DIRECTORY. A possible reason is that

the directory does not exist.

Effect: The channel request for the SFTP subsystem is rejected.

Recovery: Check the setting of SFTP-INITIAL-DIRECTORY for the relevant user.

<session id>: could not launch program <program name>, error <error number>, detail

Is the name of the program file that SSH2 tried to start.

Is the error number that was raised by the PROCESSCREATE function.

HP NonStop SSH Reference Manual Troubleshooting • 335