←back to thread

253 points pabs3 | 1 comments | | HN request time: 0.207s | source
Show context
RecycledEle ◴[] No.44615326[source]
This is yet another why I do not encrypt.
replies(2): >>44615500 #>>44615502 #
craftkiller ◴[] No.44615500[source]
Secure boot has nothing to do with encryption. It is verifying crytographic signatures. The bootloader is signed, not encrypted.
replies(1): >>44616142 #
vbezhenar ◴[] No.44616142[source]
There's some link between secure boot and encryption.

If you don't do secure boot, you need to secure your boot chain in other ways, to prevent attacker from modifying your software to log entered passphrase.

Secure boot allows to build a verifiable chain of software (UEFI -> Bootloader -> Kernel -> Initrd) which will protect against any modification, so you can be sure that your key presses are not being logged by the malicious software. That said, commonly used Linux distros have some problems protecting initrd, but that's issue of those distros.

Another link is TPM. I set up my system in a way to keep encryption key in TPM and release it only when secure boot is enabled. This allows to decrypt root automatically, without entering passphrase and my configuration only allows to boot UKI kernel signed with my key. It trades security with convenience, of course (because now attacker, who stolen my computer, only has to break through gdm or perform other ways of attacks like extracting RAM sticks), but for me it's acceptable.

replies(3): >>44616306 #>>44616371 #>>44617443 #
ahoka ◴[] No.44616306[source]
I think it’s primarily to avoid someone just putting your SSD into any other computer and access all files. Anything more is probably not a realistic threat to most people.
replies(1): >>44616922 #
1. sgjohnson ◴[] No.44616922[source]
Secure Boot does nothing whatsoever to prevent that. Disk Encryption has got nothing to do with Secure Boot.