On Thu, May 08, 2008 at 05:25:24PM +0200, Christoph Pleger wrote: > Hello, > > >> The former seems to make more sense to me. > > >Myself as well, but I'm hesitant to blindly include the old patch unless > >someone picks it up, updates or rewrites it for current code, and gets > >some code review from current PAM folks. > > As far as I can see, my old changes should still apply to the current etch > version of libpam-unix2.
Getting a fix past the release-managers into etch is probably a lost cause. We can include a fix in a normal upload to unstable. If we are quick, we can probably even make it into lenny, the next release. As my message says, what needs to be done to resolve this bug: - The patch needs to be updated to apply against the current package in unstable. and, importantly: - we need some some code review/feedback/ignoff from the Debian folks maintaining PAM and other related components. I am *NOT* going to be the guy who uploads a new setuid binary without adequate review. > unix2_chkpwd.c is available for example in the file > pam-modules-10.3-47.src.rpm of OpenSuSE 10.3. Installing that file on a > Debian system (with rpm -i) unpacks unix2_chkpwd.c > into /usr/src/rpm/SOURCES/. This is interesting new information. You're saying "unix2_chkpwd.c" has an upstream somewhere (separate from pam_unix2)? That's odd, but certainly a better situation to be in than a random one-off piece of code. Is there somewhere where one can download the current "unix2_chkpwd" source, on its own and not as part of the SuSE PAM source RPM? Someone really needs to pick up the ball and run with it as described above if they want this issue fixed. Unfortunately I don't have time for that myself in the near future. Dear LazyNet, the bug is tagged "help", please do! :) -- _ivan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
