6 ms·
Embracing HTTPS
- rgbrenner 12y agoIf you run a news site, or any site at all, we’d like to issue a friendly challenge to you. Make a commitment to have your site fully on HTTPS by the end of 2015 and pledge your support with the hashtag #https2015. This article is funny... written by the CTO for nytimes (et al).. asks news sites to make a commitment to HTTPS... but fails to commit to it for NYTimes.
- peter_l_downs 12y agoThe page itself is plain HTTP, too.
- AlyssaRowan 12y agoYeah, you don't get to say that when https://open.blogs.nytimes.com/2014/11/13/embracing-https/ https://open.blogs.nytimes.com/2014/11/13/embracing-https/ isn't even listening on port 443. Dear Akamai: when are you going to make TLS 1.2 support free? Cloudflare has. :)
- moe 12y agoDear Akamai: when are you going to make [...] free? Lol.
- joelrunyon 12y agoDid they make any notice of commitment to this for themselves?
- rgbrenner 12y agoThey didn't in the article... and I don't see anything from them with the #https2015 hashtag.. and none of them posted a commitment for the nytimes on their feeds. So I'm going to go with no. https://twitter.com/rajivpant https://twitter.com/rajivpant https://twitter.com/eitanmk https://twitter.com/eitanmk https://twitter.com/nytimes https://twitter.com/nytimes Doesn't look like she's an NYtimes employee, but her name is on the article.. so: https://twitter.com/elenakvochko https://twitter.com/elenakvochko
- joelrunyon 12y agoTwo questions on this (from an novice-techie pov): 1. Https is slower. From a practicality standpoint - is it that much slower to actually make a difference from a UX side of things? 2. I've implemented https on one of my sites, but in chrome, it's not full green, but appears as https with the broken lock. Any idea on what that means and how to fix it?
- durkie 12y agore 2: you're loading mixed https and http content. open up the devtools console and it will show you what's being loaded over http.
- mappu 12y agoEither that, or they have a SHA-1 certificate that expires in 2016 or later - https://www.ssllabs.com/ssltest/ https://www.ssllabs.com/ssltest/ will tell you for sure.
- dspillett 12y agoThe cut-off isn't 2016-01-01. I have a cert using a SHA1 fingerprint which expires in June 2016 (see https://random.spillett.net/ https://random.spillett.net/) and Chrome is not currently complaining about that.
- igrigorik 12y agore 1: see https://istlsfastyet.com/ https://istlsfastyet.com/
- kijin 12y agoIf you just put a static "Hello World" webpage on a server and try to benchmark it with something generic like `ab`, yes, HTTPS appears to be several times slower than HTTP. If you put a real web application on that server, enable all the bells and whistles (keep-alive, session cache, OCSP stapling, SPDY, etc), and configure your benchmark tool to make use of those features, the performance penalty of HTTPS becomes less than 5%. And that was a couple of years ago on a relatively low-end VPS. Nowadays, the difference is probably even smaller.
- igrigorik 12y agoFor the record, it's worth noting that we're starting from a state that's nothing short of disastrous: https://alexgaynor.net/2014/nov/12/state-of-news-tls/ https://alexgaynor.net/2014/nov/12/state-of-news-tls/ Let's hope that twelve months from now, we're looking at a very different landscape. Kudos to NYTimes for issuing the challenge. At the very least, this is an important conversation starter.
- Animats 12y agoPushing too hard for HTTPS can lead to HTTPS as security theater. Cloudflare offers this as a service; they call it "Flexible SSL". They get a multi-domain SSL certificate for a huge number of unrelated domains, and let people connect to that. The data is decrypted at Cloudflare, and retransmitted in the clear to the destination site. The user thinks they have security, and they have a little, but less than they think. The multi-domain cert makes some attacks possible. If an attacker can mess with DNS near the client end (perhaps at a public WiFi access point), and can break into any of the sites listed on the cert, they can do an MITM attack. A cert with both an important site and a weakly secured site creates an easy attack target. Multi-domain certs are used because IPv4 space is full and Windows XP doesn't support Server Name Indication, which allows a unique cert for different domains at the same IP address. So if you want SSL on a shared IP address, and need to support good old IE6 over IPv4, multi-domain certs are necessary. XP still has 19% market share on line, as of October 2014. Everything else has supported SNI since 2007 or so. I have a paper on this: http://john-nagle.github.io/certscan/whoamitalkingto04.pdf http://john-nagle.github.io/certscan/whoamitalkingto04.pdf This identifies all the major front-end services using shared SSL certificates. Cloudflare has 36,280 second level domains tied to "*.cloudflare.com". Incapsula, the DDOS protection service, has 1471. Once you're past the top 20 such services, no site has more than about 100. Once IE6 has died off, the CAs can stop issuing certs containing unrelated domains. But not yet.
- Rapzid 12y agoHoly S*. I was about to call BS on you because I know CloudFlare supports end-to-end TLS then I read this: https://www.cloudflare.com/ssl https://www.cloudflare.com/ssl: > SSL can be difficult for website administrators to set up. > For sites that require more advanced SSL configurations, CloudFlare supports custom certificates from any certificate authority, full end-to-end SSL with robust certificate checking... Just, wow. TLS is NOT hard to setup for a website administrator. I think I just lost a ton of respect for CloudFlare. Granted, most threats would be between the client and CloudFlare anyway(that is to say, on the wrong side of the tracks), but still....
- Animats 12y ago
- NickKitchen 12y agoIt's important to note that the benefits of having SSL far outweigh the potential problems. The cost is fairly low for a business to have a certificate for their main domain, the speed difference is not very noticeable (to the point that many major social networks have https on every page). Every website should be developed with the ability to add https on every page
- Panino 12y agoTo push the ball forward, major link aggregators like reddit could implement HTTPS Everywhere style code. The front page has numerous examples of linked content over plaintext http that is also offered over https.
- gojomo 12y agoIt's so critically important, we'll commit to doing it within 14 months.
- spacefight 12y ago"By the end of 2015". How about do it by the end of next quarter, seriously!?
- 101914 12y ago"In light of a growing number of cyber security and data privacy concerns, replacing HTTP with its secure alternative, HTTPS, is becoming increasingly important." s/its secure alternative/a secure alternative/ s/,HTTPS,// This NYT blog post reads like an advertisement. If the newspaper is worried about guaranteeing the authenticity of its web content, then why don't they publish their SSL certificate in the print version? For scanning/OCR. No third party CA needed. When connecting to the desired website, I can check for the correct certificate myself, thanks. This is not a perfect solution, but it is better than third party CA's or letting third parties embed certificates in browsers where no user ever looks at them. In my opinion.
- yuhong 12y agoBTW, nytimes.com is TLS 1.3 intolerant. https://www.ssllabs.com/ssltest/analyze.html?d=nytimes.com&s=170.149.168.130 https://www.ssllabs.com/ssltest/analyze.html?d=nytimes.com&s...