Date: Thu, 07 Mar 2002 10:17:11 +0000 From: Mark Murray <mark@grondar.za> To: "Brian F. Feldman" <green@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libpam/modules modules.inc src/lib/libpam/modules/pam_alreadyloggedin Makefile pam_alreadyloggedin.8 pam_alreadyloggedin.c Message-ID: <200203071017.g27AHBRV008209@grimreaper.grondar.org> In-Reply-To: <200203070015.g270F4A43670@green.bikeshed.org> ; from "Brian F. Feldman" <green@FreeBSD.org> "Wed, 06 Mar 2002 19:15:04 EST." References: <200203070015.g270F4A43670@green.bikeshed.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Mark Murray <mark@grondar.za> wrote: > > I suspect that the pam_self module should take the responsibility > > for doing what this does, probably with the assistance of some > > appropriate options. > > I'm not sure; I think it's probably worth keeping them logically separate > since they don't perform very similar actions, although they allow a > somewhat similar policy to be implemented. The actions are not as important (in this case) as the policy. Remember that PAM is a policy tool, and the more you can bundle appropriate policy together for the sysadmin, the easier you make her life. :-) > > I have a (minor) problem with the name; it's too clumsy. > > Yeah, but I would like to know of a better one (without just moving the > ugliness to the name of the option used ;) Thanks for checking it out! pam_self ;-) Seriously, pam_loggedin is already better, but still too clumsy (but not as clumsy as before). (free association mode: pam_connected; pam_on; pam_live; pam_active; pam_authenticated - of these, I dislike pam_active the least) M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203071017.g27AHBRV008209>