search

djtms / prosody-modules

Automatically exported from code.google.com/p/prosody-modules
0 stars 0 forks source link

[mod_http] [mod_bosh] Module reload doesn't use new TLS certificate #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Change TLS Certificate (because of heartbleed)
2. Reload Config
3. Reload Modules

What is the expected output? What do you see instead?
It would be expected, that all modules use the new certificate.
The core modules like c2s and s2s work fine, but http and bosh still deliver 
the old certificate.
(I'm not sure if bosh is part of the problem or just depending on http)

To make them use the new one, I had to globally unload and load the affected 
modules.

What version of the product are you using? On what operating system?
prosody 0.9.4 on debian wheezy

Original issue reported on code.google.com by ditt...@informatik.hu-berlin.de on 22 Apr 2014 at 10:30