this post was submitted on 08 Apr 2026
230 points (99.6% liked)

Technology

83600 readers
3570 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 news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
230
Developer of VeraCrypt encryption software says Windows users may face boot-up issues after Microsoft locked his account (techcrunch.com)
submitted 15 hours ago by throws_lemy@reddthat.com to c/technology@lemmy.world
18 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] krigo666@lemmy.world 12 points 15 hours ago (2 children)

And this why Secure Boot can't be trusted. It is Micro$lop that signs and issues the keys.

[–] FauxLiving@lemmy.world 20 points 14 hours ago (1 children)

Secure Boot has nothing to do with Microsoft, it's a UEFI feature.

You can enroll your own Platform Key and have complete control over the entire Secure Boot system.

https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot

I use a signed Unified Kernel Image to use Secure Boot and my machine has zero Microsoft software on it. (Arch, btw)

[–] Grass@sh.itjust.works 3 points 9 hours ago (2 children)

wasn't there some dumb shit like every linux distro using fedora keys which were from microsoft?

[–] huggingstars@programming.dev 1 points 1 hour ago* (last edited 1 hour ago)

Microsoft signs Red Hat certs then Red Hat signs everyone's certs, so the only thing Microsoft can do is to revoke Linux as a whole.

It's the solution that requires minimal user effort since most computers are designed for Windows.

[–] sorter_plainview@lemmy.today 1 points 5 hours ago

I think it is just chain of trust. Many used Microslop as the trust authority (may be due to convenience? I have no idea). Debian has a nice page on Secure boot and how it works.

[–] 9tr6gyp3@lemmy.world 15 points 14 hours ago* (last edited 14 hours ago)

You can use custom keys with secure boot. Any PC newer than 2015 should give you that option.

You don't have to use Microsoft's keys.

This isn't a secure boot issue. This is a bootloader issue.