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 ability to set path for .securefs.json #9

Closed
Sonnix1 opened this issue May 14, 2016 · 4 comments
Closed

Add ability to set path for .securefs.json #9

Sonnix1 opened this issue May 14, 2016 · 4 comments

Comments

@Sonnix1
Copy link

Sonnix1 commented May 14, 2016

Currently settings and encryption key is stored in .securefs.json which is located in the folder with all the encrypted data.
Would it be possible to add an option to specify the path for the settings file so that it could be stored on some external media separate from encrypted data or in separate folder that is not synced with the cloud?
In this setup the mount command for example could look like:
securefs mount --config /mnt/external/.securefs.json ~/Secret ~/Mount

@netheril96
Copy link
Owner

What is the use case for this?

@netheril96
Copy link
Owner

Mm, I get it. If you do not store .securefs.json in the cloud along with your data, you deny the attacker any chance to guess or brute force your password. They will have to brute force the 256-bit random key instead. I will implement it soon.

@netheril96
Copy link
Owner

Added in 73474dc.

@netheril96
Copy link
Owner

A critical security vulnerability has been found in securefs version 0.4.0 to 0.6.0. If you have used these version to encrypt your data, please either migrate to the newest version or some other encryption software.

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

2 participants