Your message dated Mon, 19 May 2014 21:38:56 -0700
with message-id <[email protected]>
and subject line libldap2: failed to get attributeTypes when connected to ldaps
has caused the Debian Bug report #212883,
regarding libldap2: failed to get attributeTypes when connected to ldaps
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
212883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=212883
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libldap2
Version: 2.1.22-1
Severity: normal
Tags: sid

hi

there seems to be a problem with fetching the attributeTypes:

normally a search like this:
ldapsearch -H ldap://azrael.azrael.de/ -D "cn=admin,dc=debian,dc=org" -U admin 
-b "cn=Subschema" -s base objectClass=* attributeTypes

will yield a list will all the attribute types :)

but if the query is changed to this:
ldapsearch -H ldaps://azrael.azrael.de/ -D "cn=admin,dc=debian,dc=org" -U admin 
-b "cn=Subschema" -s base objectClass=* attributeTypes

it will refuse to work with a ldap_result: Can't contact LDAP server (81) error

but when i try to search with:
ldapsearch -H "ldaps://azrael.azrael.de" -U admin -D 
"cn=admin,dc=debian,dc=org" -s sub -b 'ou=people,dc=debian,dc=org' cn=*

it will return the requested entries

i turned debugging on with -d 127 and this showed that server transmit the 
information on the second case (the search for attributeTypes and ldaps) and 
closes the connection just normal. no error at all

here is the error the client gives with -d 9:

ldap_chkResponseList for msgid=-1, all=0
ldap_chkResponseList returns NULL
ldap_int_select
read1msg: msgid -1, all 0
ber_get_next
ber_get_next failed.
ldap_perror
ldap_result: Can't contact LDAP server (81)
ldap_unbind
ldap_free_request (origid 4, msgid 4)
ldap_free_connection
ldap_send_unbind
ber_flush: 7 bytes to sd 3
ldap_free_connection: actually freed

maybe its just a misconfiguration...

Armin

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux azrael 2.4.20 #2 Wed Jul 2 22:09:02 CEST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages libldap2 depends on:
ii  libc6                         2.3.2-7    GNU C Library: Shared libraries an
ii  libgnutls7                    0.8.9-2    GNU TLS library - runtime library
ii  libsasl2                      2.1.15-5   Authentication abstraction library

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

This is a very old bug. I'm sorry to see it never got a response.

In current versions of openldap this works for me. I'm able to retrieve subschema info over ldaps as well as ldap+STARTTLS.

I wasn't able to find more details about this or exactly when it was fixed.

thanks,
Ryan

--- End Message ---

Reply via email to