https://bugs.openldap.org/show_bug.cgi?id=9643
Issue ID: 9643
Summary: back-wt: entry_decode failure.
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hamano(a)osstech.co.jp
Target Milestone: ---
https://bugs.openldap.org/show_bug.cgi?id=9463
ondra mentioned:
> e.g. ./run -b wt -l 50 test034
I reproduced the issue by iterating test034.
And I figure out the issue is in entry_encode/decode.
It happens stochastically by reading memory outside the malloc area when
decoding special entry (only dn entry without attributes).
Since entry_encode/decode was originally used by back-bdb and back-hdb, these
backends also had this problem.
Currently It seems that only back-wt is using entry_encode/decode.
I'll fork entry_encode/decode and create wt_entry_encode/decode.
Then, we can remove entry_encode/decode.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9636
Issue ID: 9636
Summary: delete back-shell
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The back-shell backend was removed starting with OpenLDAP 2.5. It should also
be removed from the head development branch.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9635
Issue ID: 9635
Summary: Delete back-ndb
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The back-ndb backend is deprecated and given Oracle's unwillingness to further
defvelopment it is a dead project. Time to remove it.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7080
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=6949
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=9720
Issue ID: 9720
Summary: accesslog mincsn needs initialization
Product: OpenLDAP
Version: 2.5.8
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
As reported on the -technical list, if using slapcat/slapadd to migrate an
accesslog db from 2.4 to 2.5, the mincsn attribute will not be initialized
causing a segfault on startup.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9670
Issue ID: 9670
Summary: Roadmap has bogus items for 2.6/2.7
Product: website
Version: unspecified
Hardware: All
URL: https://openldap.org/software/roadmap.html
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
- lloadd has supported "all" LDAP operation types since being merged in 2.5
- both ppolicy enhancements are bogus too
- logging landed in 2.6 already
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9724
Issue ID: 9724
Summary: FreeBSD: fetch(3) should not require com_err library
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: delphij(a)freebsd.org
Target Milestone: ---
This is reported at https://bugs.freebsd.org/259345 .
fetch(3) support was added in 48d5465ab76af3739294584e25985b0cf368ad05 and
com_err library was added as a dependency, at the time it was a dependency.
However, shortly after that in 2000
(https://cgit.freebsd.org/src/commit/?id=ba101983d5c240f191e3f233907ebb4a6c7…),
the dependency was removed, and beginning from FreeBSD 5.0 (released on January
14, 2003), the dependency was gone and do not exist in modern FreeBSD versions.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8874
Xin Li <delphij(a)freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |delphij(a)freebsd.org
--- Comment #6 from Xin Li <delphij(a)freebsd.org> ---
*** Issue 9724 has been marked as a duplicate of this issue. ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9722
Issue ID: 9722
Summary: UX defect in screen to specify new password
Product: OpenLDAP
Version: unspecified
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: christos.hayward(a)gmail.com
Target Milestone: ---
On a Debian 10 Linode, I ran:
"aptitude install slapd ldap-utils".
The screen prompting for a password was written in a way that led me to believe
I was being asked for a password previously set as an LDAP password.
This reflects a UX defect.
I suggest a wording that shows clearly that one is being asked to assign a new
password to LDAP, not enter a pre-existing password already assigned to LDAP.
--
You are receiving this mail because:
You are on the CC list for the issue.