
/i.s3.glbimg.com/v1/AUTH_08fbf48bc0524877943fe86e43087e7a/internal_photos/bs/2017/6/6/nQGEVET1CtmfWBw5BjiA/ative-o-pendrive-e-digite-a-senha-pelo-veracrypt.png)
To the “OP” - this is a great topic, I’m learning stuff here too - going to check out that product suggested : Cryptomator… Imagine your USB drive with some compromising details falls out of your pocket at a trainstation and some unscrupulous person finds it? 0700 is hardly going to stop them… VeraCrypt delivers, then I would prefer recommending Cryptomator.Īll I really want is that the documents are encrypted and easily decryptedĠ700 attribute doesn’t really cover this requirement… you could make a subfolder in there with 0700 and then have all the files in there 0600 - but - they’re still not encrypted and root (or UID of the “owner”) can run a simple find, and find them : If someone just wants to simply encrypt a folder, without all the bells and whistles e.g. But I definitely hat to put more work and thought into getting this volume running than the Cryptomator folders I have. Coincidentally, I use a 300GB VeraCrypt volume with fixed length. I use both Cryptomator and VeraCrypt regularly. Cryptomator is pretty minimalistic, straight-forward, easy to use and easy to understand. VeraCrypt bumps it up to Level 9, by bringing additional expert features and possible complications in, that someone who just wants an “encrypted folder” usually wouldn’t care much about. That said, I would generally recommend Cryptomator over VeraCrypt in such situations, as the original goal of this thread was to find a way to “encrypt a folder”, which Cryptomator is way closer to. Yes, but not sure how much ZFS applies to stuff like VeraCrypt.

it uses idle time to do its stuff - so it doesn’t slow you down)… with AES encryption on ZFS - it’s only “busy” when you’re not (i.e.

If I was “in your shoes” - I’ve be investigating the purchase of at least 1 TB of storage - and - before copying ANYTHING to it - encrypt it using some “open source” product (like VeraCrypt - you can get binaries for Wintel, Mac, Linux, ARM et cetera) - then maybe make the VeraCrypt “crypt” fat32, NTFS or exFAT, so you can read it on other “non-Linux” computers more 's confirmed this - e.g. Veracrypt or Truecrypt would probably work on “whole device too”, but I haven’t used it on this scale - so I can’t really comment.
VERACRYPT DROPBOX SOFTWARE
(note - you won’t be able to read LUKS or ZFS encrypted on other non-Linux computers - it may be possible on Mac, but probably not Windows - I have “paid” software on my Mac M1 that can read and write EXT including LUKS - but not ZFS).
VERACRYPT DROPBOX ARCHIVE
I’d suggest - Ver圜rypt for “smallish” stuff, on the fly, with ARCHIVE “files” (not devices) For 450 GB - I’d strongly suggest “the whole device” - and - preferably empty at the time of creation (I’d imagine it would take days to scramble 450 GB “on the 's confirmed this - e.g.
