Chrome 56 will mark HTTP pages with password fields as non-secure

Re:Chrome 56 will mark HTTP pages with password fields as no... by UnoriginalGuy on Sunday January 22, 2017 @02:29PM (#13456802)

That's literally what my router's login page does. It is a text box but has JavaScript which converts each non-* character into a * character and stores the actual value in a JS variable.

Why? They added a "Show Password" radio and I guess they figured this hack made more sense than simply using JS to update the DOM to turn it from a type password to a type text.

[ Parent | on HN ]

Re:Chrome 56 will mark HTTP pages with password fields as no... by JoshTriplett on Sunday January 22, 2017 @02:46PM (#13456942)

My previous router did this to obscure password length, by inserting three stars into the field for every character typed. Which completely broke browser password managers, and the ability to paste the password.

[ Parent | on HN ]

Re:Chrome 56 will mark HTTP pages with password fields as no... by duskwuff on Sunday January 22, 2017 @03:19PM (#13457168)

IIRC, changing the 'type' of an input doesn't (or, at least, didn't) work in some browsers.

[ Parent | on HN ]