- Jan 09, 2020
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
-
-
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
Long term, overlay callbacks should not be running in tool mode at all.
-
- Dec 02, 2019
-
-
Quanah Gibson-Mount authored
-
-
- Nov 25, 2019
-
-
Quanah Gibson-Mount authored
-
- Nov 22, 2019
-
-
Quanah Gibson-Mount authored
-
If a txn is aborted in id2entry_put, attribute index mappings added during that txn must also be dropped from memory.
-
Quanah Gibson-Mount authored
-
And additional debug code for tracking errant close()s
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
- Nov 21, 2019
-
-
Quanah Gibson-Mount authored
-
Howard Chu authored
-
Howard Chu authored
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
Since GnuTLS moved to implicit initialization on library load, calling this function deinitializes GnuTLS and then re-initializes it. When GnuTLS uses /dev/urandom as an entropy source (getrandom() not available, or older versions of GnuTLS), and the application closed all file descriptors at startup, this could result in GnuTLS opening /dev/urandom over one of the application's file descriptors when re-initialized. Additionally, the custom mutex functions are never reset, so if libldap is unloaded (for example via dlclose()) after calling this, its code may be unmapped and the application could crash when GnuTLS calls the mutex functions. On typical systems, GnuTLS system mutexes are probably the same as what libldap uses anyway.
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
-
- Oct 15, 2019
-
-
Quanah Gibson-Mount authored
-
-