• 0 Posts
  • 8 Comments
Joined 10 months ago
cake
Cake day: July 3rd, 2025

help-circle



  • This is dangerous

    Hence my point about why bother at all. Without full encryption one gets leaks. With full encryption some kind of secret is required. Either password (hence that need of keyboard in earlier comment) or a key, etc

    In order to not need a secret during boot, critical parts have to be exposed

    Theoretically one could also put logs and cache on encrypted volumes. Maybe that could be some solution. I have in the past had /var/logs on separate partition, so it didn’t make /run out of space. Linux had no issue with that. But that still leaves kernel and OS exposed

    fully encrypted drive and this chain’s existence makes it easier to know that no one has tampered with my system

    The comment I responded to mentioned:

    needing to enter a password before the OS boots is a decision that makes Linux kind of awkward to use disk encryption with

    I don’t think you are talking about the same setup and vectors. Their point was to not have fully encrypted drive, so it boots without a prompt


  • OS encryption isn’t that important (verification is)

    I don’t think I’ve heard about some boot-time checksum verification of root partition. Doesn’t mean it does not exist, just that I can’t help here

    protecting user data

    My point is: if OS is not encrypted, it can be modified. And that verification idea, if is not stored under some encryption, could also be changed. Which means that by the time you put in your password to decrypt your home, you might be already running system that will nullify the protection. Encrypting only your data will only protect you in scenarios when someone snatches your device turned off