CONTENTS

LIBRARY

SYNOPSIS

struct pam_response {
char *resp;
int resp_retcode;
};

The conversation function’s first argument specifies the number of messages (up to PAM_NUM_MSG) to process. The second argument is a pointer to an array of pointers to
.Vt pam_message structures containing the actual messages.

Each message can have one of four types, specified by the msg_style member of
.Vt struct pam_message :

In each case, the prompt or message to display is pointed to by the msg member of
.Vt struct pam_message . It can be up to PAM_MAX_MSG_SIZE characters long, including the terminating NUL.

On success, the conversation function should allocate and fill a contiguous array of
.Vt struct pam_response , one for each message that was passed in. A pointer to the user’s response to each message (or NULL in the case of informational or error messages) should be stored in the resp member of the corresponding
.Vt struct pam_response . Each response can be up to PAM_MAX_RESP_SIZE characters long, including the terminating NUL.

The resp_retcode member of
.Vt struct pam_response is unused and should be set to zero.

The conversation function should store a pointer to this array in the location pointed to by its third argument. It is the caller’s responsibility to release both this array and the responses themselves, using free(3). It is the conversation function’s responsibility to ensure that it is legal to do so.

The appdata_ptr member of
.Vt struct pam_conv is passed unmodified to the conversation function as its fourth and final argument.

SEE ALSO

STANDARDS

AUTHORS