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 dsp1234 on Monday January 23, 2017 @10:57AM (#13463025)

Firefox has started to do this recently

"Note that is warning in the url bar is only in Firefox Nightly and Firefox Developer Edition. This has not been released to Firefox Beta and Firefox Release."[0]

So this is not a security feature that most end users can rely on, yet.

[0] - https://developer.mozilla.org/en-US/docs/Web/Security/Insecu...

[ Parent | on HN ]

Re:Chrome 56 will mark HTTP pages with password fields as no... by theandrewbailey on Monday January 23, 2017 @04:09PM (#13466056)

Firefox Release channel has been logging console errors for this for at least two years.

"Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen."

[ Parent | on HN ]

Re:Chrome 56 will mark HTTP pages with password fields as no... by blacksmith_tb on Monday January 23, 2017 @12:15PM (#13463738)

Looks like that url lost its final char [1]

I use DE, so I have been seeing these for a little while, but I think even in the stable channel you can toggle the security.insecure_password.ui.enabled param to true in about:config.

1: https://developer.mozilla.org/en-US/docs/Web/Security/Insecu...

[ Parent | on HN ]

Re:Chrome 56 will mark HTTP pages with password fields as no... by vaidik on Monday January 23, 2017 @01:38PM (#13464621)

Well it will soon land in stable as well I am sure. But its amazing to see major browsers moving in this direction and educating users about security.

[ Parent | on HN ]