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: dsr at randomstring.org (Dan Ritter)
- Date: Fri, 27 Sep 2019 12:16:01 -0400
- In-reply-to: <23950.10922.716692.740606@blazemonger.com>
- References: <mailman.1.1569513602.7173.discuss@blu.org> <23950.6002.375891.124402@blazemonger.com> <20190927143943.uzq4rxx7elctx5jg@randomstring.org> <23950.10922.716692.740606@blazemonger.com>
Daniel Barrett wrote: > 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. I've never used it for more than dozens of gigabytes, sorry. -dsr-
- 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?
- From: dbarrett at blazemonger.com (Daniel Barrett)
- [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):