Bug#422730: lbdb: Please allow mutt_ldap_query to use local UNIX domain socket
Hi Roberto! On Mon, 07 May 2007, Roberto C. Sanchez wrote: > Please update mutt_ldap_query to allow the use of a local UNIX domain > socket (i.e., ldapi:/// or /var/run/ldapi) for communication to the LDAP > server. Such a feature was introduced with version 0.35.1 but not fully documented (the documentation only talks ablout ldaps://, but ldapi:// should work in a similar way). You can give an ldapi URI in hostname field. According to Net::LDAP following should be possible there: You can also specify a URI, such as 'ldaps://127.0.0.1:666' or 'ldapi://%2fvar%2flib%2fldap_sock'. Note that '%2f's in the LDAPI socket path will be translated into '/'. This is to support LDAP query options like base, search etc. although the query part of the URI will be ignored in this context. If port was not specified in the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS' schemes respectively. I don't haven an ldaps server available, so please try this out and tell me whether it works for you. Tscho Roland pgp81D6hYhQ9m.pgp Description: PGP signature
Bug#422730: lbdb: Please allow mutt_ldap_query to use local UNIX domain socket
On Sat, Jun 16, 2007 at 08:33:06PM +0200, Roland Rosenfeld wrote: > Hi Roberto! > > On Mon, 07 May 2007, Roberto C. Sanchez wrote: > > > Please update mutt_ldap_query to allow the use of a local UNIX domain > > socket (i.e., ldapi:/// or /var/run/ldapi) for communication to the LDAP > > server. > > Such a feature was introduced with version 0.35.1 but not fully > documented (the documentation only talks ablout ldaps://, but ldapi:// > should work in a similar way). You can give an ldapi URI in hostname > field. According to Net::LDAP following should be possible there: > Hmm. I am using Etch on my machines, which has lbdb version 0.34. If I get some time this summer, I will backport the version from unstable/testing and give it a try. > You can also specify a URI, such as 'ldaps://127.0.0.1:666' or > 'ldapi://%2fvar%2flib%2fldap_sock'. Note that '%2f's in the LDAPI > socket path will be translated into '/'. This is to support LDAP query > options like base, search etc. although the query part of the URI will > be ignored in this context. If port was not specified in the URI, the > default is either 389 or 636 for 'LDAP' and 'LDAPS' schemes > respectively. > > I don't haven an ldaps server available, so please try this out and > tell me whether it works for you. > Here is my config: $ldap_server = 'ldaps://santiago.connexer.com'; $search_base = 'ou=Addressbook,dc=connexer,dc=com'; $ldap_search_fields = 'givenname sn cn mail'; $ldap_expected_answers = 'givenname sn cn mail'; $ldap_result_email = '${mail}'; $ldap_result_realname = '${givenname} ${sn}'; $ldap_result_comment = '(LDAP)'; $ignorant = 0; $ldap_bind_dn = ''; $ldap_bind_password = ''; This works for me both on Sarge and on Etch. Just to clarify, though, you are saying that with the new version I should be able to specify 'ldapi://%2fvar%2frun%2fldapi' and have it connect to a slapd running on the local host? Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#422730: lbdb: Please allow mutt_ldap_query to use local UNIX domain socket
On Sat, 16 Jun 2007, Roberto C.Sánchez wrote: > Hmm. I am using Etch on my machines, which has lbdb version 0.34. > If I get some time this summer, I will backport the version from > unstable/testing and give it a try. Just try the binary, I placed on http://www.spinnaker.de/debian/unoff/lbdb.html > Just to clarify, though, you are saying that with the new version I > should be able to specify 'ldapi://%2fvar%2frun%2fldapi' and have it > connect to a slapd running on the local host? Yes, I always think "socket" and write "ldapS" when I mean "ldapi". Stupid me... Tscho Roland pgpG7FtwKyvB0.pgp Description: PGP signature
Bug#422730: lbdb: Please allow mutt_ldap_query to use local UNIX domain socket
package lbdb retitle 422730 lbdb: Please document how to access LDAP via UNIX domain socket thanks Roland, I was going through some old mails and wanted to follow up. On Sun, Jun 17, 2007 at 02:23:23PM +0200, Roland Rosenfeld wrote: > On Sat, 16 Jun 2007, Roberto C.Sánchez wrote: > > > Hmm. I am using Etch on my machines, which has lbdb version 0.34. > > If I get some time this summer, I will backport the version from > > unstable/testing and give it a try. > > Just try the binary, I placed on > http://www.spinnaker.de/debian/unoff/lbdb.html > That was not necessary. It turns out that your suggestion below works on versio 0.34. > > Just to clarify, though, you are saying that with the new version I > > should be able to specify 'ldapi://%2fvar%2frun%2fldapi' and have it > > connect to a slapd running on the local host? > > Yes, I always think "socket" and write "ldapS" when I mean "ldapi". > Stupid me... > I would be happy if this could be better documented. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#422730: lbdb: Please allow mutt_ldap_query to use local UNIX domain socket
Package: lbdb Version: 0.34 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please update mutt_ldap_query to allow the use of a local UNIX domain socket (i.e., ldapi:/// or /var/run/ldapi) for communication to the LDAP server. Regards, - -Roberto - -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1) Versions of packages lbdb depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libvformat1 1.13-4 Library to read and write vcard fi ii perl5.8.8-7 Larry Wall's Practical Extraction lbdb recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGP7Mn5SXWIKfIlGQRAoYlAJ9ZevcZLdbxSjEBCypl5o6roIQs+ACfaYte pflCsvZ4b2plhCYt/ODbbc0= =mcB/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]