After gstreamer, gcrypt is also dropping support for alternative thread libraries. Good thing secur32/schannel_gnutls.c doesn't use it. (Right?) - Dan
---------- Forwarded message ---------- From: Werner Koch wk@gnupg.org Date: Wed, Nov 7, 2012 at 1:31 AM Subject: Re: Bug#566351: libgcrypt11: should not change user id as a side effect To: Andreas Metzler ametzler@downhill.at.eu.org Cc: gcrypt-devel@gnupg.org, 566351@bugs.debian.org
On Sat, 3 Nov 2012 18:29, ametzler@downhill.at.eu.org said:
comment sums it up: https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/72
Well, it is the usual problem with inter-library dependencies. We will never be able to get this right. The DSO is just not designed to work with completely independent libraries. I don't like to say, but in this regard Windows DLLs are a better solution.
Although we can't solve all the problems we will be able to solve the thread initialization problem. Libgcrypt 1.6 will ignore the thread callbacks and assume pthread. Semaphores are then used for locking and provide a way to do thread-safe initialization. The hopefully minor drawback is that one needs to link against librt.
case GCRYCTL_SET_THREAD_CBS:err = ath_install (va_arg (arg_ptr, void *), any_init_done);+- if (! err) +- global_init ();
Okay, if that works, fine. It might break other things; I don't know. There are enough selftests to hopefully detect such a break (in particular in FIPS mode).
Salam-Shalom,
Werner
-- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
_______________________________________________ Gcrypt-devel mailing list Gcrypt-devel@gnupg.org http://lists.gnupg.org/mailman/listinfo/gcrypt-devel