-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.0
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
ALL
-
The gsasl initialization detection logic in the enterprise repo:
https://github.com/10gen/mongo-enterprise-modules/blob/master/src/gcrypt_init.cpp#L22-L25
Can end up running after the gsasl initialization in the client:
This is a problem because the client initializer calls sasl_init, which may initialize gcrypt, but the enterprise initializer needs to be the first to initialize gcrypt. The enterprise initializer detects that it did not get to initialize gcrypt, and errors out, preventing mongod from starting.
- is duplicated by
-
SERVER-9167 Problem with global initialization of gcrypt library in enterprise build
- Closed
- is related to
-
SERVER-8068 Need to conditionally initialize gcrypt library
- Closed
- related to
-
SERVER-9103 Backport fix for SERVER-9086 to 2.4.x
- Closed