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 technion on Sunday January 22, 2017 @07:43PM (#13458742)
Well I'm fairly certain it will go like this for me.

Pm - "why is this page insecure"

Developer - "chrome labels password fields as insecure over http"

Pm - "we'll need to setup encryption. It will need to be FIPS-140 certified or it's not secure"

Developer - "But you didn't care when there was no encryption"

Pm - "We don't need to certify plaintext, that should be obvious. You need to learn more about security".

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by theandrewbailey on Monday January 23, 2017 @04:13PM (#13466090)
Developer - "FIPS-140 has been compromised by the NSA. We don't want government spies in our servers."
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by morenoh149 on Monday January 23, 2017 @12:36AM (#13460036)
where do you work
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by msimpson on Monday January 23, 2017 @10:30AM (#13462823)
They seem to be a government contractor.
[ Parent | on HN ]