This bug was fixed in the package pam - 1.1.0-4ubuntu1
---------------
pam (1.1.0-4ubuntu1) lucid; urgency=low
* Merge from Debian, 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-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.
- Change Vcs-Bzr to point at the Ubuntu branch.
- Make libpam-modules depend on base-files (>= 5.0.0ubuntu6), to ensure
run-parts does the right thing in /etc/update-motd.d.
- debian/patches-applied/pam_motd-legal-notice: display the contents of
/etc/legal once, then set a flag in the user's homedir to prevent showing
it again.
- debian/local/common-{auth,account,password}.md5sums: include the
Ubuntu-specific intrepid,jaunty md5sums for use during the
common-session-noninteractive upgrade.
pam (1.1.0-4) unstable; urgency=low
* debian/patches/pam_securetty_tty_check_before_user_check: new patch,
to make pam_securetty always return success on a secure tty regardless
of what username was passed. Thanks to Nicolas François
<[email protected]> for the patch. Closes: #537848
* debian/local/pam-auth-update: only reset the seen flag on the template
when there's new information; this avoids reprompting users for the same
information on upgrade, regardless of the debconf priority used.
Closes: #544805.
* libpam0g no longer depends on libpam-runtime; packages that use
/etc/pam.d/common-* must depend directly on libpam-runtime, and most do
(including the Essential: yes ones), so let's break this circular
dependency. Closes: #545086, LP: #424566.
pam (1.1.0-3) unstable; urgency=low
* Bump debian/compat to 7, so we can use sane contents in debian/*.install
* Switch all packages over to dh_install
* Rename debian/*.lintian to debian/*.lintian-overrides and use dh_lintian
* Move installation logic out of debian/rules into individual .install
files
* Drop superfluous options to dh_installchangelogs, dh_shlibdeps
* Use debian/clean instead of rm -f'ing files in debian/rules clean target
* Drop ./configure options that are no-ops
* Drop the /lib/security/pam_unix_*.so symlinks, which have been deprecated
now for 10 years and are not used at all if pam-auth-update is in play.
* Drop the pam_rhosts_auth.so symlink as well, and document in NEWS.Debian
that this is now obsolete.
* Drop stale content from README.debian: some of this should have been in
NEWS.Debian instead (but is so old it's not worth putting it there now),
some of it is obsolete by the change in package VCS.
* Convert debian/rules to debhelper 7 and add versioned build-dependencies
on debhelper and quilt to suit.
* Drop CFLAGS that we don't need anymore (-fPIC, -D_REENTRANT,
-D_GNU_SOURCE).
* Explicitly add -O0 to CFLAGS when noopt is set.
* debian/patches/autoconf.patch: pull ltmain.sh in, to fix some spurious
library linkage in the modules.
* Move pam_cracklib manpage to the libpam-cracklib package, and add the
requisite Replaces
* Drop dh_makeshlibs -V; everything from lenny on should use the .symbols
file instead, making the shlibs redundant so we don't need to care what
version gets listed there.
-- Steve Langasek <[email protected]> Thu, 05 Nov 2009 21:33:15 -0800
** Changed in: pam (Ubuntu)
Status: Triaged => Fix Released
--
Dependency / Pre-Dependency cycle
https://bugs.launchpad.net/bugs/424566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
