After update to Chrome 56, I don't see the "not secure" info
Reported by
komm...@googlemail.com,
Jan 26 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: 1. Go to http://www.freenet.de 2. Hit F12 3. This page includes a password or credit card input in a non-secure context. A warning will be added to the URL bar in Chrome 56 (Jan 2017). For more information, see https://goo.gl/zmWq3m. What is the expected behavior? I expect the info "not secure" to appear left to the URL on an http page with login form. I don't expect about a future Chrome 56 when browsing with Chrome 56. What went wrong? Something is weird after the update today. Did this work before? N/A Chrome version: 56.0.2924.76 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Jan 26 2017
(removing security labels since this is not a vulnerability in Chrome)
,
Jan 26 2017
,
Jan 26 2017
,
Jan 27 2017
I can only find the similar value "684d1cdf-ca7d8d80". Does this mean that I don't have the warning feature yet and it will come with some future version for me, eventually?
,
Jan 27 2017
Yes.
,
Jan 27 2017
Thanks for the reply. Yes, it looks like you're in the control group that doesn't have the feature enabled yet, but it will be enabled for you eventually. If you'd like to force-enable it now, you can do so by going to chrome://flags and setting "Mark non-secure origins as non-secure" to the "Display a verbose state..." option.
,
Jan 27 2017
Thank you for the info. From news about the new release I got the impression that everyone got it in version 56. Sorry for the noise.
,
Jan 27 2017
Re #8: Yes, the plan is that all M56 users will eventually have the feature enabled. (Perhaps surprisingly, features can be enabled /after/ launch) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by est...@chromium.org
, Jan 26 2017Labels: Hotlist-HttpBad Team-Security-UX