Re: Draft finding - "Transitioning the Web to HTTPS"

20.01.2015, 18:02, "Philip Jägenstedt" <philipj@opera.com>:
> On Tue, Jan 20, 2015 at 2:18 PM,  <chaals@yandex-team.ru> wrote:
>>  20.01.2015, 15:44, "Philip Jägenstedt" <philipj@opera.com>:
>>>  On Tue, Jan 20, 2015 at 1:28 PM,  <chaals@yandex-team.ru> wrote:
>>>>   19.01.2015, 15:01, "Anne van Kesteren" <annevk@annevk.nl>:
>>>>>   and if anything we should move towards making it impossible to connect to such sites.
>>>>   I'd prefer you don't interfere with my decisions about what I want to look at and read. That is a whole step beyond suggesting to me that I might not be getting what I asked for.
>>>>
>>>>   The latter is, when done right, a useful service. The former is censorship, and while I support the right of the society I live in to decide that some things should not be made available, I find it highly inappropriate that a browser vendor would take it into their hands to make such decisions.
>>>  Do you find it inappropriate that the Yandex Browser is currently
>>>  unable to connect to https://crypto.cat/ and https://tv.eurosport.com/
>>>  (demo site) with no apparent option for ignoring the problem?
>>  Yes, of course, Did you file a bug, or should I?
>
> I did not file a bug as I don't think it seems like a good idea to be
> able to click through all certificate errors.

Fair enough.

(FWIW, a simple click through process obviously introduces problems…)

> You can do what you like with your own browser, of course.

(Actually, since it isn't personally mine… but indeed, we can)

cheers

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Wednesday, 21 January 2015 21:49:49 UTC