| ▲ | kubik369 8 hours ago | ||||||||||||||||
Agreed, I have personally come to the same conclusion. I do not encrypt the drives in my home desktops and servers so that the recovery/migration is easier when the time comes. The risk of someone stealing my desktops from my home is very low and the impact of someone going through my family photos or Linux ISOs is nothing. I roll my eyes at my friend when he explains the solutions for how to input the encryption password when his server restarts. At the time of writing, there are already other replies to this comment how "it's mandatory today to encrypt drives" without any qualifiers. I am growing more and more frustrated by people who try to force security measures like this "because it is more secure that way" without first taking a look at the risks, impacts and associated costs. I think they simply force these security measures on others to feel good about their choices. It was a breath of fresh reasonability when I found out that apt intentionally uses only HTTP instead of blanket HTTPS everywhere because the packages are signed, therefore they can be verified by the client, and using HTTP allows easier caching with cache proxies and such. | |||||||||||||||||
| ▲ | hellojesus 7 hours ago | parent | next [-] | ||||||||||||||||
> I roll my eyes at my friend when he explains the solutions for how to input the encryption password when his server restarts. Isn't this rather trivial? You gen a keyfile, register it with luksAddKey, then update /etc/crypttab, no? The real concern is making sure that keyfile is stored securely, but you can simply symmetrically encrypt it and upload it to your favorite cloud storage provider. | |||||||||||||||||
| |||||||||||||||||
| ▲ | microgpt 8 hours ago | parent | prev [-] | ||||||||||||||||
I used to think that and then the authorities raided my house (for bullshit reasons that had nothing to do with me). Now I encrypt everything. | |||||||||||||||||
| |||||||||||||||||