Tags: aninggo/ldap
Tags
fix: memory allocations (go-ldap#252) * fix: memory allocations * fix: replace strings.Builder to bytes.Buffer for old goland versions * fix: rename escapedStringToEncodedBytes to decodeEscapedSymbols * feat: remove one allocation * fix (v3): memory allocations
add modify-increment extension support detailed in RFC4525 (go-ldap#227) * add modify-increment extension support detailed in RFC4525 This extension is detailed in [RFC4525](https://tools.ietf.org/html/rfc4525). To summarize, it allows for auto-incrementing a specific attribute by a specific amount. It can be used in conjunction with pre-read, post-read, and assert control types * update v3
Update go.mod (go-ldap#241) I believe that this (plus a new tag) is what is necessary for native go modules support -- right now go modules complains that the version tag is >= v2 but the module doesn't claim to be a version >= v2.
Rename asn1 ber dependency. (go-ldap#243) * Rename asn1.ber dependency. * go mod tidy * Update travic CI to new asn1 ber * Update travis go_import_path
unified request flow && external binding to LDAP (go-ldap#232) * unified request flow && external binding to LDAP * fix debug mode * go.mod was added
Added check for ControlValue string check (go-ldap#213) * Added check for controlvalue * Fixed tests
Fix LDAP diagnostics message used as format string (go-ldap#208) * Add GetLDAPError() tests This patch adds a couple of tests for the `GetLDAPError()` function. * Fix LDAP diagnostics message used as format string The GetLDAPError()-function passes the `diagnosticMessage` error field as the first parameter to `fmt.Errorf()`. If this message happens to contain a `%`-character, Go will try to interpret it. This doesn't directly lead to an error, but results in error messages containing format string error codes. E.g.: The error message "Detailed error message %" will result in the error "Detailed error message %!(NOVERB)". This patch fixes this by inserting a format string as the first argument to `fmt.Errorf()`.
PreviousNext