3 ms·
Strewth, I can't even read that without wanting to go and uninstall every browser from every device I own. Are people really considering this? People that, y'k
by eponeponepon 9y ago
Strewth, I can't even read that without wanting to go and uninstall every browser from every device I own.
Are people really considering this? People that, y'know... matter?
edit: good lord, I read further and saw this:
3. Security and Privacy
Considerations
This section is non-normative.
...I mean... surely, surely that's the one bit that should be most gigantically normative? Right?
- pmoriarty 9y ago"This specification recommends device manufacturers practice defense in depth by designing their devices to only accept signed firmware updates and/or require physical access to the device in order to apply some configuration changes." Yes, let's put the burden of protecting users from browser-transmitted malware on to the hardware manufacturers, who've had a such a wonderful track record of caring about and protecting their users' security in the past. What could possibly go wrong?
- username223 9y agoAagh! "Let's take hardware designed to be connected to a machine by its owner, connect it to the whole internet, and blame the hardware when it gets hacked." Does anyone remember how long it took for single-user operating systems to harden themselves against remote attacks? Yeah, they're still working on it. Now imagine something like that, but for hardware that either never gets firmware updates, or is connected to the internet so it can have them pushed.
- duskwuff 9y ago> ...I mean... surely, surely that's the one bit that should be most gigantically normative? Right? No. "Security and privacy considerations" sections of standards documents are typically used for a analysis or discussion of the security/privacy posture of the standard. The security features are "baked into" other portions of the document.