[389-devel] Please review: [389 Project] #542: Cannot dynamically set nsslapd-maxbersize
Noriko Hosoi
nhosoi at redhat.com
Wed Jan 9 21:39:19 UTC 2013
https://fedorahosted.org/389/ticket/542
https://fedorahosted.org/389/attachment/ticket/542/0001-Ticket-542-Cannot-dynamically-set-nsslapd-maxbersize.patch
Fix description: Based on the proposal made by rmeggins at redhat.com
in the ticket #542, this patch sets maxbersize every time before
reading the client input from the socket.
If the incoming ber size is larger than maxbersize, access log logs:
[..] conn=# op=-1 fd=64 closed error 34 (Numerical result out of range) -
B2
And the error log logs:
[..] connection - conn=# fd=# Incoming BER Element was too long, max
allowable is # bytes. Change the nsslapd-maxbersize attribute in
cn=config to increase.
More information about the 389-devel
mailing list