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 Sir_Substance on Sunday January 22, 2017 @06:58PM (#13458526)
>Or like "did you know your house COULD have been ransacked today, but it didn't happen!!" >Now all my users are going to hear that my site is insecure, when nothing at all changed.

I'm not sure you should be allowed to drive a webserver.

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by NTripleOne on Monday January 23, 2017 @10:17AM (#13462700)
I'm not sure what the "driving" equivalent is for a battleship, but I'm pretty sure you do that to a server, not drive it.

Commandeer?

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Sir_Substance on Monday January 23, 2017 @04:55PM (#13466454)
Commandeering web servers will probably get you arrested ಠ_ಠ

I don't know what you do with a battleship. Helm it, maybe?

[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by NTripleOne on Tuesday January 24, 2017 @05:24AM (#13470196)
No no, you only get arrested for commandeering next to another server and then boarding it.
[ Parent | on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no... by Vendan on Tuesday January 24, 2017 @08:22PM (#13477578)
Commandeer: Verb: take possession of (something) without authority.

Sounds like you'd get arrested for that....

[ Parent | on HN ]