Encrypt config file on disk with NaCl #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the config holds sensitive values like the OTR private key and stored fingerprints, the user might wish to encrypt it. The option is offered on enroll, and then autodetected on each run.
The scheme is basic:
Scrypt SALT + SecretBox NONCE + BOXAlso, if the config file is encrypted, the user is prompted to save the account password on enroll.
Finally added a list of pinned server certificate fingerprints, since onions are already pinned and jabber.ccc.de would not work otherwise on most systems (those not trusting CA Cert) being impossible to edit the config.
The pain point is how to allow the advanced user to edit the config. My two ideas, neither good, are a
/set-opt <option> <value>command, or a/config-editcommand working like/roster-edit.