[Bug 259915] Re: ecryptfs should use pam-auth-update rather than auth-client-config
Patch attached. It seems to do the right thing in all cases that I have tested. I'm hoping Steve Langasek will review/sponsor this upload, as it contains the code needed to use his new pam-auth-update utility. Please carefully review the debian/ecryptfs-utils.post[inst|rm] scripts, as I think those are the main place where a tweak might be needed. :-Dustin ** Attachment added: ecryptfs.259915.debdiff http://launchpadlibrarian.net/16983428/ecryptfs.259915.debdiff ** Changed in: ecryptfs-utils (Ubuntu) Importance: Undecided = High Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: New = In Progress Target: None = intrepid-alpha-5 -- ecryptfs should use pam-auth-update rather than auth-client-config https://bugs.launchpad.net/bugs/259915 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
[Bug 259915] Re: ecryptfs should use pam-auth-update rather than auth-client-config
As mentioned in my follow-up to bug #260122, the postrm is the wrong place to call pam-auth-update for removal. Please instead call it in the prerm instead, using semantics equivalent to the following: if [ $1 = remove ]; then pam-auth-update --package --remove ecryptfs-utils fi Implementing --remove is on my todo list for today; and it won't hurt anything to call pam-auth-update with unknown arguments in the meantime. But I can understand that you might want to test this before upload :-), so should I let you know once pam -3ubuntu3 is available? -- ecryptfs should use pam-auth-update rather than auth-client-config https://bugs.launchpad.net/bugs/259915 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
[Bug 259915] Re: ecryptfs should use pam-auth-update rather than auth-client-config
Updated patch attached, based on IRC suggestions from slangasek, and kvm testing by kirkland. :-Dustin ** Attachment added: ecryptfs.259915.debdiff http://launchpadlibrarian.net/16991300/ecryptfs.259915.debdiff -- ecryptfs should use pam-auth-update rather than auth-client-config https://bugs.launchpad.net/bugs/259915 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
[Bug 259915] Re: ecryptfs should use pam-auth-update rather than auth-client-config
This bug was fixed in the package ecryptfs-utils - 53-1ubuntu6 --- ecryptfs-utils (53-1ubuntu6) intrepid; urgency=low * Fixes (LP: #259915). * debian/control: drop suggests of auth-client-config, add depends on libpam-runtime. * debian/ecryptfs-utils.postinst: initial creation, use pam-auth-update, be sure to 'force' if pam stack was precisely written by auth-client-config. * debian/ecryptfs-utils.prerm: remove pam-auth-update config on uninstall * debian/ecryptfs-utils.pam-auth-update: initial creation of pam-auth-update configuration. * debian/ecryptfs.acc: drop auth-client-config profile. * debian/rules, debian/ecryptfs-utils.install, debian/ecryptfs-utils.dirs: remove auth-client-config installation, add pam-auth-update. -- Dustin Kirkland [EMAIL PROTECTED] Fri, 22 Aug 2008 01:22:48 +0100 ** Changed in: ecryptfs-utils (Ubuntu) Status: In Progress = Fix Released -- ecryptfs should use pam-auth-update rather than auth-client-config https://bugs.launchpad.net/bugs/259915 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