Diego "Flameeyes" Petten� wrote:
Ok we could switch g/fbsd to use Linux-PAM, as Linux-PAM is multiplatform, in
spite of its name, but this won't fix the problem, as g/osx would have the
same problem: macosx's pam implementation is compatible with openpam,
linuxpam and so on, but it doesn't support pam_stack.
Let's replace it or fix pam-stack to work on openpam.
Now, solution of that is quite simple: just don't use pam_stack, and convert
all the pam configuration file to duplicate the default system-auth
authentication scheme. If someone needs to change the way system-auth works,
adding ldap, samba or something like that for authentication, they should
also be able to change the needed other services, such as sshd, ftpd, pop3
and imapd stuff.
I'm against it.
This is not the only thing needed to fix everything up. All the packages which
depends on sys-libs/pam should be changed, as g/fbsd, g/osx and other
g/non-linux can have other implementations of pam. My suggestion is adding a
virtual/pam which could be used, so that g/osx will provide it directly,
g/fbsd could provide it via its own packages (or using an openpam package,
which could be used on linux, too), and linux still can use sys-libs/pam.
Too much work IMHO
Also, it could be better rename sys-libs/pam into sys-libs/linux-pam: also if
the name isn't restrictive, that's the right name for them: it's not "The
PAM".
if we are going to have multiple pam implementation then I think is
necessary
[1] http://news.gmane.org/gmane.linux.gentoo.bsd
--
Luca Barbato
Gentoo/linux Developer Gentoo/PPC Operational Manager
http://dev.gentoo.org/~lu_zero
--
[email protected] mailing list
