Don't want to have to decrypt swap every boot, would be nice if that was automatic, but at the same time I'm not 100% sure doing lvm inside luks and then putting both swap and os inside lvm is a good idea. Idk.
-
-
This Tweet is unavailable.
-
Replying to @AbeSnowman
Oh? How exactly does that work? Decrypt one and it does the rest for you?
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @AbeSnowman
I mean, it's encrypted as a single continuous chunk, so there's not really a benefit to 3 keys for 3 partitions instead of one, no? Idk, this is why I ask, my threat models may be totally bogus.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @AbeSnowman
Yeah I think I'm going to do this. Encrypt the main block, and then lvm after encryption.
1 reply 0 retweets 2 likes -
Replying to @hedgeberg @AbeSnowman
If all the volumes are on the same platter then CPU usage won't go up. You're I/O limted anyway. You can always encrypt multiple volumes then store the volume keys in the root filesystem and have them automatically decrypt on boot. In the end it depends on what exactly you want.
1 reply 0 retweets 5 likes -
At one point I had a laptop with a... rather complex RAID/crypto/LVM setup. Still only typed one passphrase on boot (for a LUKS loopfile!). There were good reasons for this mess back then, but now I just have an LVM on LUKS SSD and an LVM on raw dm-crypt HDD w/keyfile on SSD.pic.twitter.com/3oa11BqO8B
3 replies 6 retweets 34 likes -
did you run qubes inside of all that :v
1 reply 0 retweets 1 like
No, just Gentoo.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.