this post was submitted on 25 Jul 2024
316 points (99.4% liked)

Technology

58303 readers
17 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
316
Secure Boot is completely broken on 200+ models from 5 big device makers (arstechnica.com)
submitted 4 months ago by [email protected] to c/[email protected]
77 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] NekkoDroid 3 points 4 months ago* (last edited 4 months ago)

The kernel modules usually are signed with a different key. That key is created at build time and its private key is discarded after the build (and after the modules have been signed) and the kernel uses the public key to validate the modules IIRC. That is how Archlinux enables can somewhat support Secure Boot without the user needing to sign every kernel module or firmware file (it is also the reason why all the kernel packages aren't reproducible).