Description of problem: After recent pam changes /var/log/secure is constantly badgered by messages in this style: pam_keyinit(gdm:session): UID:0 [0] GID:0 [0] pam_keyinit(gdm:session): JOIN = 593955641 pam_keyinit(gdm:session): UID:0 [0] GID:0 [0] pam_keyinit(gdm:session): GET SESSION = 593955641 pam_keyinit(gdm:session): GET SESSION = 1 pam_keyinit(sshd:session): UID:0 [0] GID:0 [0] pam_keyinit(sshd:session): JOIN = 614504224 pam_keyinit(sshd:session): UID:0 [0] GID:0 [0] pam_keyinit(sshd:session): GET SESSION = 614504224 pam_keyinit(sshd:session): GET SESSION = 1 This does not look like it conveys any useful information to a user/administrator of a system while no 'debug' option is used in /etc/pam.d/ files. It also looks awfully redundant. Is this some kind of development debugging turned on which later will disappear? If not then logwatch should be taught about that. Version-Release number of selected component (if applicable): pam-0.99.5.0-3.fc6
The debugging messages were on by default. Fixed.