-
Notifications
You must be signed in to change notification settings - Fork 399
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
Password protect configuration files #33
Comments
This is an interesting one. Ideally, the entire It seems unlikely that upstream It is worth noting that the default mode on all platforms is to store data portably, next to the binary, so you can place it on an encrypted disk manually.
Keep an eye on #15. I have some UI and early designs sketched out, currently.
See the discussion of both on #28. I'll repurpose this to cover the password protection issue, which doesn't have an existing bug. Thanks for the comments. |
There is discussion on #30 about storing hidden service keys. Tor has a bunch of related tickets under https://trac.torproject.org/projects/tor/ticket/8993. I promised to sketch out a control API that would be suitable at some point. That would still not allow for encrypting everything, though. All of the other data tor reads directly is still a problem, including the state file and torrc. |
Tor 0.2.7.x has an ADD_ONION control API, which is sufficient for us to encrypt Ricochet's configuration and the hidden service data. Tor's configuration and state files will remain unencrypted - which is a shame, but is at least much less sensitive. |
Requires #227 |
…base32_tests Base32 tests + make base32 code RFC4648 compliant
Torsion needs a couple of new functions.
First, it would be nice to have password protection similar to Bitcoin password protection.
Second, an option to send files would be nice.
Third, an OTR plug-in wouldn't hurt for additional security.
Lastly, additional encryption would never hurt.
The text was updated successfully, but these errors were encountered: