Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-12 Thread Francis Djabri
We haven't run any studies on security indicators as yet. On Sun, Feb 11, 2018 at 5:55 PM, Bram Pitoyo wrote: > I’ve forwarded this conversation thread to our UX researcher and designer, > Francis and Jacqueline. If we’ve run any studies, they’d be able to link us > to a report. > > On 12 Febru

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-11 Thread Bram Pitoyo
I’ve forwarded this conversation thread to our UX researcher and designer, Francis and Jacqueline. If we’ve run any studies, they’d be able to link us to a report. On 12 February 2018 at 11:58, Karl Dubost wrote: > Johann, > > Le 10 févr. 2018 à 00:51, Johann Hofmann a écrit : > > There's a val

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-11 Thread Karl Dubost
Johann, Le 10 févr. 2018 à 00:51, Johann Hofmann a écrit : > There's a valid concern around warning fatigue (plastering so many sites with > "Insecure" that users easily dismiss it) and we made those prefs to be able > to run user studies on it. Did Mozilla run UX studies about it? If yes, li

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-09 Thread Johann Hofmann
t;> There's a tangible difference between text saying "Not Secure" and a >>> broken lock icon. I think that we're close, but we'd be making a >>> stronger statement than Chrome if we did this. >>> >>> On Fri, Feb 9, 2018 at 8:17 AM

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-09 Thread Jonathan Kingston
2018 at 1:55 AM, Martin Thomson wrote: > > +ffxdev > > > > There's a tangible difference between text saying "Not Secure" and a > > broken lock icon. I think that we're close, but we'd be making a > > stronger statement than Chrome if we did

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-09 Thread Tom Schuster
did this. > > On Fri, Feb 9, 2018 at 8:17 AM, Chris Peterson wrote: >> Chrome will start marking HTTP pages as "Not secure" in July 2018 (Chrome >> 68): >> >> https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html >> >> Firefox h

Re: Chrome will start marking HTTP pages as "Not secure"

2018-02-08 Thread Martin Thomson
+ffxdev There's a tangible difference between text saying "Not Secure" and a broken lock icon. I think that we're close, but we'd be making a stronger statement than Chrome if we did this. On Fri, Feb 9, 2018 at 8:17 AM, Chris Peterson wrote: > Chrome will star

Chrome will start marking HTTP pages as "Not secure"

2018-02-08 Thread Chris Peterson
Chrome will start marking HTTP pages as "Not secure" in July 2018 (Chrome 68): https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html Firefox has a similar insecure HTTP warning icon, currently disabled by the `security.insecure_connection_icon.enabled` pref ad