Hi Gustaf I've already did it (hg clone ...). Very good idea to add this log notice (perhaps in all modules), I think I was using 0.2, not 0.4 (I didn't check that).
Server log says ... >> Notice: nsssl: version 0.4 loaded, based on OpenSSL 1.0.1e 11 Feb 2013 I'll re-test again (https://www.ssllabs.com/ssltest/analyze.html?d=cesareox.com&hideResults=on) and now (almos) same results as next-scripting.org . My only difference is: - Chain Issues Incomplete (I already had this before). I don't know who to add ca.pem and intermediate.subclass.pem to certificate. I suppose I have to add them to certificate.pem but I didn't try. Regards, Cesáreo El 05/abril/14 15:05, Gustaf Neumann escribió: > please get nsssl from bitbucket, compile & install, and check, what > the driver says during startup in the error.log. If you have already the > tip version of naviserver installed, there is no need to recompile > naviserver > > -g > > Am 05.04.14 19:34, schrieb Cesáreo García Rodicio: >> Dear Gustaf, >> >> Yes, I suppose is very rough but to have some reference. >> >> My openssl setup (Debian): >> >openssl version >> OpenSSL 1.0.1e 11 Feb 2013 >> >> It seems to be same version. Might be something with the certificate >> (mine is StartComm Class 1)? >> >> I'll rebuild naviserver. One question, nssl builds from HEAD or I had to >> change something? >> >> Cesáreo > > > > ------------------------------------------------------------------------------ > _______________________________________________ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > ------------------------------------------------------------------------------ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
