Package: pam-shield Version: 0.9.2-3.2 Severity: important pam_shield.cron never gets run by run-parts since '.' is illegal in cron filenames. In turn this means that shield-purge does not get run and then, presumably, stale shield rules don't get flushed.
The effect of this, though I did not try it in the real world, should be that it becomes possibly to lock oneself out of a system until the next reboot. Because I'm not able to test that part I have filed with severity important, but you should consider increasing it to serious if you agree with my reasoning. Any fix for this for Wheezy will have to go through testing-proposed-updates, and indeed we should fix it if possible. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
