This bug was fixed in the package pam - 1.0.1-9ubuntu1
---------------
pam (1.0.1-9ubuntu1) jaunty; urgency=low
* Merge from Debian unstable
* Remaining changes:
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's not
present there or in /etc/security/pam_env.conf. (should send to Debian).
- debian/libpam0g.postinst: only ask questions during update-manager when
there are non-default services running.
- debian/patches-applied/series: Ubuntu patches are as below ...
- debian/patches-applied/ubuntu-fix_standard_types: Use standard u_int8_t
type rather than __u8.
- debian/patches-applied/ubuntu-no-error-if-missingok: add a new, magic
module option 'missingok' which will suppress logging of errors by
libpam if the module is not found.
- debian/patches-applied/ubuntu-regression_fix_securetty: prompt for
password on bad username.
- debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly
initialise RLIMIT_NICE rather than relying on the kernel limits.
- debian/patches-applied/ubuntu-user_defined_environment: Look at
~/.pam_environment too, with the same format as
/etc/security/pam_env.conf. (Originally patch 100; converted to quilt.)
- Change Vcs-Bzr to point at the Ubuntu branch.
- debian/local/common-password, debian/pam-configs/unix: switch from
"md5" to "sha512" as password crypt default.
pam (1.0.1-9) unstable; urgency=low
* Move the pam module packages to section 'admin'.
* 027_pam_limits_better_init_allow_explicit_root: defaults need to be
declared as LIMITS_DEF_DEFAULT instead of LIMITS_DEF_ALL, otherwise
global limits will fail to be applied. LP: #314222.
pam (1.0.1-8) unstable; urgency=low
* Updated debconf translations:
- Bulgarian, thanks to Damyan Ivanov <d...@debian.org> (closes: #518121)
- Spanish, thanks to Javier Fernandez-Sanguino Peña <j...@debian.org>
(closes: #518214)
- Swedish, thanks to Martin Bagge <brot...@bsnet.se> (closes: #518324)
- Vietnamese, thanks to Clytie Siddall <cly...@riverland.net.au>
(closes: #518329)
- Japanese, thanks to Kenshi Muto <km...@debian.org> (closes: #518335)
- Slovak, thanks to Ivan Masár <heli...@centrum.sk> (closes: #518341)
- Czech, thanks to Miroslav Kure <ku...@debian.cz> (closes: #518992)
- Portuguese, thanks to Américo Monteiro <a_monte...@netcabo.pt>
(closes: #519204)
- Galician, thanks to Marce Villarino <mvillar...@users.sourceforge.net>
(closes: #519447)
- Romanian, thanks to Eddy Petrișor <eddy.petri...@gmail.com>
(closes: #520552)
* 027_pam_limits_better_init_allow_explicit_root: set the RLIMIT_MEMLOCK
limit correctly to match the kernel default, which is not RLIM_INFINITY.
Closes: #472629.
-- Steve Langasek <steve.langa...@ubuntu.com> Fri, 20 Mar 2009
19:12:10 -0700
** Changed in: pam (Ubuntu Jaunty)
Status: Fix Committed => Fix Released
--
setting core dump size to above 0 does not work in /etc/security/limits.conf
https://bugs.launchpad.net/bugs/314222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
