https://bugs.openldap.org/show_bug.cgi?id=9858
Issue ID: 9858
Summary: cn=config replication refresh breaks mdb database
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
working in an environment with the following layout:
Config node -> This node contains the cn=config databases for consumers in one
tree and providers in another tree.
provider nodes -> Pull their configuration from the config node via standard
syncrepl
consumer nodes -> Pull their configuration from the config node via standard
syncrepl
This worked fine with OpenLDAP 2.4.
With 2.6, using the same cn=config configuration, slapd will segfault if the
cn=config db is put through a REFRESH sequence. I've ruled out syncprov as an
issue as I removed the syncprov configuration from the consumer nodes entirely
and it still occurs (I was thinking perhaps it was the syncprov checkpoint at
shutdown). At this point I can reproduce this trivially 100% of the time
simply by having a node REFRESH cn=config.
Once the REFRESH has occurred, slapd will continue running. However the next
time it is stopped/started it will SEGV on startup. It is usually possible to
use slapcat to extract the MDB database and rebuild it, at which point slapd
will start again. A couple of times I was only able to extract a portion of
the database using slapcat (70MB of 650MB).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9855
Issue ID: 9855
Summary: Implement a module to enable case-insensitive Boolean
values
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: contrib
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
The module, when loaded from slapd.conf, will allow for values such as true,
false and True, False, to be accepted by the server
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9850
Issue ID: 9850
Summary: slapd-watcher ignores sids when only 1 server is
specified
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When only 1 URL is provided, it always uses only a contextCSN with sid=0.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9865
Issue ID: 9865
Summary: slapd-watcher: support for glue
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: enhancement
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When operating on glued backends, the DB where entry counts need to be
monitored may be different from where the contextCSN updates occur. Add a "-c"
option to allow specifying the contextCSN baseDN, separate from the main "-b"
baseDN.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9872
Issue ID: 9872
Summary: slapd-ldap(5) man page missing bold tag on authz
parameter
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The slapd-ldap(5) man page is missing a bold tag on the authz configuration
parameter.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9864
Issue ID: 9864
Summary: One-time leaks in accesslog
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: minor
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
In tool mode, the accesslog's configured logdb suffix isn't freed. It's
normally freed by the db_open handler but in tool mode the overlay never
actually gets opened.
Also due to 414866b8889 ITS#9580, li_sids can leak when replacing mincsn.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8882
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9867
Issue ID: 9867
Summary: syncprov leak on early Abandons
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
The baseDN found by syncprov_findbase() can be leaked if an Abandon or error
occurs early during psearch processing.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9871
Issue ID: 9871
Summary: bind operations on relay entries cause slapd to
segfault with rwm and ppolicy enabled
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: subbarao(a)computer.org
Target Milestone: ---
On 2.5.12, slapd crashes during bind operations on relay entries with rwm and
ppolicy both enabled. A simple way to reproduce this issue is to edit
tests/scripts/relay and tests/data/slapd-relay.conf as follows, and then run
test030-relay. I think this issue is the same as ITS#7966 reported in 2014.
--- tests/scripts/relay.orig 2022-05-04 07:57:30.000000000 -0700
+++ tests/scripts/relay 2022-06-23 17:16:42.020652093 -0700
@@ -356,6 +356,16 @@
exit 1
fi
+$LDAPADD -D "$MANAGERDN" -H $URI1 -w $PASSWD <<EOF > /dev/null 2>&1
+dn: cn=ppolicy,dc=example,dc=com
+objectClass: top
+objectClass: device
+objectClass: pwdPolicy
+cn: ppolicy
+pwdMinLength: 5
+pwdAttribute: userPassword
+EOF
+
BASEDN="o=Example,c=US"
echo "Changing password to database \"$BASEDN\"..."
$LDAPPASSWD -H $URI1 -D "cn=Manager,$BASEDN" -w $PASSWD \
--- tests/data/slapd-relay.conf.orig 2022-05-04 07:57:30.000000000 -0700
+++ tests/data/slapd-relay.conf 2022-06-23 16:57:15.184456120 -0700
@@ -31,6 +31,8 @@
#metamod#moduleload back_meta.la
#rwmmod#modulepath ../servers/slapd/overlays/
#rwmmod#moduleload rwm.la
+#ppolicymod#modulepath ../servers/slapd/overlays/
+#ppolicymod#moduleload ppolicy.la
#######################################################################
# database definitions
@@ -46,6 +48,9 @@
#ndb#dbname db_1
#ndb#include @DATADIR@/ndb.conf
+overlay ppolicy
+ppolicy_default cn=ppolicy,dc=example,dc=com
+
database @RELAY@
suffix "o=Example,c=US"
### back-relay can automatically instantiate the rwm overlay
--
You are receiving this mail because:
You are on the CC list for the issue.