-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTR Support #305
Comments
It is missing in 1.0 :/ |
Hi, is this one still in the TODO list ? |
Nope it's not anymore |
Hello, why is it not in the TODO list anymore ? I think it was a great improvement for jappix. Is there an alternative technology you want to use to achieve P2P cryptography ? |
I agree with dolanor; OTR would be very useful indeed. There's a project called Converse.JS which provides an already functional example of OTR in browser, implemented in JavaScript. |
I'm missing OTR, too. Please add that feature to the web chat. |
Will jappix employ mpOTR for MUC? Xmpp Texting without end2end encryption is of little value. |
I agree with Off-the-record (OTR) encrypted messaging in jappix, at least in private single-user conversations, implementation wich exist for binary clients, and is well known. |
Planned ASAP 🍺 |
Considering implementing OMEMO rather, as it is more XMPP-ish + enables multi-device message synchronization. |
I use Signal a lot, and I think Axolotl is a great idea. Totally for using this on top of xmpp. And the multi device is a real issue. Great that it tackles with it. |
There is no omemo javascript implementation at this time, omemo aim to securely identify devices to obtain multi end point delivery. The "issue" here is end to end encryption, which has some limitation in offline delivery. Axolotl aims to solve offline delivery but not in the js implementation at the moment, through history syncronization (in regular clients not in a browser window). So, here I hoped to get at least some kind of "old" e2e encryption that didn't come. Now what are you promising? offline encrypted messages? or multi end points? that doesn't exist neither in binary clients (ok offline can be achieved through PGP as usual but not through OTR implementation loosing perfect forward secrecy and deniability), history sync is server dependant and many servers don't store offline messages for security purpose. I really hope you stick with e2e encryption and eventually the possibility to decrypt offline messages sent with jappix and recieved in a regular client. (do you really want to solve an offline e2e encrypted message recieved by a js client offering perfect forward secrecy and deniabilty? in javascript?) but for now no encryption. sorry. |
Yes, I would greatly appreciate this over mpOTR and OTR. |
After almost 2 years... any news on OMEMO? |
@aslmx Jappix isn't maintained anymore ;) |
ah. Good to know. Thanks for the info... |
Use: https://github.com/arlolra/otr
The text was updated successfully, but these errors were encountered: