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: dbarrett at blazemonger.com (Daniel Barrett)
- Date: Fri, 27 Sep 2019 11:28:42 -0400
- References: <mailman.1.1569513602.7173.discuss@blu.org> <23950.6002.375891.124402@blazemonger.com> <20190927143943.uzq4rxx7elctx5jg@randomstring.org>
On September 27, 2019, Dan Ritter wrote: >cryptmount is what you are looking for. Wow, cryptmount is so easy to set up! Thank you so much, this is fantastic. I guess to make sure it's mounted when I log in, just put something like this in ~/.bashrc: mountpoint -q /home/me/crypto || cryptmount opaque Do you know anything about the performance of large cryptmount filesystems? Looks like a filesystem is stored in a single user disk file (~/crypto.fs), so it makes me wonder if it can handle (say) several terabytes without degrading. I did a quick google search for "cryptmount performance" but didn't see anything useful. -- Dan Barrett dbarrett at blazemonger.com
- Follow-Ups:
- [Discuss] Encrypt /home and allow unattended boot?
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Encrypt /home and allow unattended boot?
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] Encrypt /home and allow unattended boot?
- 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):