I just rolled out new startssl-signed class 2 certificates for several Domains, including the jabber Server and all jabber frontends. As they are all signed you should actually not notice any errors or warnings.
The current fingerprint for the jabber certificate is
I moved to the new policy of…
– signing all public services with officially signed certificates,
– signing all private services with my own certificate-authority.
One would think that having a “self”-signed certificate for jabber would actually not mattter, but the amount of TLS connected clients has doubled since the rollout of the new signed certs. Sigh.