this post was submitted on 25 Jul 2024
315 points (99.1% liked)
Technology
59689 readers
3922 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's doing a lot of work here.
Yes, it's important in certain situations, but for consumer devices, it's just another thing that can go wrong when using alternative operating systems. Regular users don't have the physical risk these other systems do, and making it more difficult for users to install more secure operating systems goes against the bigger threat.
Linux is compatible with Secure Boot (source: I exclusively run Linux, and use Secure Boot on my systems), but some distros or manufacturers screw it up. For example, Google Pixel devices warn you about alternative ROMs on boot, and this makes GrapheneOS look like sketchy software, when it's really just AOSP with security patches on top (i.e. more secure than what ships with the device). The boot is still secure, it's just that the signature doesn't match what the phone is looking for.
It's just FUD on consumer devices, but it's totally valid in other contexts. If I was running a data center or enterprise, you bet I'd make sure everything was protected with secure boot. But if I run into any problems on personal devices, I'm turning it off. Context matters.