Hi, Carlos Alberto Lopez Perez <clo...@igalia.com> writes: > Now I'm convinced that the right fix for this is to revert upstream > d769529a71ccda4e833f919f3c5693d25b005ff0 [1] commit on libgcrypt like > Ubuntu did. > > The Regression introduced on python-gnutls by such reversion was already > fixed on Ubuntu with another patch (see LP:#1013798 [2]) and they have > been running with the patch for some time without more problems (AFAIK) > so I think that we can assume that there are no more regressions. > > Therefore I think we should reassign this bug back to libgcrypt11. Fix > it with a patch that reverts d769529a71ccda4e833f919f3c5693d25b005ff0 > [1] and then fill another RC bug for python-gnutls asking for applying > the same patch that Ubuntu applied (see LP:#1013798 [2])
At work we are running into this problem while testing wheezy. setuid programs were failing when authenticating over ldap. I've tested a patch to libgcrypt11 reverting d769529a71ccda4e833f919f3c5693d25b005ff0 and it fixes the problem for us, with no obvious regressions. If you want me to do any more testing I can do so. Is it possible to get this fixed for the wheezy release? It would greatly smooth our rollout of wheezy. Thanks to all for your work on this. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
