https://bugs.openldap.org/show_bug.cgi?id=10013
Issue ID: 10013
Summary: Some code (ppolicy, etc.) ignores
REP_CTRLS_MUSTBEFREED when touching rs->sr_ctrls
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Certain parts of the source indicate that rs->sr_ctrls shouldn't be
realloc'd/free'd unless REP_CTRLS_MUSTBEFREED is set, but then other parts of
slapd (slap_ctrl_whatFailed_add, glue_op_search?, ...) and overlays (ppolicy,
syncprov, ...) will blindly overwrite and/or realloc it.
slap_add_control() (an analog of slap_add_controls()) might be useful for this,
possibly alongside some way to free the other data kept around to streamline
the code other users need for correct operation.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9944
Issue ID: 9944
Summary: Reverting an olcDbACLBind statement breaks proxied
write operations
Product: OpenLDAP
Version: 2.6.3
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: ---
On a system with olcDbIDAssertBind configured, and proxied authorizations
working correctly, an olcDbACLBind statement was added to the configuration for
lastbind support. However an incorrect identity was in place for the authzid
in the ACL bind statement which caused proxy authorization to fail. The change
was backed out (There was never any change to the olcDbIDAssertBind config
fragment) and after that, all write operations failed instead of being proxied,
with err=80. Restarting slapd fixed the issue, which indicates an underlying
problem in the cn=config db in reverting to the original working state.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10137
Issue ID: 10137
Summary: Ease redefining the MDB_IDL_LOGN value
Product: LMDB
Version: 0.9.30
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: renault.cle(a)gmail.com
Target Milestone: ---
Created attachment 992
--> https://bugs.openldap.org/attachment.cgi?id=992&action=edit
The patch do apply to midl.h
Hello,
I would like to slightly change the midl.h c file to make it possible to change
the MDB_IDL_LOGN define without having to fork on my side. I know it can be
redefined to reduce the amount of memory allocated by LMDB. I am using the
latest `mdb.master` branch version of LMDB.
https://github.com/mozilla/lmdb/pull/2
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9660
Issue ID: 9660
Summary: back-mdb Permission denied => Restore from backup
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: geert.hendrickx(a)telenetgroup.be
Target Milestone: ---
Cosmetic issue:
When an mdb database has incorrect ownership or permissions (typically after
slapadd as root), back-mdb fails with:
mdb_db_open: database "dc=my-domain,dc=com" cannot be opened: Permission denied
(13). Restore from backup!
"Permission denied" is correct, but "Restore from backup" is maybe not the most
appropriate advice. ;-)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10125
Issue ID: 10125
Summary: mdb_load: fix loading in Append mode
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
After committing/flushing a batch of writes, the cursor is not correctly
reinitialized in Append mode.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10131
Issue ID: 10131
Summary: wildcard search crash slapd with OU containing
parenthesis
Product: OpenLDAP
Version: 2.5.16
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: bourguijl(a)gmail.com
Target Milestone: ---
Dears,
When I do following ldapsearch as following :
ldapsearch -x -H ldap://hostname:3891 -b "o=mobistar.be" -s subtree
"(&(objectClass=groupOfUniqueNames)(uniqueMember=uid=jlb,ou=*,o=mobistar.be))"
cn dn
and the DB is containing these entries :
dn: uid=jlb,ou=Test (aa),ou=Partners,o=mobistar.be
dn: ou=Test (aa),ou=Partners,o=mobistar.be
even if this "uid=jlb" isn't member of a group as uniqueMember, it makes slapd
crashing.
I did test it on versions 2.5.7 & 2.5.16, same result --> slapd crashed.
Seems to be related to parenthesis presence in OU attribut.
Is it a bug ?
Thx,
Jean-Luc.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8826
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Ever confirmed|0 |1
--- Comment #1 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/661
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6166
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=10135
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10134
Issue ID: 10134
Summary: OpenLDAP Docker Installation and Migration
Product: OpenLDAP
Version: 2.5.13
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: chilimili1(a)outlook.de
Target Milestone: ---
Created attachment 990
--> https://bugs.openldap.org/attachment.cgi?id=990&action=edit
Dockerfile.txt logs_importfile.txt logs_slaptest.txt
Hi,
I am currently experiencing issues while building a Docker container for
OpenLDAP. I hope that an expert from the community can help me solve my
problem.
Issue 1: Docker Setup
I'm in the process of setting up OpenLDAP within a Docker container on a RHEL 9
base OS. I've attached the Dockerfile I'm using for reference. My primary
concern is that when I run the command RUN slaptest -f /tmp/slapd.conf -F
/etc/openldap/slapd.d -d 1, it fails with mdb_db_open: database
"dc=my-domain,dc=com": dbenv_open(/usr/var/openldap-data).
mdb_db_open: database "dc=my-domain,dc=com" cannot be opened: No such file or
directory (2). Restore from backup!.
Interestingly, slaptest -u seems to work fine. I would greatly appreciate it if
you could review my Dockerfile or provide insights into what might be causing
this issue.
Issue 2: LDAP Migration
Additionally, I'm trying to migrate configuration data from a system using
OpenLDAP 2.4.50 to OpenLDAP 2.5.13. During this process, I encountered the
following error:
csharp
Copy code
olcAuthzRegexp: value #0: keyword <olcAuthzRegexp> missing <regexp> <DN>
argument
slapadd: could not add entry dn="cn=config" (line=1)
Dockerfile.txt
logs_importfile.txt
logs_slaptest.txt
I'm not sure if these issues are related, but I thought it would be best to ask
for your expertise on both matters.
Thank you in advance for your assistance. Your guidance would be greatly
appreciated.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10133
Issue ID: 10133
Summary: We tried to use centralized authentication for the
root account, but it failed.
Product: OpenLDAP
Version: 2.6.0
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: liubo335(a)huawei.com
Target Milestone: ---
When sssd+ldap is used for centralized authentication of Linux users, it is
found that only non-root users can be authenticated, but the root user cannot
be authenticated. Therefore, I would like to ask whether the authentication of
the root user is not supported. If yes, what additional configuration items do
you need to pay attention to when authenticating the root user? Looking forward
to your answer, thank you very much.
--
You are receiving this mail because:
You are on the CC list for the issue.