Now that /etc/pam.d/common-* are managed by pam-auth-update (squeeze and
above), I think this bug can probably be closed: no PAM module profile
should ever be using 'sufficient', and users are unlikely to be editing
these files by hand going forward.

It might be reasonable for /etc/pam.d/cron to move the pam_limits line ahead
of the 'include common-session' line in any case, but I don't think it's a
very significant bug if you don't.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[email protected]                                     [email protected]

Attachment: signature.asc
Description: Digital signature

Reply via email to