https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Rename "mirrormode" to |Rename "mirrormode" to
|"multimaster", deprecate |"multiprovider", deprecate
|"mirrormode" parameter |"mirrormode" parameter
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|has_patch, IPR_OK, |
|OL_2_5_REQ, |
|openldap-scratch |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 3716245f
by Quanah Gibson-Mount at 2020-07-22T19:32:49+00:00
Issue#8511 - Update documentation and configs to correctly use multiprovider
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9121
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 9210ed16
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 add dynamic memberOf support for static groups
• 2c0499ae
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 support nested groups
• c470af37
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 add examples to manpage
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8619
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=8619
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Keywords|OL_2_5_REQ |
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Nested group support implemented as a part of issue#9121
*** This issue has been marked as a duplicate of issue 9121 ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9121
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christ.klinge(a)web.de
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
*** Issue 8619 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=9298
Issue ID: 9298
Summary: Solaris compilation errors of OpenLDAP 2.4.50
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: mnesam(a)juniper.net
Target Milestone: ---
Created attachment 746
--> https://bugs.openldap.org/attachment.cgi?id=746&action=edit
OpenLDAP 2.4.50 solaris compilation error
Hi OpenLDAP team,
We compiled OpenLDAP 2.4.50 with OpenSSL 1.1.1 version.
It compiled without errors and worked fine.
However,, the same is giving compilation errors , when compiled with openSSL
1.0.2.
Is the compilation requirement to Openssl 1.1.1 mandatory for OpenLDAP 2.4.50
?
Regards,
Merrylin
Please find the complete log in the attachement.
I'm getting the below errors during the compilation of openLDAP 2.4.50 with
OpenSSL 1.0.2 in Solaris 5.10:
/usr/bin/gcc -m64 -m64 -o apitest apitest.o
-L/export/local/mvel/workspace/openldap_1507/openssl-1.0.2q/
-L/export/local/mvel/workspace/openldap_1507/krb5-1.18.1/src/lib/
-L/export/local/mvel/workspace/openldap_1507/krb5-1.18.1/src/lib/gssapi/
-L/export/local/mvel/workspace/openldap_1507/cyrus-sasl-2.1.27/lib/.libs/
-L/export/local/mvel/workspace/openldap_1507/cyrus-sasl-2.1.27/plugins/.libs/
./.libs/libldap.a
/export/local/mvel/workspace/openldap_1507/openldap-2.4.50/libraries/liblber/.libs/liblber.a
-L/export/local/mvel/workspace/openldap_1507/openssl-1.0.2q/lib
-L/export/local/mvel/workspace/openldap_1507/krb5-1.18.1/src/lib
-L/export/local/mvel/workspace/openldap_1507/krb5-1.18.1/src/lib/gssapi/lib
../../libraries/liblber/.libs/liblber.a ../../libraries/liblutil/liblutil.a
/export/local/mvel/workspace/openldap_1507/cyrus-sasl-2.1.27/lib/.libs//libsasl2.so
-ldl -lgss -lssl -lcrypto -lresolv -lgen -lnsl -lsocket
-R/export/local/mvel/workspace/openldap_1507/cyrus-sasl-2.1.27/lib/.libs/
-R/usr/local/lib
Undefined first referenced
symbol in file
SSL_CTX_set_options ./.libs/libldap.a(tls_o.o)
OPENSSL_sk_num ./.libs/libldap.a(tls_o.o)
BIO_meth_set_write ./.libs/libldap.a(tls_o.o)
OPENSSL_sk_free ./.libs/libldap.a(tls_o.o)
OPENSSL_sk_value ./.libs/libldap.a(tls_o.o)
TLS_method ./.libs/libldap.a(tls_o.o)
OPENSSL_init_ssl ./.libs/libldap.a(tls_o.o)
BIO_meth_new ./.libs/libldap.a(tls_o.o)
BIO_set_init ./.libs/libldap.a(tls_o.o)
BIO_get_data ./.libs/libldap.a(tls_o.o)
BIO_set_data ./.libs/libldap.a(tls_o.o)
BIO_meth_set_create ./.libs/libldap.a(tls_o.o)
ASN1_STRING_get0_data ./.libs/libldap.a(tls_o.o)
OPENSSL_sk_new_null ./.libs/libldap.a(tls_o.o)
X509_NAME_get0_der ./.libs/libldap.a(tls_o.o)
BIO_meth_free ./.libs/libldap.a(tls_o.o)
SSL_CTX_up_ref ./.libs/libldap.a(tls_o.o)
BIO_meth_set_destroy ./.libs/libldap.a(tls_o.o)
BIO_meth_set_gets ./.libs/libldap.a(tls_o.o)
BIO_meth_set_ctrl ./.libs/libldap.a(tls_o.o)
BIO_meth_set_puts ./.libs/libldap.a(tls_o.o)
BIO_meth_set_read ./.libs/libldap.a(tls_o.o)
ld: fatal: symbol referencing errors. No output written to apitest
gmake[2]: *** [apitest] Error 1
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9300
Issue ID: 9300
Summary: OpenLDAP 2.4.50 Dependency Details
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: muthaiyan1991(a)gmail.com
Target Milestone: ---
I have selected product OpenLDAP 2.4.50.. can you please answer the query?
We compiled OpenLDAP 2.4.50 with OpenSSL 1.1.1 version.
It compiled without errors and worked fine.
However,, the same is giving compilation errors , when compiled with openSSL
1.0.2.
Is the compilation requirement to Openssl 1.1.1 mandatory for OpenLDAP 2.4.50
?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9297
Issue ID: 9297
Summary: memory leak in mdb_dn2entry()
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: grapvar(a)gmail.com
Target Milestone: ---
Callers of mdb_dn2entry() expect that
mdb_dn2entry( ..., Entry **e [out], match = 1 )
provides newborn Entry if and only if [mdb_dn2entry return value in {0,
MDB_NOTFOUND}].
They are right with this, because any other error code makes asking for
"matching entry" irrelevant.
However, mdb_dn2entry does not anyhow restrict error code when generates a
"matching" Entry:
| int
| mdb_dn2entry(
| ...
| struct berval *dn,
| Entry **e,
| ...
| int matched )
| {
| ...
| int rc = mdb_dn2id( ..., dn, &id, ... );
| if ( rc ) {
| if ( matched ) {
| int rc2 = mdb_cursor_open( ..., "id2entry", &mc );
| if ( rc2 == MDB_SUCCESS ) {
| mdb_id2entry( op, mc, id, e );
| mdb_cursor_close( mc );
| }
| }
| } else ...
| ...
| return rc;
| }
So, when [mdb_dn2id return value is NOT in {0, MDB_NOTFOUND}], the Entry will
be allocated by mdb_id2entry and then leaked by a caller.
Not exactly so. Will be leaked only by mdb_search() and by mdb_add(). It looks
like that other callers of mdb_dn2entry() are, by chance, not affected by this
issue.
--
You are receiving this mail because:
You are on the CC list for the issue.