directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Riddering (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-2043) SSL connection failures errors are useless
Date Tue, 18 Oct 2016 09:13:58 GMT


Andreas Riddering commented on DIRSERVER-2043:

As i edited in my last answer, i messed up with the title of this ticket and my request is
about die ADStudio not the server. Sorry for the confusion. So as its not ApacheDirServer,
but IBM SDS its written in C and the JVM Parameter cant be applied.
Nevertheless i did some testing. Installing Java8 leads to some strange behaviour, so connection
to one of the two servers in charge is possible, but not to the other. Versions differ only
a little bit. (Remember, with Java7 > .85 a connection to non of the two was possible...)

At this point i took openssl and did some tests and while connecting to the server with the
problems openssl throws up some strange SSL3 "bad record mac" errors... Interestingly i don't
get those errors, if i put -ssl3 or -tls1 as a parameter to openssl.

ldapsearch on cygwin on my local machine also can't connect to the server in question, same
"bad record mac"-error, but ldapsearch on another linux-server is able to connect to both

So my conclusion is, that this unpatched server has some problems with the "autonegotation"
of the ssl/tls protocol or something like that. So no todo left here, but thank you for your

> SSL connection failures errors are useless
> ------------------------------------------
>                 Key: DIRSERVER-2043
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M19
>            Reporter: Roy Wellington
>            Priority: Minor
> When connecting, if StartTLS fails, you get an error such as the following:
> {noformat}
> Error while opening connection
>  - SSL handshake failed.
> SSL handshake
> 	at
> 	at
> 	at
> 	at$
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> SSL handshake failed.
> {noformat}
> But _why_ did the SSL handshake fail? I don't need the stack trace, I need to know what
exactly failed, something like what Firefox/Chrome do on SSL failures. I'm trying to debug
this right now, and I have absolutely no idea what's going on here.

This message was sent by Atlassian JIRA

View raw message