Francois Botha wrote:
Hi,
I did a quick and dirty install of jabberd2. Everything works
beautifully, except that the users get a prompt that the certificate is
invalid every time they (re)connect. They are all using Pidgin 2.10.
"Invalid" as in "SSL protocol error", or "invalid" as in "The
certificate could not be validated"?
How can I generate a valid self-signed certificate so that these
problems go away?
If the first, your cert is functionally gibberish and jabberd should
have complained in the log IIRC. SSL will not work, and generating a
new cert according to any handy HOWTO should clear that up.
If the second, you can try adding your cert to everyone's system
certificate store, or buy a commercial cert. The client is essentially
complaining about the self-signed-ness of the certificate, so adding it
to the system certificate store will "validate" it according to the SSL
trust chain as seen from the Jabber client.
I've never found a way to tell any Jabber client to accept a self-signed
cert directly without questions; all the ones I've tested ask if you
really want to accept the self-signed cert every time they start up.
-kgd
