The federal judge let Google off the hook in the antitrust case that the company supposedly lost. He said no to any serious remedy. And he indirectly killed Mozilla (Firefox and Thunderbird).

A good day for Google, and a terrible day for what's left of the open web.

https://arstechnica.com/gadgets/2025/09/google-wont-have-to-sell-chrome-judge-rules/

Google won’t have to sell Chrome, judge rules

Google’s penalty for being a search monopoly does not include selling Chrome.

Ars Technica
@dangillmor I think this is probably a relief. Google owning Chrome is awful, but anyone else buying it is even worse. A successful antitrust action would have put *Chromium* under a foundation outside Google's control and forced them to keep shipping Chrome based on that, with no control of the upstream. Not handed it over to someone with a worse mandate to monetize.
@dalias @dangillmor Bingo. I still trust Google’s developer and security teams on Chrome (and by extension, Chromium) far more than any of the trial balloon offers floated by “serious” suitors. Better stewardship under *OpenAI*? No thanks.

@matt_garber where can i read more about these details? the ars technica article was (unsurprisingly) pretty surface level

@dalias @dangillmor

@matt_garber @dalias @dangillmor So I have to express that if you think Google is good at security you are wrong. So wrong, I would argue Google fundamentally *doesn't understand* security. We literally straight up ban Chrome at the office.

@ocdtrekkie @dalias @dangillmor I’ll clarify because you’re right that Google certainly contains multitudes.

I believe while it may not be true of everything they ship, that Google also genuinely has world-class security researchers (e.g., Project Zero), engineers on infra, Go devs, and plenty more. I also think it’s reasonable to say that Google has invested a lot in browser sandboxing and other tech over the years, relative to the other engines. Also FWIW, security != privacy wrt Google.

@matt_garber @dalias @dangillmor Well privacy = security, so we're already up a creek... The problem is not that Googlers aren't smart, but that they don't understand the core principles of effective security, which is almost exclusively about humans, not cryptography.

Project Zero is a black hat group sent after companies or projects Google finds inconvenient.

@ocdtrekkie @matt_garber @dangillmor In some senses you're both right. At least among the ones I've met, the Googlers working on browser security are smart and believe they're doing something good for the public, but it's one of those cases where it's hard to see what's wrong with the model you're working in when your paycheck depends on not seeing it. Google's idea of security is very much not aligned with the interests of the public, and the browser team constantly do things required of them by other parts of the company, with poor justifications they're able to convince themselves to believe, that are extremely harmful to security.

I don't really deem them a factor tho in this question. Google's control of the browser is harmful, but anyone else who purchased it would want to get orders of magnitude more harm for the price tag they'd be paying.

@ocdtrekkie @matt_garber @dalias @dangillmor Can you explain why you think Chrome doesn't understand security? Specific examples of failure, or a general sense, or...?
@twifkak @matt_garber @dalias @dangillmor So specifically with Chrome, Google constantly pushes new APIs which enable malware and fingerprinting, over half of which other browsers consider actively harmful. Most of good security is disabling about half of the "features" Chrome has shoved into web browsers. Notifications API, WebUSB, etc. Meanwhile they pioneered removing the EV indicator because Google is committed itself to misunderstanding SSL security.

@ocdtrekkie @twifkak @matt_garber @dangillmor Removing EV indicator was good. EV was nothing but a vector for deceiving users. One of these two things must inherently be true:

Either you have to be sufficiently big to play (pro-monopolist), or

Anyone can setup a scam company with a name sufficiently close to some company users trust and get an EV issued to that name to deceive users that they're trustworthy.

@dalias @twifkak @matt_garber @dangillmor This is false. And even Google has admitted it in a backwards way but they're too committed to their doctrine to publicly admit EV is necessary. BIMI requires the "Verified Mark Certificate" in Gmail which is just "EV but we can't admit we were wrong".

@ocdtrekkie @twifkak @matt_garber @dangillmor BIMI is likewise bad. For the exact same reasons.

The only reason they insisted on doing something so ridiculous was that they previously made the decision to *hide the actual sender address* and only show a freeform text field the sender sets to anything they want.

Email clients should never show the sender name, only the raw email address, unless the name is in your address book matching the address.

@dalias @twifkak @matt_garber @dangillmor Why is BIMI bad? It's not. VMC and EV are the only things that actually approach a useful purpose for the entire WebPKI nonsense. Because while there may be holes worth shoring up they put a huge practical dent in the problem of enabling users to trust a message.

And it's important that you recognize that an example edge case is not important: They are practically extremely effective: Malicious use is basically zero.

@dalias @twifkak @matt_garber @dangillmor EV is an incredible example of the problem with the way Google thinks about security because it was real world effective but someone could at significant expense create a single test example where it was fooled and therefore is bad, but Google constantly pushes concepts that are cryptographically secure but provide no human security and are easy for bad actors to exploit with social engineering.
@ocdtrekkie @twifkak @matt_garber @dangillmor EV is an example of security-through-trusting-authority. Which is the exact same badness Google is always pushing.

@ocdtrekkie @twifkak @matt_garber @dangillmor Nobody needs to know "site I'm interacting with is a big respected company that gets a green lock". What folks need to know is that the party they're interacting with now is *the same party* they setup a prior relationship with.

None of the authoritarian validation systems do anything to solve this problem.

@dalias @twifkak @matt_garber @dangillmor I would definitely prefer long-lived certificates which you can identify having dealt with before, and ideally ways of distributing some indications of who other users are trusting that are likely relevant to you. But in a current sense of what we have, where a few dozen companies just certify globally to everyone every single site out there... EV still works better than what we have.

@ocdtrekkie @twifkak @matt_garber @dangillmor The long-lived identifier you have to know you're dealing with the same party is the *domain name*. That's the whole point of a domain name. The certificate validates that you're communicating with the legitimate owner of the domain name. Whether it's EV or not makes no difference.

Yes there are way this system could be a lot better. But "trust some freeform text field in an EV cert" is so ridiculously worse than "use the domain system the way it was intended".

@dalias @twifkak @matt_garber @dangillmor Has an EV cert *ever* been used maliciously? Like not in a test case but for actual abuse?

The trusting authority part is sort of useful, if we insist on having CAs at all, but the funny part is the most useful part of EV is the part of TLS modern organizations want to eliminate: Cost. Cost is why EV is basically a guaranteed indicator you've landed on a safe site.

@ocdtrekkie @twifkak @matt_garber @dangillmor Yes, they have. I don't have receipts readily available and Google is broken and won't find them, but it's happened.

However, there are two sides to the malice of EV. One is lending trust to scammers who get an EV cert to exploit trust. The other is the harm to everyone who doesn't pay the EV racket, when users who don't understand wonder why the browser UI shows them as "less secure".

@dalias @twifkak @matt_garber @dangillmor I don't need to verify the real world identity of every blog site I'm viewing. I do think EV-to-flesh-and-brick should be required for anything approaching a payment transaction. And that for anyone legitimately conducting a payment transaction, EV is a minimal effective cost.

@ocdtrekkie @twifkak @matt_garber @dangillmor Um, most payment transactions are with parties I absolutely do not expect to dox themselves to be able to recive payment.

I do not see how you can call yourself a "privacy advocate" and yet claim every payment transaction should require an EV certificate. 🤦

Aside from that, payment transactions are low-stakes, lowest-possible even. If they're fraudulent the payment processor reverses them.

@dalias @twifkak @matt_garber @dangillmor I think when we've hit the point you are looking for sniping opportunities based on my profile bio we've escaped polite discourse, so I'll call it here. But suffice to say, effective security measures depend on humans (because that's also where the mistakes are made), and generally does not scale/automate well.
@ocdtrekkie @twifkak @matt_garber @dangillmor There's an abundance of information out there about what a joke BIMI is. I haven't spent any time thinking about it since several years ago and I'm not going to go dig the stuff up for you.
@dalias @twifkak @matt_garber @dangillmor I have read all of the marketing on it and do not need links. They are wrong.

@ocdtrekkie @twifkak @matt_garber @dangillmor LMAO even BIMI Group says:

"BIMI enables brands to have control over the logos displayed with their email. It is important to know that BIMI is not a security solution."

IT IS IMPORTANT TO KNOW BIMI IS NOT A SECURITY SOLUTION.

@twifkak @matt_garber @dalias @dangillmor Privacy of course, is a critical component of security as well, so Google's decision not to block third party cookies when *every other browser did* makes it a complete nonstarter from a security standpoint. Before we even talk about things like constantly introducing new attempts at web standard spyware like FLoC.

@ocdtrekkie @matt_garber @dalias @dangillmor Google cares about security, such as secure channels, ever since Snowden. The last thing they want is someone snooping on "their" data, inside or outside their data centres.

Privacy is not a concern, so long as they have power over advertisers.

@dalias @dangillmor Yeah I agree with this. Reminder, the vast majority of college students and people who use their personal computers for work must run a chromium-based browser on their personal computer. Right now, that means we can run a FOSS version of chromium and that it works well on Linux.

Who would benefit if the courts let Perplexity AI make chromium proprietary Windows-only software?

@dalias @dangillmor After hearing stories of Perplexity considering buying chrome... yeah I am far happier with Chrome staying in Google's space.

Google is also pretty awful for the internet but at least they're mostly interested in exploiting humans to deliver ads and sell data instead of, whatever the hell AI companies think they're trying to accomplish. Google comes off as far less likely to accelerate the Dead Internet vs Perplexity.

@dangillmor

If Mozilla dies and Thunderbird with it, there's always (Al)Pine.

@dangillmor I'm not attempting to defend google here, but I've seen two assertions now that Mozilla is going to die without Google funding (which would be absolutely true); but this is straight from the article: "Under the court's ruling, Google will still be permitted to pay for search placement—those multi-billion-dollar arrangements with Apple and Mozilla can continue."

what am I missing? Has google indicated it's going to stop supporting Mozilla? Or was the hope that, if they lost Chrome, they'd end up dumping a lot more money into Firefox?

@dangillmor How did he kill Mozilla? (I can’t find that referenced in the article, it just says that Google can keep paying Mozilla for search.)

@dangillmor a few questions:

1) how does this kill mozilla (even if indirectly)? what does thunderbird have to do with google owning chrome?

2) what is the argument for google's ownership of chrome allow it to have a monopoly on search?

3) if google was forced to divest from chrome, who would take those shares?

4) what does all of this mean in relation to google's development efforts on chromium?

@xyhhx @dangillmor i also don't get one, especially since its even mentionend "Under the court's ruling, Google will still be permitted to pay for search placement—those multi-billion-dollar arrangements with Apple and Mozilla can continue."
@bws sometimes it seems @dangillmor has some pretty off base takes on tech, and i wish he'd consult someone with deeper technical understanding before making such comments considering his following

@xyhhx @dangillmor

Right on! Chrome is a cost center, not a revenue source, afaik.

It's an open source browser ( Chromium ), called Chrome when bundled with Google's snoopware.

I'm asking, not stating here. Someone please explain.

@xyhhx @dangillmor It doesn't kill Mozilla, the judge pointed out specifically that preventing Google's default search deals would hurt them.

@tad lol

judge: *delivers ruling to mitigate damage to mozilla*
@dangillmor: this ruling kills mozilla

@dangillmor ever since Trump took office, i just knew that corporations are going to be let loose to do whatever they want

@dangillmor divestiture of Chrome was a horrible proposal for breaking Google's monopoly anyway. As someone elsewhere mentioned in the thread Chrome is a cost center.

Forcing Google to sell off its advertising arm would be better. A lot of decisions that hurt users and customers are driven by making Google's ads more pervasive and more profitable. It would also significantly punish them for their bad behaviour since advertising actually makes Google money.

@dangillmor "Under the court's ruling, Google will still be permitted to pay for search placement—those multi-billion-dollar arrangements with Apple and Mozilla can continue."
@dangillmor how is this bad for Firefox/Thunderbird? I don’t see that elaborated in the article.

@allancavanagh @dangillmor well, if Google doesn't have this over their head, why should they carry on funding a competitor as a "look, not a monopoly" artifact?
I think #mozilla might do much better without the torrents of ad and privacy cash from #google ...

#firefox #Thunderbird

@falken @dangillmor thanks, I wasn’t aware Google funded Mozilla.
@dangillmor @jwz Why specifically is this bad for Mozilla?