Let PAM to provision users on their first login

Nico Williams nico at cryptonector.com
Sat Nov 21 15:15:24 AEDT 2026


On Fri, Nov 20, 2026 at 08:03:06PM -0700, David Lang via openssh-unix-dev wrote:
> Nico Williams wrote:
> > What is a serious problem is that none of this will work for anything
> > other than password or keyboard-interactive userauth because the point
> > is that either the PAM/NSS modules will need user credentials, or an
> > interactive user account sign-up is involved, and the former can't work
> > with non-interactive userauth due to limitations of those userauth
> > methods and/or limitations of PAM, and the latter is strictly
> > interactive and requires keyboard-interactive userauth.
> 
> even if it only works for userid/password, getting an account setup with one
> userid/password manual login and then being able to use other credentials
> for automated access after that seems a bit step forward.

Yes, but it's not super compelling.

Replacing PAM, or giving it a thorough working over along the lines I
described earlier is much more compelling, yet no one has bothered.

I tried adding PAM_GSS_NAME and PAM_GSS_DELEG_CRED items at Sun circa
2007, but PSARC did not like that the values would be opaque GSS-API
objects where GSS-API did not have functions for duplicating/referencing
them, and I ran out of time when a different project (ID mapping for
ZFS/Windows interop) came along.  Eventually we did add better "export"
functions to GSS-API to deal with this, but then too GSS-API and
Kerberos are basically dying and should die.  PSARC was right, but also
we really need to do more than merely let the app pass information about
how non-interactive authentication was done.  Basically, PAM was
obsolete as designed when it came out, and that's holding everything
back.

Nico
-- 


More information about the openssh-unix-dev mailing list