User Authentication - PAM
Malformed packet from PAM subprocess
auths-pam: PAM subprocess sent a malformed packet. (packet type:
%d)
The server received a malformed packet from the PAM subprocess.
Wrong packet received from PAM subprocess
auths-pam: PAM subprocess returned packet
SSH_PAM_OP_SUCCESS_WITH_PAYLOAD, expecting SSH_PAM_OP_SUCCESS.
The PAM subprocess sent a packet of wrong type.
Error returned by PAM subprocess
kbd-int:pam: PAM subprocess returned packet
<packet-type>. (err_num: <errornumber>, err_msg:
<error-message)
The PAM subprocess returned an error.
Invalid packet type returned by PAM subprocess
auths-pam: PAM subprocess returned packet %d, which is
invalid.
The packet type returned by the PAM subprocess was invalid.
Client sent response packet prematurely
auths-pam: client sent response packet, and we weren't expecting
any (yet).
The client sent a response packet prematurely.
Client sent invalid packet
auths-pam: client sent invalid packet as a response to our
conversation message.
The client sent an invalid packet.
Client sent continuation packet when expecting start packet
Client sent continuation packet when expecting start packet for
PAM-auth..
The client sent continuation packet when the server was expecting a
start packet.
Extra data in SSH_MSG_USERAUTH_REQUEST packet from client
Extra data at end of SSH_MSG_USERAUTH_REQUEST packet for PAM
authentication.
Extraneous data was included in the SSH_MSG_USERAUTH_REQUEST packet
received from client.
Pipe creation failed in PAM authentication
ssh_server_auth_pam: pipe creation failed.
The forking and pipe creation to the subprocess failed in PAM
user authentication.
Error happened during the PAM transaction
PAM transaction resulted in error.
There was an error during the PAM transaction.