News for hackers. Stuff that matters.
Re:Chrome breaks the Web by danaliv on Monday November 06, 2017 @02:21PM (#15638152)
> Regulatory compliance.

> there are plenty of regulations in certain setting that require us to disallow client applications from auto-filling form fields.

And which regulations would those be, specifically?

Re:Chrome breaks the Web by agentultra on Monday November 06, 2017 @02:56PM (#15638501)
If I recall in Part 11 compliance (which is how the FDA regulates software in the US) one is required to ensure that "Passwords are not remembered by [browsers] and applications."

From an ISO/IEC/IEEE 29148 perspective the language might be "shall not remember passwords" which would imply a legally binding requirement for compliance purposes.

This doesn't preclude applications from using autocomplete on form entry from password managers; just that the browser is not allowed to remember the entered password.

However in practice I've seen most systems deploy their applications on a target platform that runs the browser in "kiosk" mode, which if I recall from the time, was an IE-only thing. In more modern times we're starting to see consumer-level tablets and devices enter the mix and I'm not even sure if those can be locked down into a multi-user/kiosk type mode. Regardless... the web is a difficult platform for this kind of stuff.

Re:Chrome breaks the Web by user5994461 on Monday November 06, 2017 @07:19PM (#15640151)
Good thing that the NIST published updated recommendation on passwords, it supersedes all these previous regulations.
Re:Chrome breaks the Web by agentultra on Monday November 06, 2017 @08:45PM (#15640481)
I love the NIST. That's good to hear.
Re:Chrome breaks the Web by tinus_hn on Tuesday November 07, 2017 @07:17PM (#15649005)
If you want the browser to conform, you do control the browser. It isn't hard to set it up so it doesn't do autocomplete.