[389-devel] Please review: [389 Project] #542: Cannot dynamically set nsslapd-maxbersize

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx
 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.

--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel



[Index of Archives]     [Fedora Directory Announce]     [Fedora Users]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [CentOS]     [Fedora SELinux]     [Big List of Linux Books]     [KDE Users]     [Fedora Art]     [Fedora Docs]

  Powered by Linux