I’m vaguely interested in having a few different encrypted folders on my computer, with different passwords on each. I don’t have any particular strong requirements. It’s more of a velleity; mostly just to try it so that I know more about it.
That said, when I search for encryption options, I see a lot of different advice from different times. I’m seeings stuff about EncFS, eCryptFS, CryFS; and others… and I find it a bit confusing because to me all those names look basically the same; and it’s not easy for me to tell whether or not the info I’m reading is out of date.
So figure I’d just ask here for recommendations. The way I imagine it, I want some encrypted data on my computer with as little indication of what it is as possible; and but with a command and a password I can then access it like a normal drive or folder; copying stuff in or out, or editing things. And when I’m done, I unmount it (or whatever) and now its inaccessible and opaque again.
I’m under the impression that there are a bunch of different tools that will do what I’ve got in mind. But I’m interested in recommendations (since most of the recommendations I’ve seen on the internet seem to be from years ago, and for maybe slightly different use-cases).
The CryFS developers have a comparison page here that might help you decide what to use. There’s a summary table at the bottom that gives a comparison of features between encryption filesystems if you don’t feel like reading through it all.
I personally use and would recommend CryFS because it’s the only one (that I’m aware of) that plays nice with data synchronization software (i.e. doesn’t store the container as a single file) while keeping the directory structure encrypted.
I don’t see Cryptomator in the comparison. Doesn’t it have a similar feature set?
Was not aware of this, thanks! Looks like it does, with a notable difference being that Cryptomator has better cross-platform support in exchange for not having file size obfuscation.
Yeah, Cryptomator does sound like a good option. But I personally found the comment from the developer at the bottom to be a bit off-putting. I don’t like when people needlessly trash-talk other options.
He seems to belittle the importance of a key advantage of CryFS, and then goes on to accuse them of being ‘snakeoil statements’ because CryFS said their security was ‘proven’ in a masters thesis. I’m sure that ‘proven’ is not a great choice of word here, but I don’t think CryFS was trying to trick anyone. They’re just saying that the tool has been thoroughly analysed in a masters thesis and found to be secure.
One of the ‘advantages’ being touted for Cryptomator is that it is more ‘stable’ than CryFS. But the claim of stability coimes from CryFS saying their software is in beta while Cryptomator says theirs is complete. The way I see it, that’s not really a measure of stability; it’s a measure of caution from the developers. Stability and reliability are not things you can just claim, or base on whether or not something is called ‘beta’. It’s about testing, and analysing. So, in that context of CryFS expressing caution, to say their masters thesis statement is a ‘snake oil statement’, I think is disingenuous.
(Note: I’ve given an in-depth explanation of something that really isn’t a big deal. What the developer said is not that bad. I just wanted to articulate why I found it off putting.)
Seems like a pretty minor complaint all in all. It’s a free open source project that solves a real world issue well.
Is not like he even bashed the project that much, just pointed out a few of his own pet peeves.
IMO it has a better feature set because it has a native android app with remote storage support built in, and native desktop apps with a GUI.
I guess it’s mostly because it way written by CryFS people - but that does make CryFS sound pretty good; with the main downside being that it is less mature than some other tools. And it gives useful info on the others regardless.