Re: ldap e rubriche condivise
On Thu, May 22, 2003 at 09:04:47PM +0200, Whiterabbit wrote:
> Ciao a tutti, ho quasi completato il mio sever LDAP casalingo, e ho un
> paio di dubbi riguardanti la gestione delle info dell' utente tramite
> client di posta (mozilla o $outlookexpress$)...
Ti preeeeego!
dimmi che sei riuscito a configurare LDAP anche per l'autenticazione
centralizzata, e che stai scrivendo un HOWTO in italiano, bello,
semplie, completo e che funzioni.
Io sto seguendo questo http://freego.it/articles.php?show=42 , ma sono
bloccato alla configurazione lato client.
# ldapsearch -x
ldap_bind: Can't contact LDAP server
additional info: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
mentre il server dice:
# /usr/sbin/slapd -h 'ldaps:///' -d 1
@(#) $OpenLDAP: slapd 2.0.23-Release (sab mag 17 18:27:44 CEST 2003) $
root@fingolfin:/usr/src/openldap2-2.0.23/debian/build/servers/slapd
daemon_init: listen on ldaps:///
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldaps:///)
daemon: socket() failed errno=97 (Address family not supported
by protocol)
daemon: initialized ldaps:///
daemon_init: 1 listeners opened
slapd init: initiated server.
slap_sasl_init: initialized!
==>backsql_initialize()
<==backsql_initialize()
slapd startup: initiated.
slapd starting
ldap_pvt_gethostbyname_a: host=fingolfin, r=0
connection_get(9): got connid=0
connection_read(9): checking for input on id=0
TLS trace: SSL_accept:before/accept initialization
TLS trace: SSL3 alert write:fatal:handshake failure
TLS trace: SSL_accept:error in SSLv3 read client hello B
TLS trace: SSL_accept:error in SSLv3 read client hello B
TLS: can't accept.
TLS: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared
cipher s3_srvr.c:852
connection_read(9): TLS accept error error=-1 id=0, closing
connection_closing: readying conn=0 sd=9 for close
connection_close: conn=0 sd=9
Fiducioso in un howto,
Werewolf.
--
Matteo D'Alfonso \ /
werewolf(at)pavia.linux.it \/\/
http://bagginslab.hopto.org/ /\/\
http://pavia.linux.it/ / \
Reply to: