Full_Name: John Morrissey
Version: 2.4.16
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (2001:4978:194:0:21f:5bff:fee9:da92)
tlsg_ctx_init() doesn't initialize the gnutls_x509_privkey_t structure before
passing it to gnutls_x509_privkey_import. This yields:
main: TLS init def ctx failed: -50
on slapd startup. gnutls error -50 is GNUTLS_E_INVALID_REQUEST. Initializing the
structure with gnutls_x509_privkey_init() allows slapd startup to succeed.
[jwm@coral.lab.isis:pts/1 ~> dpkg -l libgnutls26
[...]
ii libgnutls26 2.6.4-2 the GNU TLS library - runtime library
--- openldap-2.4.16.orig/libraries/libldap/tls_g.c
+++ openldap-2.4.16/libraries/libldap/tls_g.c
@@ -354,6 +354,9 @@
gnutls_x509_crt_t certs[VERIFY_DEPTH];
unsigned int max = VERIFY_DEPTH;
+ rc = gnutls_x509_privkey_init(&key);
+ if ( rc < 0 ) return -1;
+
/* OpenSSL builds the cert chain for us, but GnuTLS
* expects it to be present in the certfile. If it's
* not, we have to build it ourselves. So we have to
luca.scamoni(a)sys-net.it ha scritto:
> luca.scamoni(a)sys-net.it ha scritto:
New update
The problem is still there. Same call in bdb_rdn_cmp.
strncmp fails because one of the berval passed to the function has
inconsistent values between bv_len and bv_val
Ing. Luca Scamoni
Responsabile Ricerca e Sviluppo
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office: +39 0382 573859 (137)
Fax: +39 0382 476497
Email: luca.scamoni(a)sys-net.it
-----------------------------------
Full_Name: Kostas Kalevras
Version: 2.4
OS: FreeBSD
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (147.102.247.75)
In OpenLDAP 2.4 Administration Guide, chapter 15 (Using SASL) in
15.3.3.1. Notes on Proxy Authorization Rules
the documentation states that the administrator can use regular expression
matching like:
authzTo: dn.regex=^uid=[^,]*,dc=example,dc=com$
I believe the correct form should be:
authzTo: dn.regex:"^uid=[^,]*,dc=example,dc=com$"
Notice the : instead of = and the quotes around the regular expression.
Full_Name: Hendrik Saly
Version: JLDAP 4.3
OS: Linux 2.6, Sun JDK 1.5
URL: http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/com/novell…
Submission from: (NULL) (78.43.136.21)
While trying to use SASL with JLDAP i encounter a potential minor bug in
$OpenLDAP: pkg/jldap/com/novell/ldap/LDAPConnection.java,v 1.154 2006/02/09
08:43:45 sunilk Exp $
Seems the bind method on line 1730 fails to release the bind semaphore properly
under some circumstances. I tried to use more than the wit JLDAP provided SASL
mechanisms DIGESTMD5 and EXTERNAL by wrapping the novell sasl client with a Java
1.5 sasl client. All works very well but CRAM login for example fails. I have a
workaround http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/com/novell…
but i thinks there are some problems with the bind semaphore.
The wrapping code is here
http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/org/mule/t…
If neccessary i can provide a test suite for this.
Thanks
Hendrik
tmackey(a)zetta.net wrote:
> Full_Name: Theral Mackey
> Version: 2.4.16
> OS: Linux/Debian
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (216.200.8.2)
>
>
> Running make install leaves an existing slapd.conf alone, but happily nukes and
> replaces the existing schema directory, taking with it any additional or custom
> schema, leaving you with only the ones installed by default (hooray for svn and
> backups!).
No, it doesn't.
> For consistency, it should probably either nuke slapd.conf as well, or leave an
> existing schema dir alone (I vote for option 2).
> fix should be as simple as an 'if [ ! -d $base/schema ] ; then (mkdir, cp
> schemas, etc) ; fi' around where it drops the schemas in place in the Makefile
Since you're already looking in the Makefile, you should see this for the
install-schema: rule...
###
install-schema: FORCE
@if test -d $(DESTDIR)$(schemadir) ; then \
echo "MOVING EXISTING SCHEMA DIR to $(DESTDIR)$(schemadir).$$$$" ; \
mv $(DESTDIR)$(schemadir) $(DESTDIR)$(schemadir).$$$$ ; \
fi
$(MKDIR) $(DESTDIR)$(schemadir)
###
The existing schema directory is simply renamed / moved out of the way. If you
had any custom schema files stored there, they are still there.
This ITS will be closed.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Theral Mackey
Version: 2.4.16
OS: Linux/Debian
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (216.200.8.2)
Running make install leaves an existing slapd.conf alone, but happily nukes and
replaces the existing schema directory, taking with it any additional or custom
schema, leaving you with only the ones installed by default (hooray for svn and
backups!).
For consistency, it should probably either nuke slapd.conf as well, or leave an
existing schema dir alone (I vote for option 2).
fix should be as simple as an 'if [ ! -d $base/schema ] ; then (mkdir, cp
schemas, etc) ; fi' around where it drops the schemas in place in the Makefile
neil.dunbar(a)hp.com wrote:
> On Tue, 2008-12-16 at 14:52 +0000, Neil Dunbar wrote:
>> Andrew:
>>> One suggestion following a very quick scan of the code: I think it
>>> would be worth bringing the warning about turning off TLS checks
>>> into the manual page.
>>
>> Agreed. Done.
>>
>>> In particular, there is no reason for this
>>> to be AD-specific and it should be easy to adapt it to authenticate
>>> against any [collection of] remote LDAP servers.
>>
>> Actually, it may not be AD specific as is.
>
> Are we any further forward to getting this rolled into contrib? Is there
> more we need to do to make it fit better? The tarball has been sitting
> there a while, it would seem.
I've reviewed the package and have some comments.
I'm puzzled by the design of this overlay; in ActiveDirectory a user can exist
in only one domain and there is a one-to-one mapping between their domain name
and the suffix of their LDAP DN. As such, the lookup of the
adauth_domain_attribute seems clumsy and unnecessary.
The adauth_default_realm and adauth_default_domain terms are confusing. Your
adauth_default_realm item is really just the hostname of a particular server.
Your use of the word "realm" is basically inconsistent with common usage of
this term.
The usage for adauth_mapping is clumsy; you could simply have made it a list
of LDAP URLs and not bothered with an external file. Is there a commonly used
external file that other software uses, that prompted this approach?
The description of adauth_dn_attribute is misleading. Is it a DN, or is it a
userPrincipalName? In what way is this a "map" at all? Examining the code, it
is simply "the DN of the user to Bind against on the remote LDAP server" - it
is not a map, nor is it a userPrincipalName.
I wonder in what context this overlay is easily used. If I have 100,000 users
in my LDAP directory, I don't want to maintain 100,000 AD_DN attributes for
them; I want a simple rule that actually performs an algorithmic mapping of
their local DN to their remote DN. I suppose using an AD_DN attribute for the
users whose DNs don't easily map might be a good fallback, but it shouldn't be
the primary mechanism for linking a local user to a remote user. I would
re-use the authz-regexp machinery here.
It seems there's a lot of AD-specific overhead in this code, for what is
really a pretty simple and generic operation - passthru Bind to a remote LDAP
server. I would have used the back-ldap/chain.c code instead, which would also
provide connection pooling and the other benefits of back-ldap's already
comprehensive support for communicating with remote LDAP servers.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Jan Zeleny
Version: 2.4.15
OS: Fedora 11
URL: http://jzeleny.fedorapeople.org/patches/openldap/openldap-options.patch
Submission from: (NULL) (62.40.79.66)
Client tools share a part of help printed to stdout. In this shared help, there
are some options, even if they are not in fact supported by all client tools.
I've made a simple patch to resolve this minor issue.