OTR-problems while testing Rocket.chat


#1

I am testing OTR on my own rocket.chat-server and I have some problems:

  1. Often I can click on OTR in the actions-menu but then the “Start OTR session”-button is missing. This happens especially after an OTR-session was closed, and a new one shall be opened
  2. It happens that one side starts an OTR-session but the pop-up for accepting it doesn’t show up on the other side.
  3. When I have an OTR-session open and then send a message from the mobile client, the message won’t appear in the chat-window but only in the extended view beneath the user name. I would expect to see an unencrypted messge in the browser window

Am I doing something wrong or are those legit bugs?


#2

And when you have an OTR-session open, leave your desk, write a message from the smartphone the other side will have it only in the extended view beneath the icon but no further notification. Thus you cannot let it run on the desktop with OTR because the other side won’t get your messages.


#3

OTR is kinda broken in RC these days… at least there are several unfixed issues and the current implementation is not very convenient. But fret not. I see that there are current developments in the following PR:

Cheers
Thomas


#4

… though I’m not sure whether this will implement the OTR property of the conversation.

Cheers
Thomas


#5

Thanks. I doubt that this will be OTR but another way of E2E (offline-support doesn’t sound like OTR at all). I mainly need E2E, so that we have a way to send confidential information to each other which needs to be E2E-encrypted.


#6

Ah, I see. The Signal-protocol seems to be used here (there is a commit called: " adding libsignal to eslint ignore, fixing other eslint errors")