BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Encrypt /home and allow unattended boot?
- Subject: [Discuss] Encrypt /home and allow unattended boot?
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Fri, 27 Sep 2019 11:25:40 -0400
- In-reply-to: <20190927143943.uzq4rxx7elctx5jg@randomstring.org>
- References: <mailman.1.1569513602.7173.discuss@blu.org> <23950.6002.375891.124402@blazemonger.com> <20190927143943.uzq4rxx7elctx5jg@randomstring.org>
On Fri, 27 Sep 2019 10:39:43 -0400 Dan Ritter <dsr at randomstring.org> wrote: > You can also use encfs, which is an overlay filesystem. It > provides less metadata security -- any user can see the number > of files, what perms they have, a lower bound on their size, and > atime/mtime stats. On the other hand, it's a lot easier to > experiment with. Also: it's a FUSE module so you don't need root. It's also single threaded and slower than the other options but that's the trade-off. It also has a nifty reverse mode. encfs normally presents plain data layered over encrypted files. Reverse mode presents encrypted data layered over plain files. The example case is encrypted remote backups where you don't want to encrypt the local files. -- Rich Pieri
- References:
- [Discuss] Encrypt /home and allow unattended boot?
- From: dbarrett at blazemonger.com (Daniel Barrett)
- [Discuss] Encrypt /home and allow unattended boot?
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] Encrypt /home and allow unattended boot?
- Prev by Date: [Discuss] Encrypt /home and allow unattended boot?
- Next by Date: [Discuss] Encrypt /home and allow unattended boot?
- Previous by thread: [Discuss] Encrypt /home and allow unattended boot?
- Next by thread: [Discuss] Encrypt /home and allow unattended boot?
- Index(es):