Re:Chrome 56 will mark HTTP pages with password fields as no...
by clamprecht on Sunday January 22, 2017 @04:57PM
(#13457797)
What if the <form> submits to an https page but the page is served up on an http page? The form submission will be secure, correct? Will Chrome still mark as insecure?
[ Parent
| on HN ]
Re:Chrome 56 will mark HTTP pages with password fields as no...
by dbbk on Sunday January 22, 2017 @05:04PM
(#13457844)
The form submission is only half the issue. If the http page gets compromised the malicious party could simply read the contents of the password input.
Re:Chrome 56 will mark HTTP pages with password fields as no...
by clamprecht on Sunday January 22, 2017 @05:15PM
(#13457926)
thanks
Re:Chrome 56 will mark HTTP pages with password fields as no...
by waskosky on Sunday January 22, 2017 @05:16PM
(#13457936)
Technically it would be possible to use JavaScript to intercept the onSubmit event of such a form, and alter the submission location or send the data insecurely wherever you want with AJAX, completely ignoring the destination action that came with the initial HTML. This is one of the reasons people have needed to use forms within secure iFrames to circumvent PCI Compliance requirements when sending credit card numbers.
Re:Chrome 56 will mark HTTP pages with password fields as no...
by gregmac on Sunday January 22, 2017 @08:22PM
(#13458923)
I was also thinking of the opposite: submitting from an https-loaded page to an http page. I can't imagine why any application would do this (other than by mistake), but it would ideally be flagged as insecure as well.
Re:Chrome 56 will mark HTTP pages with password fields as no...
by Wilya on Sunday January 22, 2017 @09:18PM
(#13459194)
It's already the case most of the time. If you submit via a plain form (without js), you get the (old) "This page is encrypted, but the information you submitted will be sent unencrypted" message. If you submit via an XMLHttpRequest, it should be blocked as Mixed Content.