Author
Topic: New SSL Cert for Jabber @phcn.de (Read 5541 times)

We have upgraded our Jabber SSL Cert with our self-signed RootCA (like this Forum)The Cert is 8192bit. Maybe you have to update your Jabber Client because old openssl libs would not work. (For Pidgin: Use the newest version on windows, if need be recompile with new openssl on linux)

« Last Edit: April 08, 2014, 04:01:24 pm by p »

Logged

axelerator

I think the crtificate still missing something more than signing by an official authority .. The chrome browser won't let me connect to the forum at all - (see attachments) - also the (pidgin based) OSX instant messenger Adium that I'm using on OXS to access my jabber account won't let me connect with an SSL Handshake error - normally I would simply trust you self signed certificate, but Chrome would not even let me display it..

I think the crtificate still missing something more than signing by an official authority .. The chrome browser won't let me connect to the forum at all - (see attachments) - also the (pidgin based) OSX instant messenger Adium that I'm using on OXS to access my jabber account won't let me connect with an SSL Handshake error - normally I would simply trust you self signed certificate, but Chrome would not even let me display it..

Firstthis certificate has nothing to do with heartbleed bug. Our Jabber cert just ends on april 8th 2014 so simply we needed a new one ...

To the problemThe forum uses a Cert from 31.10.2013. The CommonName is "board.phcn.*" This could be a problem for your Chrome if it uses an old ssl lib (older than 4 years). The Cert uses 8192bits this could be a problem tooOur Jabber server uses the same style for "*phcn.de" . We also got some errors with older Pidgin versions on windows because they used an old ssl lib from 2006-2008 (why?)

Please have a look at your browser whether you see our RootCA. See my screenshot