pam 1.0.1-7ubuntu1 source package in Ubuntu

Changelog

pam (1.0.1-7ubuntu1) 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.
  * Dropped changes, merged in Debian:
    - debian/local/pam-auth-update (et al): new interface for managing
      /etc/pam.d/common-*, using drop-in config snippets provided by module
      packages.
    - New patch dont_freeze_password_chain, cherry-picked from upstream:
      don't always follow the same path through the password stack on
      the PAM_UPDATE_AUTHTOK pass as was used in the PAM_PRELIM_CHECK
      pass; this Linux-PAM deviation from the original PAM spec causes a
      number of problems, in particular causing wrong return values when
      using the refactored pam-auth-update stack.  LP: #303515, #305882.
    - debian/patches/027_pam_limits_better_init_allow_explicit_root:
      Add documentation to the patch showing how to set limits for root.
  * Bump the libpam-cracklib dependency on libpam-runtime to 1.0.1-6,
    reducing the delta with Debian.
  * Drop upgrade handling code from libpam-runtime.postinst that's only
    needed when upgrading from 1.0.1-2ubuntu1, a superseded intrepid
    pre-release version of the package.
  * pam-auth-update: swap out known md5sums from intrepid pre-release versions
    with the md5sums from the released intrepid version
  * pam-auth-update: drop some md5sums that will only be seen on upgrade from
    pre-intrepid versions; skipping over the 8.10 final release is not
    supported, and upgrading via 8.10 means those config files will be
    replaced so the old md5sums will never be seen again.

pam (1.0.1-7) unstable; urgency=low

  * 027_pam_limits_better_init_allow_explicit_root:
    - fix the patch so that our limit resets are actually *applied*,
      which has apparently been broken for who knows how long!
    - shadow the finite kernel defaults for RLIMIT_SIGPENDING and
      RLIMIT_MSGQUEUE as well, so that the preceding change doesn't
      suddenly expose systems to DoS or other issues.
    - include documentation in the patch, giving examples of how to set
      limits for root.  Thanks to Jonathan Marsden.
  * pam-auth-update: swap out known md5sums from intrepid pre-release
    versions with the md5sums from the released intrepid version
  * pam-auth-update: set the umask, so we don't accidentally mark
    /etc/pam.d/common-* unreadable.  Thanks to Martin Krafft for catching.
    Closes: #518042.

pam (1.0.1-6) unstable; urgency=low

  * Updated debconf translations:
    - Vietnamese, thanks to Clytie Siddall <email address hidden>
  * New patch dont_freeze_password_chain, cherry-picked from upstream:
    don't always follow the same path through the password stack on
    the PAM_UPDATE_AUTHTOK pass as was used in the PAM_PRELIM_CHECK
    pass; this Linux-PAM deviation from the original PAM spec causes a
    number of problems, in particular causing wrong return values when
    using the refactored pam-auth-update stack.  LP: #303515, #305882.
  * debian/local/pam-auth-update (et al): new interface for managing
    /etc/pam.d/common-*, using drop-in config snippets provided by module
    packages.

 -- Steve Langasek <email address hidden>   Tue, 03 Mar 2009 17:34:19 -0800