Re:Chrome 68 will mark all HTTP sites as “not secure”
by ksk on Friday February 09, 2018 @04:58PM
(#16344204)
>And that's why chrome will mark your site as insecure.
That is a false statement. Using 'what could happen' logic, Windows should label Chrome/Firefox/IE as insecure/malware since someone could theoretically do bad things with those tools.
>Please propose something better (that doesn't come with its own significant drawbacks).
Why don't you start first? Since this HTTPS so-called 'solution' has its own significant drawbacks.
And that's why chrome will mark your site as insecure.
> why should I be forced to [..] beg for permission [..]
That seems to be the best thing humans came up with so far, if you want nice stuff that requires coordination. You also have to "beg" for a connection & ip address. You also have to "beg" for a DNS name. Please propose something better (that doesn't come with its own significant drawbacks).