-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Errr... ?
- - As *I* have not changed *myself* anything in pam/winbind configuration in the past few months - - As it used to work ==> There is something / somebody that changed the configuration files on my system (without asking for). - - As nobody (but me – and *I* didnt do that) can access my machine (well, I suppose) ==> "something" did that for me If "something" did that without asking, and left the system (this part of) unuseable, it is a bug (because doing so cannot be a feature). I don't say it is a libpam bug but there is a bug somewhere in the "something" that changed this configuration *without asking*. And probably this "something" should have left the system as clean as it found it before when removed from the system. In this particular problem, probably this is winbind (update from 2:3.4.6~dfsg-1 -> 2:3.4.7~dfsg-1) but I think closing the bug whitout further investigation is a quick answer. Regards Jean-Luc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLmPFIUdGGXzzGnNARApfkAJ0dJKbz5TO0PlLoxPS7HoTz/X5eoQCfSaB7 ZMplcckJdk0ED6kbUZ9Ctz0= =PTuF -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
