Skip to content
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

Open
n8fr8 opened this issue Oct 1, 2014 · 5 comments
Open

Add encryption to the direct message feature #3

n8fr8 opened this issue Oct 1, 2014 · 5 comments

Comments

@n8fr8
Copy link
Owner

n8fr8 commented Oct 1, 2014

use OTR4J or TextSecurev2 code/protocol

@Asherehsa
Copy link

It would be awesome to use the TextSecurev2 Identity keys (aka baseKey) to prove your identity regardless of device.

@n8fr8
Copy link
Owner Author

n8fr8 commented Oct 10, 2014

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.

@Asherehsa
Copy link

Keep in mind Bluetooth LE/Smart encryption has been cracked: https://github.com/mikeryan/crackle/

@n8fr8
Copy link
Owner Author

n8fr8 commented Oct 10, 2014

Yes, we will use libsodium, minilock, axiotl/textsecurev2 or some other message layer encryption.

@TameOfGroans
Copy link

yes, OTR would be awesome.

Perhaps a bridge with Zeroconf will be possible to Xmpp Texting possibly through the MAXS Project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants