News for hackers. Stuff that matters.
Re:Google's Requirement for Developers to Be Verified Threat... by vzaliva on Tuesday October 07, 2025 @03:41PM (#45507846)
Locked app store was my primary reason staying away from iPhone. Now, this is gone. It also open door for censorship, like disabling ICE-tracking or other politically inconvenient apps. This is a terrible decision for Android and for our freedoms.
Re:Google's Requirement for Developers to Be Verified Threat... by chasil on Tuesday October 07, 2025 @03:49PM (#45507932)
Google only directly controls the Pixel line.

OEMs may be forced to do the same, but 3rd party ROMs will not.

I do agree this cuts deeply for F-Droid.

Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @03:56PM (#45508021)
Google only directly controls the Pixel line because of antitrust action from the EU.

Originally, device makers who used Android themselves were contractually prohibited from manufacturing devices for any company that forked Android, for instance.

Re:Google's Requirement for Developers to Be Verified Threat... by bpye on Tuesday October 07, 2025 @03:58PM (#45508059)
> but 3rd party ROMs will not.

Google are also making that harder, at least for the Pixel line by no longer publishing the device tree as part of AOSP.

I know Fairphone do publish a buildable tree - though it's not yet available for their latest device - does anyone else?

Re:Google's Requirement for Developers to Be Verified Threat... by skrlet13 on Thursday October 09, 2025 @05:11PM (#45533131)
Also, you cannot unlock most phone's bootloaders nowadays, so you cannot even try them.
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

Re:Google's Requirement for Developers to Be Verified Threat... by hparadiz on Tuesday October 07, 2025 @04:18PM (#45508301)
Not to be dramatic but I'll ask the question.

Do we really want a future where 99.9% of people's pocket computers must ask for permission from one of two companies to run something on a device?

Re:Google's Requirement for Developers to Be Verified Threat... by ThatMedicIsASpy on Tuesday October 07, 2025 @05:36PM (#45509220)
I can buy EU software for my PC only to be required to sign in with google, apple, meta or microsoft. The lazy dev world isn't much better
Re:Google's Requirement for Developers to Be Verified Threat... by kyriakos on Tuesday October 07, 2025 @11:21PM (#45511715)
Unfortunately sign on with social media improves engagement and conversions in apps. It's not about being lazy it's about doing what will bring more users.
Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @04:29PM (#45508412)
It's entirely possible to prosecute Google for fraudulently marketing Android as open and force them to keep their promise.

If they want to have a closed platform, do what Microsoft did with Xbox and create something new.

Re:Google's Requirement for Developers to Be Verified Threat... by stockresearcher on Tuesday October 07, 2025 @06:52PM (#45509949)
> prosecute Google for fraudulently marketing Android as open and force them to keep their promise.

Sorry man. The EU Cyber Resilience Act is forcing these changes. An operating system is a class 1 important product. A tamper-resistant microchip is a class 2 important product. A device with a secure element is a critical product. Your smartphone has all of these pieces. Manufactures must follow a list of best practices to enjoy a presumption of conformity. That list of best practices is being compiled and made ready for publication, with full effect in 2026/2027. Google knows what is coming. Everyone big knows what’s coming.

True open source with no monetization can get a pass. Everyone else has to do this.

https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L...

Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @07:54PM (#45510427)
There is no reason to punish users outside the EU who still have the legal right to demand that Google keep its word.
Re:Google's Requirement for Developers to Be Verified Threat... by hyghjiyhu on Wednesday October 08, 2025 @10:12AM (#45516412)
Please explain to me what the relevant parts are. What are the requirement that forces verified developers?
Re:Google's Requirement for Developers to Be Verified Threat... by stockresearcher on Wednesday October 08, 2025 @10:20AM (#45516508)
Scheduled to be published in December.
Re:Google's Requirement for Developers to Be Verified Threat... by NotPractical on Wednesday October 08, 2025 @10:30AM (#45516601)
Even if the idea originally came from the EU, the fact that Google is rolling it out worldwide would seem to indicate that they already wanted to do this, no? And regardless of whether they wanted to or not (inside the EU), it does not invalidate criticism of the move from outside of the EU.
Re:Google's Requirement for Developers to Be Verified Threat... by sam_lowry_ on Wednesday October 08, 2025 @11:29AM (#45517268)
> True open source with no monetization

Even RMS needs money once in a while, short of eating bits of his own flesh.. oh wait!

Re:Google's Requirement for Developers to Be Verified Threat... by Ajedi32 on Tuesday October 07, 2025 @05:09PM (#45508916)
If the only thing standing in the way of closed platforms is that they have to be marketed as closed, you're just going to get everyone marketing their software like Apple does and nothing else will change.
Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @05:23PM (#45509054)
Here in the States iOS, XBox, PlayStation and Nintendo's various gaming platforms are all perfectly legal walled gardens.

If you don't like that, you have to do what they did in the EU and change the law.

Fraud is illegal here today, and Google's marketing was definitely fraudulent, so there is clearly something that can be done about it today.

Re:Google's Requirement for Developers to Be Verified Threat... by the8472 on Tuesday October 07, 2025 @04:55PM (#45508745)
Sony didn't have to reopen the PS3, it got away with a settlement.
Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @05:07PM (#45508893)
Sony didn't spend a decade marketing an "open" platform that allowed users to run any software they chose to run.
Re:Google's Requirement for Developers to Be Verified Threat... by the8472 on Tuesday October 07, 2025 @05:28PM (#45509120)
OtherOS was an advertised feature of the PS3. Are advertising claims now advisory until they mature?
Re:Google's Requirement for Developers to Be Verified Threat... by GeekyBear on Tuesday October 07, 2025 @05:59PM (#45509447)
Given that Sony lost a class action case seeking damages in court, clearly not.
Re:Google's Requirement for Developers to Be Verified Threat... by NotPractical on Wednesday October 08, 2025 @12:18AM (#45512015)
The only solution to this problem is new legislation. The case that Google fraduently marketed Android is flimsy at best.

People buying phones by and large do not care in the slightest about "openness". Whether or not their phone supports sideloading is completely and utterly irrelevant to them.

But aside from that, it would be enermously difficult to prove that Google made claims that were unequivocally false while advertising Android. Sure, they made some vague claims about Android being an "open" platform. But they had more than enough well-compensated lawyers on their side to avoid making specific promises about specific functionality that could eventually land them in court.

Finally, even if some of the claims Google made about Android in 2015 no longer hold up in 2025, that in and of itself is not illegal. Google is allowed to change and adapt Android over time as it sees fit. Though you and I may disagree with their findings, they have internally identified systemic security threats caused by unrestricted sideloading, and have created a solution to this real-world problem (however flawed it may be). There is no reason under the current laws of the United States that they should not be allowed to make those changes (aside from perhaps general antitrust law, but that is not enough in this instance as evidenced by the outcome of Epic Games' case against Google). Perhaps they will have to change their advertising going into the future, and they can definitely no longer reuse older advertising materials promoting Android's capability for unrestricted sideloading (if those exist). But just because they advertised Android as having feature X in the past does not mean that they would break the law if they were to remove feature X in the future after they stopped running those old ads.

(Yes, it gets a little blurry in the case of software because it often automatically updates and offers no option to downgrade. But phones don't last forever. In the worst case Google could just wait ~5 years from today to implement Developer Verification.)