| 1 |
On 17-05-21 at 08:41, Ian Zimmerman wrote: |
| 2 |
> On 2017-05-21 09:51, Neil Bothwick wrote: |
| 3 |
> > Why are you using encfs with the associated FUSE baggage when ecryptfs |
| 4 |
> > is in the kernel and performs the same function? |
| 5 |
> Is ecryptfs behind the scenes when I run /sbin/cryptsetup ? |
| 6 |
No, ecryptfs is a stacked filesystem (filesystem layered on a filesystem) |
| 7 |
that handles encryption on a file-by-file basis |
| 8 |
|
| 9 |
> Cryptsetup is utility used to conveniently setup disk encryption based on DMCrypt kernel module. |
| 10 |
> These include plain dm-crypt volumes, LUKS volumes, loop-AES and TrueCrypt (including VeraCrypt extension) format. |
| 11 |
> Project also includes veritysetup utility used to conveniently setup DMVerity block integrity checking kernel module. |
| 12 |
> [1] |
| 13 |
cryptsetup does encryption on the device layer on a block-by-block basis |
| 14 |
|
| 15 |
You put ecryptfs on a filesystem, you put a filesystem on a dmcrypt |
| 16 |
device. |
| 17 |
|
| 18 |
[1]: https://gitlab.com/cryptsetup/cryptsetup/blob/master/README.md |
| 19 |
|
| 20 |
-- |
| 21 |
Simon Thelen |
Archives