[Petter Reinholdtsen] >> So, I see two problems here >> >> - The pam module fail when there is no tty, and thus listing it as >> required in /etc/pam.d/common-session will fail with the current >> implementation. > > This is still an issue, and I suspect it need to be solved in the > pam configuration, ie /etc/pam.d/current-session. It could be > argued that a pam module that only work when a tty is available > should not be required if you want pam to accept sessions without a > tty. On the other hand, perhaps the module should accept to do > nothing if no tty is available?
On second thought, I believe the proper way to configure pam is to only use pam-devperm for the services providing ttys, and to _not_ list it in /etc/pam.d/current-session but in /etc/pam.d/login, /etc/pam.d/gdm, etc. Then at will not try to use the module and this work properly. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
