https://bugs.openldap.org/show_bug.cgi?id=8835
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 58caa2f8
by Quanah Gibson-Mount at 2021-02-22T15:59:15+00:00
ITS#8835 - Update to use rehash command from OpenSSL
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9476
Issue ID: 9476
Summary: Documentation error for MDB_GET_BOTH_RANGE
Product: LMDB
Version: 0.9.28
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: jaqenn(a)hotmail.com
Target Milestone: ---
The documentation for MDB_GET_BOTH_RANGE is incorrect.
This operation is documented as 'position at key, nearest data'. It appears to
me that it should instead say 'position at key, first data greater than or
equal to specified data'.
If I call mdb_cursor_get with a valid key and a data smaller than all existing
values, then lmdb returns MDB_SUCCESS and the cursor is positioned at the first
value.
If I call mdb_cursor_get with a valid key and a data larger than all existing
values, then lmdb returns MDB_NOTFOUND and the cursor is not repositioned.
The documentation 'nearest data' makes me expect that if I call mdb_cursor_get
with a valid key and a data larger than all existing values, then lmdb would
return MDB_SUCCESS and the cursor is positioned at the last value.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9332
Issue ID: 9332
Summary: Compilation of 2.4.52 fails: "init.c", line 45: too
many initializers for scalar
Product: OpenLDAP
Version: 2.4.52
Hardware: All
OS: Solaris
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: stacey.marshall(a)gmail.com
Target Milestone: ---
The addition of integer ldo_tls_require_san to structure requires an additional
initialization digit to macro LDAP_LDO_TLS_NULLARG.
--- openldap-2.4.52/libraries/libldap/ldap-int.h 2020-08-28
09:10:00.000000000 -0700
+++ openldap-2.4.52.x/libraries/libldap/ldap-int.h 2020-09-01
10:08:44.661226154 -0700
@@ -263,7 +263,7 @@
int ldo_tls_impl;
int ldo_tls_crlcheck;
int ldo_tls_require_san;
-#define LDAP_LDO_TLS_NULLARG ,0,0,0,{0,0,0,0,0,0,0,0,0},0,0,0,0
+#define LDAP_LDO_TLS_NULLARG ,0,0,0,{0,0,0,0,0,0,0,0,0},0,0,0,0,0
#else
#define LDAP_LDO_TLS_NULLARG
#endif
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
--- Comment #19 from jens.schleusener(a)fossies.org <jens.schleusener(a)fossies.org> ---
> Feel free to configure it to email me directly for both openldap master and
> lmdb master.
Done.
And congratulations for the now "perfect" status.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
--- Comment #18 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to jens.schleusener(a)fossies.org from comment #13)
> By the way, there exists also the possibility to be informed by email if new
> misspellings are detected but that may be a bit annoying ;-)
Feel free to configure it to email me directly for both openldap master and
lmdb master.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #17 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• a48d8b48
by Quanah Gibson-Mount at 2021-02-18T20:25:35+00:00
ITS#9161 - A few more typo fixes
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8977
--- Comment #13 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #8)
> --On Thursday, June 27, 2019 8:56 PM +0000 quanah(a)symas.com wrote:
>
> > --On Thursday, June 27, 2019 8:35 PM +0000 hyc(a)symas.com wrote:
> >
> >> No, because order is irrelevant for these.
> >
> > Cool, thanks! I'll continue on with deeper testing then. :)
>
> Given the current implementation of OpenLDAP, this feature is impossible to
> use w/o recompiling OpenLDAP when a change to the IDL size is made. This
> is because LDAP_PVT_THREAD_STACK_SIZE must be adjusted as well and that
> requires a recompile.
>
> The default size for LDAP_PVT_THREAD_STACK_SIZE is:
>
> ( 1 * 1024 * 1024 * sizeof(void *) )
>
> which works for an IDL size of 16 (2^16) which is 65536.
>
> If you change the IDL size, say to 22, then the new IDL size is: 4,194,304.
> We then use this difference to find the offset we need to adjust
> LDAP_PVT_THREAD_STACK_SIZE by:
>
> 4194304/65536 = 64
>
> So it needs to be 64 time larger:
>
> ( 64 * 1024 * 1024 * sizeof(void *) )
>
>
> Generally, this feature is simply unusuable (currently) as a tunable given
> the requirement for recompiling OpenLDAP to use it.
I believe the above explanation is incorrect, so want to update it.
1024*1024^2 = 1,048,576
This appears to work with an idlexp of 20, which is also 1,048,576
So really what is required is that the LDAP_PVT_THREAD_STACK_SIZE_VALUE total
needs to match the 2^idlexp value.
So, 2^22 is 4,194,304, so in this case, the LDAP_PVT_THREAD_STACK_SIZE_VALUE
would need to be recompiled as ( 4 * 1024 * 1024 * sizeof(void *) )
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8977
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ, reviewed |
Target Milestone|2.4.53 |2.6.0
Assignee|quanah(a)openldap.org |bugs(a)openldap.org
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• a40f6bff
by Quanah Gibson-Mount at 2021-02-18T18:47:40+00:00
ITS#8977 - Remove documentation for idlexp
The idlexp feature depends on additional work that is not yet done. Remove
documentation for the feature
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8835
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.5.2
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8835
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
https://git.openldap.org/openldap/openldap/-/merge_requests/246
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9180
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
Target Milestone|--- |2.5.2
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• e6cf2378
by OndÅ™ej KuznÃk at 2021-02-18T16:28:12+00:00
ITS#9180 Mark memberof deprecated
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |IN_PROGRESS
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|TEST |---
Status|RESOLVED |CONFIRMED
--- Comment #16 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
For the remaining typos in master:
https://git.openldap.org/openldap/openldap/-/merge_requests/244
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8865
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=8865
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8104
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.3 |---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7744
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|has_patch |
Target Milestone|2.5.3 |2.5.2
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• c25fa7b0
by Jan Synacek at 2021-02-18T14:45:51+00:00
ITS#7744 Fix TLS_REQCERT description
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8861
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.3 |2.5.2
Keywords|OL_2_5_REQ |
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• dfd8515e
by Howard Chu at 2021-02-18T14:33:16+00:00
ITS#8861 clarify tls keyword
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7795
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.3 |2.5.2
--- Comment #12 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 70a7f517
by Howard Chu at 2021-02-18T13:23:47+00:00
ITS#7795 more detail for "manage" priv
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7744
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Howard Chu <hyc(a)openldap.org> ---
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=8861
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|CONFIRMED |RESOLVED
--- Comment #6 from Howard Chu <hyc(a)openldap.org> ---
fixed 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=8861
--- Comment #5 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #4)
> (In reply to Howard Chu from comment #3)
>
> > Sounds more like the back-ldap manpage is wrong. The use of "ldaps" is
> > implicit in the URI, so there's no point in supporting it here and it should
> > be an error to allow it here. In particular it makes no sense to allow it
> > here if it differs from the URI.
>
> Ok, although that doesn't entirely answer the rest of my question (i.e.,
> about tls_reqcert etc missing from back-meta).
>
> Ironically I would note you're literally the person who added the "ldaps"
> option to back-ldap.
>
> a6a8fb514b (Howard Chu 2007-01-08 23:36:24 +0000 511) {
> BER_BVC( "ldaps" ), LDAP_BACK_F_TLS_LDAPS },
The original text in that commit is more clear:
+Specify the use of TLS when a regular connection is initialized. The
+StartTLS extended operation will be used unless the URI directive protocol
+scheme is \fBldaps://\fP. In that case this keyword may only be
+set to "ldaps" and the StartTLS operation will not be used.
So this setting is required to agree with the URI. The only reason this
keyword is defined here is because slap_bindconf_unparse emits it for ldaps
URIs and it would have taken extra work to omit it.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9161
--- Comment #15 from jens.schleusener(a)fossies.org <jens.schleusener(a)fossies.org> ---
Oops, again overseen, now corrected.
By the way, the according Doxygen related information are also used by Fossies
https://fossies.org/dox/openldap/lmdb_8h.html
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8104
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
images are present.
--
You are receiving this mail because:
You are on the CC list for the issue.