-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add encryption to the direct message feature #3
Comments
It would be awesome to use the TextSecurev2 Identity keys (aka baseKey) to prove your identity regardless of device. |
yeah, linking into another known key might be a good idea, be it chatsecure, textsecure or pgp. also looking into using Minilock for this. FYI, currently direct messages are encrypted at the bluetooth RFComm level if you have paired with the device ahead of time. |
Keep in mind Bluetooth LE/Smart encryption has been cracked: https://github.com/mikeryan/crackle/ |
Yes, we will use libsodium, minilock, axiotl/textsecurev2 or some other message layer encryption. |
yes, OTR would be awesome. Perhaps a bridge with Zeroconf will be possible to Xmpp Texting possibly through the MAXS Project. |
use OTR4J or TextSecurev2 code/protocol
The text was updated successfully, but these errors were encountered: