[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
tags 492348 + patch
thanks
[Petter Reinholdtsen]
The back trace look like the function pointer __write_message is
NULL, and thus a call to the function fail. But as far as I can see,
it isn't a function pointer but a real function. Perhaps the dynamic
linker is confused?
I managed to track
[Petter Reinholdtsen]
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
I am able to reproduce this issue. I rebuild libpam-devperm with
debug symbols and ran 'valgrind atd -d' to get more details on the
crash, and this is the report:
==21819== Jump to the invalid address stated on the next line
==21819==at 0x0: ???
==21819==by 0x403339A:
Package: libpam-devperm
Version: 1.5-2
Severity: critical
Justification: breaks unrelated software
Hello,
as you can see in the bug description for Debian Bug #418560, at jobs are
not executed if I include session required pam_devperm.so to my
/etc/pam.d/common-session.
I do not know if this
5 matches
Mail list logo
