On 23/01/13 19:48, Andreas Metzler wrote: > On 2013-01-23 Carlos Alberto Lopez Perez <clo...@igalia.com> wrote: >> On 23/01/13 19:04, Andreas Metzler wrote: >>> On 2013-01-23 Carlos Alberto Lopez Perez <clo...@igalia.com> wrote: > ..] >>>> I'm attaching the debdiff. I rebuilt libgcrypt11 with the attached debdiff. >>>> After installing it, sudo works as expected. >>> [...] > >>> According to the experiences in Ubuntu it breaks other stuff: >>> https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798 >>> (+ 2 merged bugreports) > [...] > >> If you download the last Ubuntu dsc for libgcrypt11 > >> $ dget -u >> http://archive.ubuntu.com/ubuntu/pool/main/libg/libgcrypt11/libgcrypt11_1.5.0-3ubuntu2.1.dsc > > >> You will see that the patch they are carrying is the one that >> I put on the debdiff (no-global-init-thread-callbacks.diff) > >> The previous patch (enable-global-init-secure-memory.patch) >> applied on libgcrypt11/1.5.0-3ubuntu1 was the one that caused >> the regression and was the patch reverted (. > [...] > > Hello, > > I am pretty sure you are mistaken. > > Doublechecking LP #1013798 we find this: > https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798/comments/12 > | I just found the apparent root cause for the libgcrypt11 crash: > | Ubuntu includes a patch called > | 'no_global_init_during_thread_callbacks.diff' > > https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798/comments/23 > | This bug was fixed in the package libgcrypt11 - 1.5.0-3ubuntu2 > | [...] > | * debian/patches/enable-global-init-secure-memory.patch: > | Fix regression during disable/suspend of secure memory > > https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798/comments/25 > | Afaict this bug should not be marked as "fixed released" anymore because > | 1.5.0-3ubuntu2.1 reverted 1.5.0-3ubuntu2. > > enable-global-init-secure-memory.patch would have fixed LP #1013798 > but was reverted back to no-global-init-thread-callbacks.diff (which > fixes the sudo/LDAP issue) because the regression > <https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1076906> > from no-global-init-thread-callbacks.diff to > enable-global-init-secure-memory.patch > was too severe. > > LP #1013798 is still open and unfixed. > > cu andreas >
I see. Thanks for the clarification I can confirm that this patch is breaking python-gnutls: $ python Python 2.7.3 (default, Sep 9 2012, 17:41:34) [GCC 4.7.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import gnutls.crypto Segmentation fault There is only one reverse-dependency for python-gnutls on the archive: $ apt-rdepends -r python-gnutls Reading package lists... Done Building dependency tree Reading state information... Done python-gnutls Reverse Depends: mandos (1.6.0-1) mandos
signature.asc
Description: OpenPGP digital signature