https://bugs.openldap.org/show_bug.cgi?id=7595
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9687
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Re25:
• 2a537ad0
by Ondřej Kuzník at 2021-09-14T16:17:45+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• ea92405a
by Ondřej Kuzník at 2021-09-14T16:17:25+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• bfe3d19e
by Ondřej Kuzník at 2021-09-09T10:26:06+01:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9619
Issue ID: 9619
Summary: mdb_env_copy2 with MDB_CP_COMPACT in mdb.master3
produces corrupt mdb file
Product: LMDB
Version: 0.9.29
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: kriszyp(a)gmail.com
Target Milestone: ---
When copying an LMDB database with mdb_env_copy2 with the MDB_CP_COMPACT with
mdb.master3, the resulting mdb file seems to be corrupt and when using it in
LMDB, I get segmentation faults. Copying without the compacting flag seems to
work fine. I apologize, I know this is not a very good issue report, as I
haven't had a chance to actually narrow this down to a more
reproducible/isolated case, or look for how to patch. I thought I would report
in case there are any ideas on what could cause this. The segmentation faults
always seem to be memory write faults (as opposed to try fault on trying to
read). Or perhaps the current backup/copying functionality is eventually going
to be replaced by incremental backup/copying anyway
(https://twitter.com/hyc_symas/status/1315651814096875520). I'll try to update
this if I get a chance to investigate more, but otherwise feel free to
ignore/consider low-priority since the work around is easy.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE25:
commit a00ec090bdcdfdb390ace2238f581ad147e5974f
Author: Ondřej Kuzník <ondra(a)mistotebe.net>
Date: Tue Jun 1 13:56:58 2021 +0100
ITS#6467 Free uuid list after we're finished
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
commit 726a2031334d066a6e463d7b992b6ca7b390e631
Author: Ondřej Kuzník <ondra(a)mistotebe.net>
Date: Tue Jun 1 13:56:58 2021 +0100
ITS#6467 Free uuid list after we're finished
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9571
Issue ID: 9571
Summary: Add Behera Draft 8 compatibility flag to ppolicy
overlay
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: mhardin(a)symas.com
Target Milestone: ---
The RFC for Behera Password Policy, Draft, 10 changes modification semantics of
certain policy attributes from those that were in effect in Draft 8. To
preserve compatibility with applications that depend on the Draft 8 semantics,
a compatibility flag needs to be added to the ppolicy configuration that
restores the Draft 8 semantics.
--
You are receiving this mail because:
You are on the CC list for the issue.