On 01/04/2008, Nick Matteo <[EMAIL PROTECTED]> wrote: > MJ Ray makes an interesting point: Requiring PAM, and putting all > this in a pam.d/common-session sourced from pam.d/other, would really > be an ideal solution. This could guarantee that all sessions > (interactive, noninteractive, login, nonlogin, zsh, bash, ssh, > whatever) would have the proper environment. > > In fact, if it's possible to use Debian-style "configuration > directories" (where every package Foo which has some env-settings has > a file foo in, say, pamenv.d, and common-session sources pamenv.d/*) > then pam_env would work really well with the Links tree setup. > > Each package would just put its environment stuff into > Settings/pamenv.d, they'd get linked in, and common-session would > include them; DisableProgram it, and it goes away. You wouldn't even > need special Cache-handling, etc. > As 015 will feature PAM as default, I'd love to have more input on this - possibilities and solutions with PAM and good recourses and tips on how PAM should be configured. I have some ideas, but more information is always welcome.
-- /Jonas _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
