Re:Google Will Soon Shame All Websites That Are Unencrypted
by Cpoll on Wednesday January 27, 2016 @03:51PM
(#10983205)
> That makes your network insecure, not my page.
At which hop does it stop being "my" network and starts being "our" network? Your webhost? Your IX? Your country?
You can't shift the responsibility; only you can definitively secure the content coming out of your webpage.
Re:Google Will Soon Shame All Websites That Are Unencrypted
by geofft on Wednesday January 27, 2016 @04:26PM
(#10983541)
I've just wired you the amount needed to buy an SSL certificate from any of multiple reputable and well-priced providers. You can use the money I sent you to buy a cert from https://letsencrypt.org/ , https://www.startssl.com/Support?v=1 , or https://www.cloudflare.com/plans/ .
If those options aren't enough for you, let me know why and also how to non-vacuously send you money, and I'm happy to buy you a $4.99/year certificate from https://www.ssls.com/ssl-certificates/comodo-positivessl .
Re:Google Will Soon Shame All Websites That Are Unencrypted
by gilrain on Wednesday January 27, 2016 @03:41PM
(#10983118)
Just set mine up for free, today. Letsencrypt.org works great. I recommend the simp_le client.
Re:Google Will Soon Shame All Websites That Are Unencrypted
by dawnerd on Wednesday January 27, 2016 @04:08PM
(#10983381)
Yeah, there's really no excuse anymore really. They've made it insanely easy to generate certs.
Re:Google Will Soon Shame All Websites That Are Unencrypted
by kpcyrd on Wednesday January 27, 2016 @04:19PM
(#10983484)
Please read the article, this isn't about google the search engine, it's about google the browser vendor. Firefox nightly is doing the same already by default.
I'm always wondering if there's a correlation between the relevance of integrity for a site and the relevance of the site itself.
Re:Google Will Soon Shame All Websites That Are Unencrypted
by serge2k on Wednesday January 27, 2016 @04:08PM
(#10983380)
> Still not paying for a cert on my person home-pages
lets encrypt?
That page contains static HTML and does not need SSL, and it's not "insecure" just because you may be on a network which MITMs traffic. That makes your network insecure, not my page.
So yeah. Not interesting. Not worth it.