You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's what I was thinking in terms of implementation:
In the call to pam_start, for the second parameter, provide user (the string passed in to the function call). That will automatically set the PAM_USER item1.
Once you have the PAM handle, call pam_set_item to set the PAM_AUTHTOK item type to be the user's password (the pass string passed into the function call).2
For PAM stacks to take advantage of it, modules which prompt for a password (like pam_unix) would have to be invoked with the try_first_pass or use_first_pass option, but for pam_unixtry_first_pass is the default already.
If all of this works, then a successful authentication will not require invoking the conversation function.
Please let me know if you have any questions about my request!
The text was updated successfully, but these errors were encountered:
The pam_start(() change you mention was addressed by #1883.
The pam_set_item(,PAM_AUTHTOK,) call can't be done from an application as you request. This is raised on stackoverflow but not adequately answered. For that we need to look at the code for linux-PAM. The relevent code from pam_set_item() is here:-
Hello!
I'd like to request that
PAM_USER
andPAM_AUTHTOK
both be set withinauth_userpass
(in https://github.com/neutrinolabs/xrdp/blob/devel/sesman/verify_user_pam.c). This will allow basic PAM stacks to run possibly without the need for prompting for a username/password in the conversation mechanism.Here's what I was thinking in terms of implementation:
pam_start
, for the second parameter, provideuser
(the string passed in to the function call). That will automatically set thePAM_USER
item1.pam_set_item
to set thePAM_AUTHTOK
item type to be the user's password (thepass
string passed into the function call).2For PAM stacks to take advantage of it, modules which prompt for a password (like
pam_unix
) would have to be invoked with thetry_first_pass
oruse_first_pass
option, but forpam_unix
try_first_pass
is the default already.If all of this works, then a successful authentication will not require invoking the conversation function.
Please let me know if you have any questions about my request!
The text was updated successfully, but these errors were encountered: