Few years ago I watched this engineer who used an rp3 to hack a bit locker encryption key.
Technology
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- 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.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
Unpopular opinion but I’m dying on this hill. Secure boot creates more problems than it solves.
That's a very popular opinion.
That's like saying windows 11 doesn't need tpm chips, an extremely popular opinion
I'd argue this is actually a popular opinion. IMO secureboot has just become a way for Microsoft to leverage it's position and keep a strangle hold on industries they have no business being in.
The whole kernel level anti-cheat on win11 bullshit in the gaming industry is a good example. Essentially locking games to its platform and willing to sacrifice security to do so at our expense.
This is especially true on computers where it is impossible to change the signing keys. Smartphones, game consoles, many laptops, some desktops, smart TVs, IoT devices, modern cars, etc.
Only in tech circles, it says secure and that's enough for most people.
Outside of tech circles most people think secure boot looks something like this

Fantastic 😂 ! Thanks for the laugh.
Was it ever popular?
Popular is the wrong question, the correct question is, how many machines is this default on.
And, how many people switch to something other than the default? Most W11 users are just going to go with whatever the computer says it's doing without changing anything. They're either ignorant of the options available, or scared of breaking something if they make a change.
That's the scary part about security assumptions.
Arch Wiki had pointed out for years that Secure Boot is a flawed mechanism.
It's not flawed at all. But its purpose isn't actually to secure anything. Its purpose is to complicate the installation of alternative OS and to perpetuate vendor lock in, while sounding like it's "for your security". In that regard, it has succeeded.
There is also TPM and Microsoft Pluton, which serve the same purpose.
A very large portion of Microsoft's efforts are dedicated to this. If they redirected just a bit of their work force to fixing their products, maybe people would actually want to use them, instead of being forced to.
11 old and forgotten UEFI shim bootloaders at versions 0.9 and below that can be used to bypass UEFI Secure Boot on any UEFI-based machine that trusts Microsoft’s Microsoft Corporation UEFI CA 2011 third-party UEFI certificate authority (CA) certificate, regardless of the installed operating system (OS).
This "Trust" is one of my pet peeves. It's $$$.
I get why you'd dislike that wording, but this is also how all certificate stores work, regardless of whether we're talking Secure Boot, Windows or Linux. Gotta trust the top level as providing legitimate certificates to then trust everything underlying as coming from the correct parties.
Certificate are something I work with constantly at work and I fucking hate resolving issues with them lol.
I get why you’d dislike that wording
It's not just the wording.
this is also how all certificate stores work
Precisely.
Check out cacert.org and why it never gained "Trust". Hint: $$$
Add this to the pile of reasons why M$ is a joke and people should stop using them. Nothing they make is so good that you need to stick around.
MS has mastered the one thing businesses love which is being perfectly mediocre. If you present a business two pieces of software one that does one thing really well but nothing else, and one that does three things terribly, they'll pick the one that does three things terribly every time. That's the MS design, it smears a thin coating of suck across as broad a surface as possible and then advertises that it does everything.
A PKI without a CRL will eventually become exploitable.
Secure boot does have a revocation mechanism (It's literally how this issue has been mitigated) though.
You can not only load in allowed signatures, you can also load in disallowed ones so even properly signed binaries will get rejected.

My word of advice; any security implementation by an actor who has a fiscal responsibility and/or incentive is inherently flawed.
You are handing your keys to a whore.
All it takes for it to be 'broken' is to be from Microslop.