Ticket #109 (closed task: fixed)
debathena-pam-config updates for Intrepid
Reported by: | andersk | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Keywords: | ||
Cc: | Fixed in version: | ||
Upstream bug: |
Description
debathena-pam-config needs to be updated to work on Intrepid, as outlined in my email from August:
From: Anders Kaseorg <andersk@…>
To: debathena@…
Subject: Major PAM configuration changes in intrepid
Date: Thu, 28 Aug 2008 05:47:18 -0400
I’m guessing the rest of you are too lame to run intrepid, but just so you have advance warning, they completely redid their PAM configuration today in a much more package-friendly way. There’s a new pam-auth-update(8) utility that manages /etc/pam.d/common-* by using package-supplied configuration snippets in /usr/share/pam-configs. Here’s an example from /usr/share/pam-configs/ldap:
Name: LDAP Authentication Default: yes Priority: 128 Auth-Type: Primary Auth-Initial: [success=end default=ignore] pam_ldap.so Auth-Final: [success=end default=ignore] pam_ldap.so use_first_pass Account-Type: Primary Account-Final: [success=end default=ignore] pam_ldap.so Password-Type: Primary Password-Initial: [success=end user_unknown=ignore default=die] pam_ldap.so Password-Final: [success=end user_unknown=ignore default=die] pam_ldap.so use_authtok try_first_pass Session-Type: Additional Session-Final: optional pam_ldap.so
Some information is available at:
https://wiki.ubuntu.com/PAMConfigFrameworkSpec
With intrepid scheduled for release in about two months, it would be a very good idea for someone to play with this new framework and come up with a plan for updating debathena-pam-config (and maybe even splitting it somewhat, now that this seems possible).
Anders
Done in r23225 through r23230.