CA-signed certificates import problems (bug fixed)

Openfire Openfire Support
1

Version 3.6.3 of Openfire fixes this bug:

http://www.igniterealtime.org/issues/browse/JM-1503?page=com.atlassian.jira.plug in.system.issuetabpanels%3Aall-tabpanel

It also affects 3.5.2, version I use in production (under Red Hat 4).

Do you know of a workaround? With keytool?

Thanks for your answers.

2

No idea anyone?

Thanks

3

Hi,

What are you looking for? A patch to the old version?

daryl

4

A patch for 3.5.2 would be cool.

Or just a workaround, a way to have CA-signed certificates for TLS/SSL connections in my Openfire.

5

Hi,

Well, you’d have to apply a number of patches to a source tree and recompile. Are you in a position to be able to do that?

Is there some issue preventing your upgrade?

daryl

6

Time is preventing me from applying too many patches, compiling, making the RPM and testing before going to production: I have one day of work left (in two weeks), which is very short.

So I understand there is no other solution? Do we have to use the provided self-signed certificate?

That doesn’t seem to me a so big issue since the connections are still encrypted. The server in on an intranet, and not visible on the internet…

7

Hi,

I have no idea if this would work, but perhaps you could install 3.6.3 on a test machine, import your certs into it and then copy your security/ folder to the production machine and see if it takes it?

daryl