Cannot dynamically set nsslapd-maxbersize

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/542

• Created at 2012-12-20 00:02:33 by jraquino
• Closed as Fixed
• Assigned to nhosoi (@nhosoi)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=918689

---

This bug effects directory initializations when the membersize exceeds the default value. For example, a dogtag replica installation with a large CRL entry will fail due to the size exceeding 2097152 bytes.

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-12-20 00:10:24

The only place we tell the Sockbuf layer that we have a max size is here:

Connection_Table *
connection_table_new(int table_size)
...
		ber_len_t maxbersize = config_get_maxbersize();

this should be moved before the loop - no reason to do this inside the loop

		ber_sockbuf_ctrl( ct->c[i].c_sb, LBER_SB_OPT_SET_MAX_INCOMING, &maxbersize );

Will be tricky to do this dynamically and have it apply to all open connections. Would prefer to do it only for new connections:

handle_new_connection()
...
	ber_sockbuf_add_io( conn->c_sb, &openldap_sockbuf_io,
						LBER_SBIOD_LEVEL_PROVIDER, conn );
...
		ber_len_t maxbersize = config_get_maxbersize();
		ber_sockbuf_ctrl( conn->c_sb, LBER_SB_OPT_SET_MAX_INCOMING, &maxbersize );

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2013-01-10 03:36:22

Fix description: Based on the proposal made by richm@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.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2013-01-10 03:37:12

git patch file (master)
0001-Ticket-542-Cannot-dynamically-set-nsslapd-maxbersize.patch

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2013-01-11 00:52:04

Reviewed by Rich (Thank you!!)

Pushed to master: commit cce46be

Pushed to 389-ds-base-1.3.0: commit 5941a5b

[389-ds-bot]

Comment from nkinder (@nkinder) at 2013-03-07 00:13:23

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=918689

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 22:53:27

Metadata Update from @nhosoi:

• Issue assigned to nhosoi
• Issue set to the milestone: 1.3.0.2