The attached patch applied over current ebuild, and the three pamd files (put in the right place, see the ebuild patch) allows gdm to work with openpam implementation: it removes the /lib/security prefix in pamd configuration file (breaks also no-lib32 profile of amd64) and uses include directive instead of pam_stack; it also move pam_env sa optional as it's a non-standard pam module which doesn't exists by default in fbsd. I've added a domansecurity function to simplify the installation, it's in the pam eclass which is still not in the tree so needs to wait for it to be before this patch can be applied clean. Thanks, Diego
Created attachment 59287 [details, diff] Ebuild patch
Created attachment 59288 [details] gdm
Created attachment 59289 [details] gdm-autologin
Created attachment 59290 [details] gdmconfig
So get us up to speed here, this works fine for both pam implementations ? The ebuild patch needs only to install the pam stuff if it's actually used (thats why there's the USE flag).
Yes this works fine on both implementation. I've set this bug dependent on bug #93118 because it uses the functions defined in the new pam eclass, which is not in tree right now. new/dopamd, new/dopamsecurity installs the files just if pam useflag is selected by user (and if it's in $IUSE to avoid problems when pam is mandatory), so no need to use an if check for this (see always the eclass above).
added to gdm-2.6.0.9-r1
