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

File encryption and master password support #1199

Open
Emdek opened this issue Oct 1, 2016 · 4 comments
Open

File encryption and master password support #1199

Emdek opened this issue Oct 1, 2016 · 4 comments

Comments

@Emdek
Copy link
Member

Emdek commented Oct 1, 2016

No description provided.

@landroni
Copy link

landroni commented Oct 4, 2016

I'm not sure how easy this is, but have you considered using SpiderOak's open-source crypton framework:
https://github.com/SpiderOak/crypton

For an example of what can be done with it see encryptr:
https://github.com/SpiderOak/Encryptr

My understanding is that crypton significantly reduces the security considerations when building an encrypted application... SpiderOak's philosophy is fully reliant on the concept of master password and rendering the data securely inaccessible without it.

@Emdek
Copy link
Member Author

Emdek commented Oct 4, 2016

@landroni, we already have encryption implementation based on libtomcrypt, but we need to polish it and integrate master password.

@Emdek Emdek modified the milestones: The Next Big Thing, Beta 12 Dec 30, 2016
@Emdek Emdek modified the milestones: The Next Big Thing, The Future Next Big Thing Sep 26, 2017
@Emdek Emdek modified the milestones: 1.0, The Next Big Thing Jan 1, 2019
@Emdek
Copy link
Member Author

Emdek commented May 10, 2022

Any thoughts on approach using transparent file system encryption?
That would allow to encrypt entire profile without implementing encryption for every file separately (and some stuff simply cannot be encrypted otherwise, like QtWebEngine profile).
https://en.wikipedia.org/wiki/EncFS

@Emdek
Copy link
Member Author

Emdek commented May 10, 2022

I guess that we still need to finally adopt the work done by @Chocimier, perhaps adjusted to this file format:
https://www.aescrypt.com/aes_file_format.html

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

No branches or pull requests

3 participants