- Apr 26, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
- Apr 14, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
- Apr 07, 2017
-
-
Quanah Gibson-Mount authored
-
Make two successive modifications of the same attribute separate. This lets the consumer interpret the log entry the same way as the server that produced it. Still depends on the log entry attributes being read in the same order as they were written.
-
Quanah Gibson-Mount authored
-
- Apr 06, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
- Mar 29, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
Update sections 6.2.2.1, 6.2.3.3
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
- Mar 16, 2017
-
-
Quanah Gibson-Mount authored
-
-
- Mar 08, 2017
-
-
Quanah Gibson-Mount authored
-
This fixes issues with values that need escaping in the rDN when an incorrect value would be passed to the handler and back-ldif.
-
- Feb 28, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
The TLS configuration deliberately hid the error in case that user specified CA locations cannot be read, by loading CAs from default locations; and when user does not specify CA locations, the CAs from default locations are not read at all. This patch corrects the behaviour so that CAs from default location are used if user does not specify a CA location, and user is informed of the error if CAs cannot be loaded from the user specified location.
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-
- Feb 03, 2017
-
-
Quanah Gibson-Mount authored
-
Quanah Gibson-Mount authored
-