Comments on 2018-06-07 No More WhatsApp

Regarding TLS...

@algernon said: Interesting. I had no trouble with TLS. Grabbed a cert from LetsEncrypt, prosodyctl --root cert import /etc/letsencrypt/live, and done. The last step is important, ’cos Prosody by default does not have access to the LE certs.

See https://prosody.im/doc/letsencrypt

@ckeen said: If you have enabled http_upload and http you can try that port with a web browser to check whether the certificate is correct. The default port is: 5281 for TLS


Regarding encryption:

@algernon said: I used the Prosody 0.11 packages via stretch-backports, the default config worked out of the box. The “roster” and “pep” modules need to be enabled for OMEMO. For encryption to work, you will have to first log in with a client that supports encryption (Dino, Empathy, Conversations, Converse.js were the ones I found working, Movim did not support OMEMO).

@ckeen said: The conversations client site has a list of peps you should enable for the best experience.

https://conversations.im/#xmpp and compare with https://prosody.im/doc/xeplist


@algernon also posted their config. Very cool.

Thank you both! 🙂

– Alex Schroeder 2019-03-13 08:42 UTC


Please make sure you contribute only your own work, or work licensed under the GNU Free Documentation License. Note: in order to facilitate peer review and fight vandalism, we will store your IP number for a number of days. See Privacy Policy for more information. See Info for text formatting rules. You can edit this page if you need to fix typos. You can subscribe to updates by email without leaving a comment.

To save this page you must answer this question:

Please say HELLO.