News for hackers. Stuff that matters.
Re:Google's Requirement for Developers to Be Verified Threat... by numpad0 on Tuesday October 07, 2025 @04:05PM (#45508140)
Google can force OEMs implement non-unlockable secure boot.
Re:Google's Requirement for Developers to Be Verified Threat... by j4hdufd8 on Tuesday October 07, 2025 @05:34PM (#45509174)
What is non-unlockable secure boot?
Re:Google's Requirement for Developers to Be Verified Threat... by numpad0 on Tuesday October 07, 2025 @05:36PM (#45509211)
State of the art SoC with silicon baked private keys laser fused for production configuration
Re:Google's Requirement for Developers to Be Verified Threat... by j4hdufd8 on Wednesday October 08, 2025 @04:36AM (#45513615)
"Silicon baked private keys" are really vague buzzwords. That's pretty much standard and it can be implemented in a variety of ways.

Not sure why you're calling this non-unlockable. Everything is unlockable with enough money.

Re:Google's Requirement for Developers to Be Verified Threat... by numpad0 on Wednesday October 08, 2025 @06:36AM (#45514504)
You're not going to be decapping and recapping SoCs at scale... Lots of eFuse implementations are just writable ROMs with erasing lines disabled, and people aren't taking out particle accelerators to wipe them.
Re:Google's Requirement for Developers to Be Verified Threat... by bri3d on Wednesday October 08, 2025 @10:35AM (#45516658)
Whatever silly OTP implementation is involved is 99.9% irrelevant to unlocking a phone, and OTP for root-of-trust has been in use in phones for 15+ years anyway.

Maybe we use some hardware-level trick to get to some protected firmware initially to reverse engineer it, but almost universally it's what reads the state of the fuses (or something after it) that actually gets exploited. That's changing, too, but in general very slowly and at at the pace of hardware manufacturers learning how to make software (aka, glacial with a few notable exceptions).

Re:Google's Requirement for Developers to Be Verified Threat... by lucb1e on Tuesday October 07, 2025 @05:42PM (#45509288)
And (present tense) forces OEMs to not ship with utilities that let users access their own data

Fairphone wanted to give users full access on the Fairphone 2, but were contractually disallowed if they wanted to also ship the Android Market, Google Maps, etc., which users can't otherwise install themselves so it was essential to pre-install for a normal user experience. That's why they made two OSes for that phone: a googleful one and a free OS based on AOSP that you can install if you don't want Google (https://code.fairphone.com/projects/fairphone-2/fairphone-op...). Nowadays they let the /e/ Foundation do that work with e/OS. They're supportive of it but apparently don't have the internal manpower to continue making and supporting an extra distribution