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: Sat, 28 Sep 2019 22:07:30 -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>
On Fri, 27 Sep 2019 11:28:42 -0400 Daniel Barrett <dbarrett at blazemonger.com> wrote: > 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. cryptmount is a wrapper around device mapper and dmcrypt so it doesn't have any performance of its own. Whether or not cryptmount+dmcrypt is going to have problems depends on your storage. If it's raw partitions or logical volumes then it will be exactly the same as cryptsetup +dmcrypt because it's the same dmcrypt. If you're using file-backed block devices then it's anyone's guess. Too many variables. -- 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?
- 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: [no subject]
- Previous by thread: [Discuss] Encrypt /home and allow unattended boot?
- Next by thread: [Discuss] Encrypt /home and allow unattended boot?
- Index(es):