News for hackers. Stuff that matters.

A comment on Google workspace threatening to block Firefox access. Parent comment

Re:Google workspace threatening to block Firefox access by insanitybit on Friday June 19, 2026 @03:37PM (#48602373)
My point was that CAA's threat model is flexible based on your requirements. If your requirement is "an attacker with the ability to make arbitrary network requests from the host can not pretend to be Chrome", CAA does not work unless you have OS/Hardware support (which ChromeOS provides).

I just don't think that matters much. CAA is policy enforcement, it is not a full MDM solution, nor is it antimalware.

[ Parent | on HN ]
Re:Google workspace threatening to block Firefox access by Brian_K_White on Friday June 19, 2026 @05:18PM (#48603343)
If it can't prove what it purports to prove, then it is not policy enforcement, because it is not anything enforcement.

But someone thinks it is, which is harmful to them on top of being an annoyance to everyone else.

[ Parent | on HN ]
Re:Google workspace threatening to block Firefox access by insanitybit on Saturday June 20, 2026 @01:47PM (#48611274)
That's just a misunderstanding of the threat model. It's like saying "if someone can just mitm TLS it's pointless" when that "someone" is in the position to run arbitrary code on the client. Mitigations map to specific attacker positions.
[ Parent | on HN ]