A few days ago Daniel Gultsch added the column XEP-0384: OMEMO Encryption to his compliance list. It suggested that only conversations.im supports OMEMO Encryption, which isn’t true. Yesterday an explanation was added to one of the source files of the ComplianceTester and also a question mark was added to the column mentioned above, which is a link to this explanation.
Daniel Gultsch strongly recommends that the servers PEP module should support publish-options. If enabled, Conversations starting with version 1.20, will be able to send OMEMO encrypted messages to clients, without the need to add them to your roster first. This is a great new feature and we like it, and would like to support it, but currently the PEP module from Prosody does not support publish-options (yet).
Long speak short: You can still use Conversations and other clients with OMEMO over our and other servers, but without the feature of writing encrypted messages to persons, who are not in your address book.
For more information please see here at 5222.de. I also reused some text of the blog post of Sebastian as it describes everything quite good. So thank you for that, Sebastian! ;-)
We just moved from StartSSL to Let’s Encrypt certificates for all public Jabber domains including the certificate for this website. You can find the new certificate fingerprints on the Server Specifications page.
We updated our old expired certificates a while ago. And now I just updated the website. You can find the new fingerprints here.
Also we had some problems with certificates, especially on this website. Sometimes the webserver delivered the old and expired certificate. This was because some old tasks of Apache were still in the memory. Problem solved three days ago.
A short time before the old certificates expire we setup some new ones:
hot-chilli.net and im.hot-chilli.net (and also for this website):
A few day ago we activated a new theme on our website. Also we switched from http to https. The benefits are that we do not get spam comments so much anymore with the features of the new WordPress theme. Also if you use our (now completly working) online account management tools (register, change password, remove, transport pre-registration) and online clients (JWChat and Jappix) you will not have to send any data unencrypted over the internet.
We love to read what you think about the changes. ;-)
We just upgraded ejabberd to 2.1.10. Therefore the service was down for some minutes. Everything should be up and running again.
One of the main reasons we were really looking forward for ejabberd 2.1.6 is the support of captcha for mod_register. This module handles in-band registration, which means the interface where users can register through their client. This interface is also abused by spammers. We hope that the use of captchas will prevent most spam registrations.
If you client does not support captcha you well see a url where you can see the captcha in your browser window.
Finally the Debian package for ejabberd 2.1.6 is available. Therefore we will perform an upgrade to ejabberd 2.1.6 in the next minutes. There will be a short service outage.