Re:RFC 9849. TLS Encrypted Client Hello
by ndriscoll on Wednesday March 04, 2026 @09:35PM
(#47256792)
Because consumer devices are barely if at all capable of even setting policy, are basically incapable of enforcing it, and are generally adversarial. It's also easy to apply different policies to different clients at the network level.
[ Parent
| on HN ]
Re:RFC 9849. TLS Encrypted Client Hello
by pocksuppet on Thursday March 05, 2026 @03:46AM
(#47259234)
The new California and Colorado laws force consumer devices to be capable of setting and enforcing policy.
Re:RFC 9849. TLS Encrypted Client Hello
by ndriscoll on Thursday March 05, 2026 @08:46AM
(#47261504)
They do not. Here's the California bill[0]. Here's the Colorado bill[1]. They're short. Nowhere is there something about letting me set policy (e.g. blocking applications/services, presenting plaintext traffic to filtering software, setting time-of-use restrictions, etc.). In fact, it requires my operating system to give any application developer PII about me and requires the application to collect it, even when it's irrelevant (functionality is not age-restricted).
Or did you have some other laws in mind?
[0] https://leginfo.legislature.ca.gov/faces/billTextClient.xhtm...