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=10151
Issue ID: 10151
Summary: Leaks in do_syncrep2() when error handling
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: ---
Investigating the persistent CI failures in test050, I can see some memory
leaks that should be tackled (if only to reduce noise). For one, when receiving
an entry without a syncrepl control attached or when dealing with a concurrent
thread removing that consumer, we leak our scratch data (decoded controls,
modlist, ...).
--
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=10157
Issue ID: 10157
Summary: mdb_load doesn't build for me
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: tools
Assignee: bugs(a)openldap.org
Reporter: vl(a)samba.org
Target Milestone: ---
Created attachment 1001
--> https://bugs.openldap.org/attachment.cgi?id=1001&action=edit
Patch
see attached patch
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7420
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• f5c96f44
by Howard Chu at 2024-01-10T17:05:13+00:00
ITS#7420 move entry_naming_check earlier in Add
• 7debe76f
by Howard Chu at 2024-01-15T16:43:56+00:00
ITS#7420 re-fix slapcommon.c
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10154
Issue ID: 10154
Summary: Configure auto close for pull requests created on
github
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Configure the auto close action for PRs created on Github.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7420
--- Comment #9 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Ondřej Kuzník from comment #8)
> The patch in MR!665 (now in master) has introduced a regression in slapadd
> not filling in the implicit RDN attributes. Try removing line 7
> (olcDatabase: {0}config) in tests/data/slapd-dynamic.ldif and run test062.
I see, the naming check needed to happen before the schema check. Fixed now in
master.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7420
--- Comment #8 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
The patch in MR!665 (now in master) has introduced a regression in slapadd not
filling in the implicit RDN attributes. Try removing line 7 (olcDatabase:
{0}config) in tests/data/slapd-dynamic.ldif and run test062.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10156
Issue ID: 10156
Summary: Any recorded crash-consistency bugs/vulnerabilities in
LMDB for study?
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: yilegu(a)cs.washington.edu
Target Milestone: ---
Dear LMDB developers,
Hello! I am Michael Gu, a CS PhD student at the University of Washington,
advised by Prof. Baris Kasikci. We are building a software testing tool that
can test the crash-consistency of POSIX applications. The tool also supports
testing MMIO-based applications and we think LMDB is a perfect evaluation
target.
We are wondering if there are any recorded crash consistency
bugs/vulnerabilities during the development of the LMDB database. If so, could
you kindly provide some pointers to which version of the LMDB database has such
issues and if possible the Github commit or Issue ID on OpenLDAP issue tracking
system correspondingly?
Thank you so much in advance!
Bests,
Michael Gu
-----------------
Yile (Michael) Gu
CSE Ph.D. Student
University of Washington -- Paul G. Allen School of Computer Science &
Engineering
yilegu(a)cs.washington.edu
--
You are receiving this mail because:
You are on the CC list for the issue.