Issue with upgrading to 2.3.6

[Halm Reusser]

On 29.02.12 14:51, Peter Schwindt wrote:
> I checked with a handful of SSL tools and all I found out was, that
> upper mentioned server does have i ts IP as the CN in the cert. So
> that looks really ok for me.

Your problem could be that the IP isn't in the subjectAltName?

http://code.google.com/p/vt-middleware/source/browse/vt-ldap/branches/vt-ldap-3/src/main/java/edu/vt/middleware/ldap/ssl/DefaultHostnameVerifier.java?spec=svn2217&r=2217#137

(sorry I didn't find any published java doc)

Although this is RFC compliant, I guess a lot of deployers will struggle
- especially if they used CNs/subjectAltNames in a mixed way.

-Halm