https://bugs.openldap.org/show_bug.cgi?id=9437
Issue ID: 9437
Summary: Add OTP module to core
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Symas will contribute its OTP module for OpenLDAP 2.5 as a core overlay
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9817
Issue ID: 9817
Summary: rwm overlay : Issue with DN containing special
characters
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: thierry.pubellier(a)paris.fr
Target Milestone: ---
Hi,
I'm using rwn to select the database useg for bind operations based on the
result of a rewriteMap requets.
Sample configuration in global section :
#Rewrite Map to request a remote server
rwm-rewriteMap ldap checkEntry
"ldap://10.1.2.3/ou=users,dc=paris,dc=local?dn?sub"
binddn="cn=myuser,ou=users,dc=paris,dc=local" credentials="XXX"
# Backing up original DN
rwm-rewriteRule ".+" "${&binddn($0)}$0" ":"
# Contructing LDAP Filter for remote search. Combined with a rewrite Map,
the requested DN is returned if there is a match.
rwm-rewriteRule ".+" "(&(!(description=TEST))(distinguishedName=$0))"
":"
# If filter matches, end of rewriting. Going to 'dc=paris,dc=local'
database
rwm-rewriteRule ".+" "${checkIfPasswordExpiredDN($0)}" ":@I"
# Otherwise, restoring the original DN.
rwm-rewriteRule ".+" "${*binddn}" ":"
# And final DN massaging from "dc=paris,dc=local" to "dc=paris,dc=local2"
database
rwm-rewriteRule "(.+,)?ou=users,dc=paris,dc=local$"
"$1ou=users,dc=paris,dc=local2" ":@"
Everything goes fine until I use DN with special characters, like ',' or '['.
For example : 'cn=Pubellier\, Thierry (TEST),ou=users,dc=paris,dc=local'
In this case, the rwm-rewriteRule contructs a LDAP filter with incorrect
syntax, as special caracters are not being escaped.
I have to use some ugly tricks to escape these caracters, as shown below :
#Rewrite Map to request a remote server
rwm-rewriteMap ldap checkEntry
"ldap://10.1.2.3/ou=users,dc=paris,dc=local?dn?sub"
binddn="cn=myuser,ou=users,dc=paris,dc=local" credentials="XXX"
# Backing up original DN
rwm-rewriteRule ".+" "${&binddn($0)}$0" ":"
# Rewriting for ','
rwm-rewriteRule "(.+).\2C(.+)" "$1\\,$2"
# Adding a special '#' (asserting it in none of my DNs) suffix for special
characters, in order to escape them without looping forever
rwm-rewriteRule "(.*)([)*(\\])([^#].*|$)" "$1$2#$3"
# Escaping of special characters with dedicated '#' suffix, avoiding
infinite loops
rwm-rewriteRule "(.*)([)*(\\])#(.*)" "$1\\$2$3"
# Contructing LDAP Filter for remote search. Combined with a rewrite Map,
the requested DN is returned if there is a match.
rwm-rewriteRule ".+" "(&(!(description=TEST))(distinguishedName=$0))"
":"
# If filter matches, end of rewriting. Going to 'dc=paris,dc=local'
database
rwm-rewriteRule ".+" "${checkIfPasswordExpiredDN($0)}" ":@I"
# Otherwise, restoring the original DN.
rwm-rewriteRule ".+" "${*binddn}" ":"
# And final DN massaging from "dc=paris,dc=local" to "dc=paris,dc=local2"
database
rwm-rewriteRule "(.+,)?ou=users,dc=paris,dc=local$"
"$1ou=users,dc=paris,dc=local2" ":@"
Could there be a way to integrate the ldap escape mechanism when making an
variable assignment (like using a '#' character in place of the usual '&') ?
Thanks by advance,
Best regards,
Thierry
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9438
Issue ID: 9438
Summary: Add remoteauth overlay to core
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Symas will contribute its remoteauth overlay for OpenLDAP 2.5 as a core overlay
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9358
Issue ID: 9358
Summary: back-mdb may return accesslog entries out of order
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
back-mdb will usually return search entries in entryID order, but may do a dn
traversal instead if the count of children is smaller than the count of search
filter candidates. The RDNs are sorted in length order, not lexical order. For
accesslog, all RDNs are of equal length but if they have trailing zeroes, the
generalizedTime normalizer truncates them. Changing their lengths causes
accesslog's timestamp-based RDNs to sort in the wrong order.
The least intrusive fix is to override the syntax/normalizer for reqStart and
reqEnd attributes to not truncate trailing zeroes.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9516
Issue ID: 9516
Summary: Argon2 configuration parameters with slappasswd
Product: OpenLDAP
Version: 2.4.58
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: gilbert.kowarzyk(a)servicenow.com
Target Milestone: ---
It is currently possible to generate an Argon2 hash using slappasswd as
follows:
slappasswd -h {ARGON2} -o module-load=pw-argon2
However, I believe that it is currently not possible to provide Argon2
configuration values for parameters "m", "t", and "p" when using slappasswd.
If it is currently possible to provide these config parameters when using
slappasswd, please add documentation for how to do so.
Thanks in advance!
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9889
Issue ID: 9889
Summary: Error while installation Openldap 2.5.9
Product: OpenLDAP
Version: 2.5.9
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: vmaidarkar(a)gmail.com
Target Milestone: ---
Hi Team,
While installing OpenLDAP v2.5.9 we are getting following error "Clould not
locate TLS/SSL package.
Error:-
checking openssl/ssl.h usability... no
checking openssl/ssl.h presence... no
checking for openssl/ssl.h... no
configure:error: Could not locate TLS/SSL package
Kindly suggest to resolve this issue.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9890
Issue ID: 9890
Summary: Core is seen while reboot for RHEL_8_4_X86_64
Product: OpenLDAP
Version: 2.4.59
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: sunil.ece.126(a)gmail.com
Target Milestone: ---
Hi,
I am seeing below core while using openLdap 2.4.59. We are using openLdap in
our application as stack to initiate the connection towards ldapServer.
Current I am using RHEL_8_4_X86_64.
Core is seen whenever system is going for reboot.
Let me know if more information is required.
(gdb) bt
#0 0x00007ff94be7d998 in vtable for {}cxxabiv1::{_}_si_class_type_info () from
/lib64/libstdc++.so.6
#1 0x00007ff9520296cc in ManagedObjectList*
ManagedObject::findMOListByKey<MOID>(MOID const&) const ()
from /usr/IMS/current/bin/libMX.so.0
#2 0x00007ff9520287a5 in ManagedObject::findObjectById(MOID const&) const ()
from /usr/IMS/current/bin/libMX.so.0
#3 0x00007ff952029fa9 in SignalInstaller::signalAction(int, siginfo_t*, void*)
() from /usr/IMS/current/bin/libMX.so.0
#4 <signal handler called>
#5 memfence_check (ptr=0x7fffffff00000000, size=0x0) at src/tcmalloc.cc:294
#6 0x00007ff94c72f90d in memfence_check_and_free (ptr=<optimized out>,
size=size@entry=0x0) at src/tcmalloc.cc:307
#7 0x00007ff94c73dfe4 in free_fast_path (ptr=<optimized out>) at
src/tcmalloc.cc:2142
#8 tc_free (ptr=<optimized out>) at src/tcmalloc.cc:2149
#9 0x00007ff949d3b0ce in ldap_int_destroy_global_options () from
/lib64/libldap-2.4.so.2
#10 0x00007ff9528cfc96 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#11 0x00007ff94b1d0b0c in __run_exit_handlers () from /lib64/libc.so.6
#12 0x00007ff94b1d0c40 in exit () from /lib64/libc.so.6
#13 0x00007ff94b1ba49a in __libc_start_main () from /lib64/libc.so.6
#14 0x0000000000427b6e in _start ()
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9884
Issue ID: 9884
Summary: Document "set" patterns in ACLs
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The slapd.access(5) man page has this exceptionally unhelpful line where sets
are concerned:
"The statement set=<pattern> is undocumented yet."
Even if it is an experimental feature, it should still be documented on how it
is meant to operate.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9885
Issue ID: 9885
Summary: Error while compilation of Openldap 2.5.9
Product: OpenLDAP
Version: 2.5.9
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: rekha.shivsan(a)gmail.com
Target Milestone: ---
Created attachment 908
--> https://bugs.openldap.org/attachment.cgi?id=908&action=edit
Error while compilation
Hi,
We are trying to install Openldap v2.5.9. While running the make command we are
seeing below error.
./.libs/libldap.so: undefined reference to `BIO_meth_set_read'
./.libs/libldap.so: undefined reference to `BIO_get_data'
./.libs/libldap.so: undefined reference to `BIO_meth_set_write'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_value'
./.libs/libldap.so: undefined reference to `BIO_meth_set_ctrl'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_new_null'
./.libs/libldap.so: undefined reference to `BIO_meth_set_gets'
./.libs/libldap.so: undefined reference to `BIO_meth_set_create'
./.libs/libldap.so: undefined reference to `SSL_CTX_set_ciphersuites'
./.libs/libldap.so: undefined reference to `BIO_meth_set_puts'
./.libs/libldap.so: undefined reference to `BIO_meth_free'
./.libs/libldap.so: undefined reference to `BIO_meth_new'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_push'
./.libs/libldap.so: undefined reference to `EVP_MD_CTX_new'
./.libs/libldap.so: undefined reference to `X509_NAME_get0_der'
./.libs/libldap.so: undefined reference to `BIO_set_init'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_num'
./.libs/libldap.so: undefined reference to `SSL_CTX_up_ref'
./.libs/libldap.so: undefined reference to `OPENSSL_init_ssl'
./.libs/libldap.so: undefined reference to `ASN1_STRING_get0_data'
./.libs/libldap.so: undefined reference to `TLS_method'
./.libs/libldap.so: undefined reference to `EVP_MD_CTX_free'
./.libs/libldap.so: undefined reference to `SSL_CTX_set_options'
./.libs/libldap.so: undefined reference to `SSL_set_ciphersuites'
./.libs/libldap.so: undefined reference to `BIO_meth_set_destroy'
./.libs/libldap.so: undefined reference to `SSL_session_reused'
./.libs/libldap.so: undefined reference to `X509_get_X509_PUBKEY'
./.libs/libldap.so: undefined reference to `OPENSSL_sk_free'
./.libs/libldap.so: undefined reference to `BIO_set_data'
./.libs/libldap.so: undefined reference to `SSL_CTX_clear_options'
collect2: error: ld returned 1 exit status
Complete error logs are attached " OpenLdap 2.5.9_error.txt".
Could you please help to resolve this issue.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9873
Issue ID: 9873
Summary: idle timeout by backends close connections
Product: OpenLDAP
Version: 2.6.2
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ettorevi(a)gmail.com
Target Milestone: ---
Hi,
making searches through lloadd to a bunch of backends returns weird results
Sometimes I get:
| ldap_bind: Other (e.g., implementation specific) error (80)
| additional info: connection to the remote server has been severed
Others
ldap_result: Can't contact LDAP server (-1)
due to an idle_timeout from the backend in the middle of the search, in a non
deterministic way.
If I search directly on the backends everything works
ldapsearch -x -Hldaps://lloadd.server 'objectClass=*' -w pwd
[...]
# numResponses: 9620
# numEntries: 9620
ldap_result: Can't contact LDAP server (-1)
lloadd compiled standalone from 2.6.2 with:
--enable-balancer=yes --enable-syslog --enable-debug --enable-slapd=no
Backends are older, 2.4.49+dfsg-2ubuntu1.9 from Ubuntu 20.04
Any hints?
Thank you
--
You are receiving this mail because:
You are on the CC list for the issue.