Full_Name: Chad Richards
Version: 2.4.15
OS: CentOS 5.2
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (12.178.116.129)
overlay chain
chain-rebind-as-user FALSE
chain-uri "ldap://XXX"
chain-rebind-as-user TRUE
chain-idassert-bind
bindmethod="simple"
binddn="cn=Manager,dc=XXX,dc=com"
credentials="secret"
mode="self"
starttls=critical
tls_reqcert=never
tls_cacertdir=/etc/openldap/cacerts
chain-tls start
chain-return-error TRUE
slapo-chain and TLS work fine connecting to the slave with LUMA, I can do
password updates and everything is fine. At first TLS slapo-chain wouldn't work
in LUMA until I added starttls=critical inside chain-idassert-bind
Now the problem I'm having is that I cannot do a passwd as root or an ldap user
from the shell prompt.
ldap.conf
ssl start_tls
tls_reqcert never
tls_checkpeer no
tls_cacertdir /etc/openldap/cacerts
Master log file when slapo-chain runs
---------------
TLS trace: SSL_accept:before/accept initialization
TLS trace: SSL_accept:SSLv3 read client hello A
TLS trace: SSL_accept:SSLv3 write server hello A
TLS trace: SSL_accept:SSLv3 write certificate A
TLS trace: SSL_accept:SSLv3 write server done A
TLS trace: SSL_accept:SSLv3 flush data
TLS trace: SSL_accept:error in SSLv3 read client certificate A
TLS trace: SSL_accept:error in SSLv3 read client certificate A
connection_get(18): got connid=6
connection_read(18): checking for input on id=6
TLS trace: SSL3 alert read:fatal:unknown CA
TLS trace: SSL_accept:failed in SSLv3 read client certificate A
TLS: can't accept: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert
unknown ca.
connection_read(18): TLS accept failure error=-1 id=6, closing
connection_close: conn=6 sd=18
Slave log file when slapo-chain runs
-----------------
TLS trace: SSL_connect:before/connect initialization
TLS trace: SSL_connect:SSLv2/v3 write client hello A
TLS trace: SSL_connect:SSLv3 read server hello A
TLS certificate verification: depth: 1, err: 19, subject:
/C=US/ST=XX/O=XX/OU=XX/CN=XX/emailAddress=XX, issuer:
/C=US/ST=XX/O=XX/OU=XX/CN=XX/emailAddress=XX
TLS certificate verification: Error, self signed certificate in certificate
chain
TLS trace: SSL3 alert write:fatal:unknown CA
TLS trace: SSL_connect:error in SSLv3 read server certificate B
TLS trace: SSL_connect:error in SSLv3 read server certificate B
TLS: can't connect: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
I had the same problem with LUMA and that problem went away when I put the
starttls=critical in the chain-idassert-bind
my ldap.conf works fine for everything else but just dies on passwd with TLS
errors with slapo-chain.
Any ideas?
Thanks!
Full_Name: Mathias Gug
Version: 2.4.15
OS: Ubuntu Linux (Jaunty - 9.04)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (64.56.226.136)
Starting with GnuTLS 2.6.3, V1 CA certs are no longer trusted by default when a
CA chain is checked. Thus libldap+gnutls breaks in existing environement when
one of the CA certs uses a V1 certificate. However libldap+openssl still
supports V1 certificates in the CA chain.
See https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/305264 for more
information.
Could libldap+gnutls be updated to also support V1 CA certificates to match
features provided by libldap+openssl?
To reproduce:
0. Need two versions of openldap : one compiled with gnutls, the other with
openssl.
1. Create a V1 CA.
2. Create a certificate to be used by slapd and sign it with the V1 CA.
3. Configure a slapd+openssl system with certificates issues above.
4. Try to connect to the slapd+openssl system with a libldap+gnutls client:
mathiaz@t-slapd-gnutls:~$ ldapsearch -b "dc=vmnet" -D "cn=admin,dc=vmnet" -x -w
mypwd -H ldaps://t-slapd-openssl./ -d 1
ldap_url_parse_ext(ldaps://t-slapd-openssl./)
ldap_create
ldap_url_parse_ext(ldaps://t-slapd-openssl.:636/??base)
ldap_sasl_bind
ldap_send_initial_request
ldap_new_connection 1 1 0
ldap_int_open_connection
ldap_connect_to_host: TCP t-slapd-openssl.:636
ldap_new_socket: 3
ldap_prepare_socket: 3
ldap_connect_to_host: Trying 172.19.42.220:636
ldap_pvt_connect: fd: 3 tm: -1 async: 0
TLS: peer cert untrusted or revoked (0x82)
TLS: can't connect: (unknown error code).
ldap_err2string
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
On a system with libldap+openssl:
mathiaz@t-slapd-openssl:~$ ldapsearch -b "dc=vmnet" -D "cn=admin,dc=vmnet" -x -w
mypwd -H ldaps://t-slapd-openssl./
# extended LDIF
#
# LDAPv3
# base <dc=vmnet> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# vmnet
dn: dc=vmnet
objectClass: top
objectClass: dcObject
objectClass: organization
o: vmnet
dc: vmnet
# admin, vmnet
dn: cn=admin,dc=vmnet
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
userPassword:: e2NyeXB0fWtlVHlnV1lleFBDWFU=
# search result
search: 2
result: 0 Success
# numResponses: 3
# numEntries: 2
$
ldapsearch is able to connect to the slapd+openssl server.
crispy(a)cluenet.org wrote:
> Full_Name: Chris Breneman
> Version: 2.4.15
> OS: Debian Lenny
> URL:
> Submission from: (NULL) (207.38.203.80)
>
>
> Using this configuration on a replication consumer, it segfaults almost
> immediately, and on startup.
> === ./slapd.d/cn=config/olcDatabase={0}config.ldif ===
> dn: olcDatabase={0}config
> objectClass: olcDatabaseConfig
> olcDatabase: {0}config
> olcAccess: {0}to * by * none
> olcAddContentAcl: TRUE
> olcLastMod: TRUE
> olcMaxDerefDepth: 15
> olcReadOnly: FALSE
> olcRootDN: cn=config
> olcRootPW:: XXXXXXXXXXX
> olcMonitoring: FALSE
> structuralObjectClass: olcDatabaseConfig
> entryUUID: 410b0970-9d47-102d-8854-57b95f7e164c
> creatorsName: cn=config
> createTimestamp: 20090304203158Z
> olcSyncrepl: {0}rid=3 provider=ldap://ldap.cluenet.org type=refreshAndPersist
> interval=00:00:01:00 retry="60 10 300 +" searchbase="cn=schema,cn=config" bin
> dmethod=simple binddn="cn=replicator,dc=cluenet,dc=org" credentials="xxxxxxxx
> xxxxxxxxx" starttls=critical tls_cacert=/etc/ssl/certs/Cluenet.pem tls_reqcer
> t=demand
> olcSyncrepl: {1}rid=4 provider=ldap://ldap.cluenet.org type=refreshAndPersist
> interval=00:00:01:00 retry="60 10 300 +" searchbase="olcDatabase={0}config,cn
> =config" attrs=olcAccess bindmethod=simple binddn="cn=replicator,dc=cluenet,d
> c=org" credentials="xxxxxxxxxxxxxxxxx" starttls=critical tls_cacert=/etc/ssl/
> certs/Cluenet.pem tls_reqcert=demand
> entryCSN: 20090304203402.651594Z#000000#000#000000
> modifiersName: cn=config
> modifyTimestamp: 20090304203402Z
This replication config is not currently supported. Fractional replication
means the consumer gets a subset of the provider's attributes. But it also
means that the consumer can *only* have that subset. Here, cn=config needs all
of its attributes in order to function, but the consumer code will attempt to
delete the non-replicated ones because they aren't part of the info received
from the provider.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
quanah(a)OpenLDAP.org wrote:
> Full_Name: Quanah Gibson-Mount
> Version: RE24/HEAD
> OS: NA
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (75.111.29.239)
>
>
> In the slapd-ldap man page, the section on idassert-bind is missing the fact
> that you can configure:
>
> starttls=no|yes|critical
>
> while listing all the other tls related keywords you can configure.
tls_protocol_min is missing as well. Also, I note the values of
starttls should be changed from "no,yes,critical" to "no,try,yes" (with
"critical" synonym of "yes"), to remove the false security perception
given by the current semantics of "yes".
The change would create minor backward compatibility issues, but no
security concern, since the meaning of "yes" would be promoted from
optional to required. Incautious users that still use "yes" would just
need to change it to "try" to restore the previous unsafe behavior.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
Full_Name: Quanah Gibson-Mount
Version: RE24/HEAD
OS: NA
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (75.111.29.239)
In the slapd-ldap man page, the section on idassert-bind is missing the fact
that you can configure:
starttls=no|yes|critical
while listing all the other tls related keywords you can configure.
Thanks for your help.
Would you be able to email your Makefile that you generated for gcc
4.0.3 on Solaris/SPARC?
I am seriously missing something. I installed lated Sun Studio 12 and
compiled with it and it's the same problem.
/M.
On Tue, Mar 3, 2009 at 2:49 PM, <hyc(a)symas.com> wrote:
> mariusp44(a)gmail.com wrote:
>> as I have pointed out in earlier post not only it doesn't work when I
>> compile it myself but also the one that was downloaded form
>> sunfreeware.com. It is not possible to tell what version of gcc was
>> used to compile openldap that is distributed but explanation that it
>> doesn't work because of compiler bug seems to me highly unlikely.
>> Unless you can specifically point to which bug in gcc on SPARC
>> contributes to this erratic behaviour of openldap.
>
> It's not our responsibility to do your legwork for you. You can easily email
> the maintainers at sunfreeware.com and ask them. Since they currently host gcc
> 3.4.6 on their site it's a safe bet they're still using gcc 3.4.x overall.
>
> Fyi, I have just now built the 2.4.15 source using gcc 4.0.3 on SPARC/Solaris
> and all of the hash mechanisms work fine. I don't have a gcc 3.x build handy
> on my system, nor do I see any reason to install a known-bad compiler just to
> further demonstrate what has already been plainly documented by other folks.
>>
>> Either way, thanks for comments.
>>
>> /M.
>>
>> On Mon, Mar 2, 2009 at 5:56 PM,<hyc(a)symas.com> Â wrote:
>>> ando(a)sys-net.it wrote:
>>>> mariusp44(a)gmail.com wrote:
>>>>> I have just compiled and tested 2.4.15 and result is same: cleartext,
>>>>> md5 and sha works, smd5, ssha and crypt doesn't.
>>>>>
>>>>> Solaris 10 SPARC latest, gcc 3.4.3, Berkeley DB 4.7.25, opessl 0.9.8j.
>>>> I have no chance to test on that arch. Â You should figure our why those
>>>> hashes are not supported. Â Did you enable crypt (--enable-crypt)?
>>> gcc 3.4.3 was released November 4 2004 http://gcc.gnu.org/gcc-3.4/
>>>
>>> and is known to have many bugs. It's also already known that old gcc releases
>>> have other problems on Sparc. (E.g. ITS#5875.)
>>>
>>> Please use a working compiler.
>>>
>>> As a workaround, recompile the offending functions with optimization disabled.
>>> That usually helps in cases like this.
>>>
>>> There is no bug in OpenLDAP Software here, 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/
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> Â -- Howard Chu
> Â CTO, Symas Corp. Â Â Â Â Â http://www.symas.com
>  Director, Highland Sun   http://highlandsun.com/hyc/
> Â Chief Architect, OpenLDAP Â http://www.openldap.org/project/
>
>
>
mariusp44(a)gmail.com wrote:
> as I have pointed out in earlier post not only it doesn't work when I
> compile it myself but also the one that was downloaded form
> sunfreeware.com. It is not possible to tell what version of gcc was
> used to compile openldap that is distributed but explanation that it
> doesn't work because of compiler bug seems to me highly unlikely.
> Unless you can specifically point to which bug in gcc on SPARC
> contributes to this erratic behaviour of openldap.
It's not our responsibility to do your legwork for you. You can easily email
the maintainers at sunfreeware.com and ask them. Since they currently host gcc
3.4.6 on their site it's a safe bet they're still using gcc 3.4.x overall.
Fyi, I have just now built the 2.4.15 source using gcc 4.0.3 on SPARC/Solaris
and all of the hash mechanisms work fine. I don't have a gcc 3.x build handy
on my system, nor do I see any reason to install a known-bad compiler just to
further demonstrate what has already been plainly documented by other folks.
>
> Either way, thanks for comments.
>
> /M.
>
> On Mon, Mar 2, 2009 at 5:56 PM,<hyc(a)symas.com> wrote:
>> ando(a)sys-net.it wrote:
>>> mariusp44(a)gmail.com wrote:
>>>> I have just compiled and tested 2.4.15 and result is same: cleartext,
>>>> md5 and sha works, smd5, ssha and crypt doesn't.
>>>>
>>>> Solaris 10 SPARC latest, gcc 3.4.3, Berkeley DB 4.7.25, opessl 0.9.8j.
>>> I have no chance to test on that arch. You should figure our why those
>>> hashes are not supported. Did you enable crypt (--enable-crypt)?
>> gcc 3.4.3 was released November 4 2004 http://gcc.gnu.org/gcc-3.4/
>>
>> and is known to have many bugs. It's also already known that old gcc releases
>> have other problems on Sparc. (E.g. ITS#5875.)
>>
>> Please use a working compiler.
>>
>> As a workaround, recompile the offending functions with optimization disabled.
>> That usually helps in cases like this.
>>
>> There is no bug in OpenLDAP Software here, 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/
>>
>>
>>
>
>
>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/