News for hackers. Stuff that matters.

A comment on Chrome 56 will mark HTTP pages with password fields as non-secure. Parent comment

Re:Chrome 56 will mark HTTP pages with password fields as no... by the_duke on Sunday January 22, 2017 @04:29PM (#13457610)
I don't really know what your point is.

This will mark pages as insecure that have a '<input type="password">' field on your page. If you don't have that, you are fine.

I don't know of any reasons to have a password field if it's not actually sensitive information that's being entered.

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Piskvorrr on Thursday February 02, 2017 @04:54PM (#13555102)
...for now. Marking all non-secured HTTP as insecure (duh) is in the pipeline - it seems.

This is actually a Good Thing - with HTTPS-friendly CDN and/or Letsencrypt, rolling out sites that are secure-by-default is now easier and cheaper than ever before.

[ Parent | on HN ]