I can confirm that it works as expected after adding the upstream PAM file.
Can't say what would be the best approach here, but I agree that fixing the
issue might bring with it security issues, particularly if the binary is
also installed as setuid-root, which is, as far as I can tell, also required for
full functionality.
Thanks for looking into this.
I can confirm that it works as expected after adding the upstream PAM file.
Can't say what would be the best approach here, but I agree that fixing the
issue might bring with it security issues, particularly if the binary is
also installed as setuid-root, which is, as far as I can tell, also required for
full functionality.
The bug was already reported to Debian: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 1004472
https:/