14 ms·
CloudFlare, We Have a Problem
- fweespeech 10y ago> This may not sound that bad - after all, they're just a service provider, right? - but let's put this in context for a moment. Currently, CloudFlare essentially controls 11% of the 10k biggest websites, over 8% of the 100k biggest websites (source), and almost 5% of sites on the entire web (source). According to their own numbers from 2012(!), they had more traffic than several of the most popular sites and services on earth combined, and almost half the traffic of Facebook. It has only grown since. And unlike every other backbone provider and mitigation provider, they can read your traffic in plaintext, TLS or not. https://www.datanyze.com/market-share/cdn/ https://www.datanyze.com/market-share/cdn/ Amazon and Akamai are both larger providers than Cloudflare. Akamai also can function similarly to the criticism leveled against Cloudflare (i.e. No TLS to the edge, so it can be meddled with.) Tbh, I'd be more worried about Amazon's position on that pie than Cloudflare since its comparable to Google's. https://www.comscore.com/Insights/Rankings/comScore-Releases-January-2016-US-Desktop-Search-Engine-Rankings https://www.comscore.com/Insights/Rankings/comScore-Releases... Its rarely healthy for any market to have a majority owned by a single player, even if Tech tends to generate winner-take-most situations in the marketplace.
- pavs 10y agoI don't understand why Cloudflare is used by so many sites. I would guess that for 95% of it's users, it doesn't solve any real problem. http://www.slashgeek.net/2016/06/07/cloudflare-making-internet-little-bit-faster-select-group-people/ http://www.slashgeek.net/2016/06/07/cloudflare-making-intern...
- reefoctopus 10y agoHow about because they serve hundred of terabytes of our images for $20/month? It has been well worth the money.
- pavs 10y agoI am talking about free users.
- detaro 10y agoThey'll serve quite a lot of traffic for those as well. I've seen quite a few people recommend a combination of Amazon S3 and Cloudfront for hosting static sites.
- angry-hacker 10y agoThe same applies to free tier, I need 5x less server power thanks to cloudflare and I get it for free! Including other useful things.
- gkoberger 10y agoFor me, it's so I don't have to deal with SSL. Sure, SSL isn't hard... but I have thousands of things more important to do than worry about where my keys are and when it expires. There's some nice bonus features like redirects, error pages, etc. It takes 10 seconds to sign up, is cheap, makes something complicated very simple, and offers immediate value. Anyone building a developer tool should use CloudFlare as a case study. EDIT: To the person who replied to me: Heroku, Shopify, and other similar services already serve their sites as HTTPS; Cloudflare just lets you throw HTTPS on a custom domain. It's HTTPS from top to bottom, don't worry.
- yoo1I 10y agoIf I understand you correctly your setup is exactly what's described in the article: your_server <--- no TLS ---> CloudFlare <--- TLS ---> Browser If that's the case you are putting your users at risk, by pretending there is a TLS connection to your server when really it's only to CloudFlare. The connection from CloudFlare to your server is completely unprotected and is routed over the public internet. That's not an acceptable setup. If I am communicating to a service that is TLS protected and I see the little green icon in the top left of the bar, I should be confident that my data that I am communicating to you is not routed over the public internet unprotected! You say this: > makes something complicated very simple You made it simple by simply not doing it
- sqldba 10y agoThe browser indicator is working properly according to the standard. That's what standards are - you don't get to complain about intent just because it doesn't mean to YOU what YOU WANT it to mean. Traditionally certificates have been very expensive for little unpaid blogs to have, and difficult to setup. LetsEncrypt is a very new solution but it will be a long time until hosts support it; remembering most of us are on simple cPanel setups so until it's baked INTO cPanel and hosts have upgraded it's unusable for a majority of the web. Just because we can run a web site doesn't mean we can hack layers into web internals. This is in part the fault of LE's idiotically short and crippling certificate lifespan. Lord knows why they did it but they knew it would screw us from the beginning. "Hey you should automate this, but seeing as you can't, no cert for you." Google prefers https content. Cloudflare gives small people a better slice of those readers. Ultimately nobody gives a shit that you're reading the semi-encrypted content I publish. NOBODY. Oh no you read how a database works? If that's illegal where you live then I think you're in much deeper survival problems than whether your browser button is magically misleading you (which it isn't; it's a guide, one that reveals itself once you click through, which is again exactly how it was designed).
- danneu 10y agoThey cloak my origin.
- mikecke 10y agoCloudFlare passes your origin.
- manigandham 10y agoHow so?
- tyho 10y agoX-Forwarded-For https://support.cloudflare.com/hc/en-us/articles/200170706-How-do-I-restore-original-visitor-IP-with-Nginx- https://support.cloudflare.com/hc/en-us/articles/200170706-H...
- detaro 10y agowrong direction. Reveals client IP to server, not server IP to client.
- dylz 10y agoIf you are on free/pro (ddos protection starts on business+ iirc) they will just pass through your A record unproxied after attacked
- manigandham 10y agoAll plans have protection, free has lower limits but still substantial. Pro has higher limits and Business is unlimited. Given the pricing, that's very fair. They won't automatically unproxy you without notice. If you're getting attacked, you need to pay for the level of protection you need.
- joepie91_ 10y ago
- unchaotic 10y agoThey've got a very compelling free tier to get you roped in. Works great as a CDN, integrated SSL, great interface, DDoS protection / firewall, page rules - there are just a few of the useful features. Is there a more comprehensive free tier anywhere else ? P.S. I'm not saying they are the best choice. They are simply too convenient & comprehensive to get started. With a single click your site can "claim" to be HTTPS even though the upstream connection "may not" be encrypted.
- aorth 10y agoDNS!
- api 10y agoAmazon Route 53 is better.
- PuffinBlue 10y agoIt isn't free, it's more complex to set up and it uses some of its own terminology like 'Hosted Zones' that need to be understood. Just 3 ways in which it's not better. It's probably better if you define the comparison in terms of flexibility/control etc etc, but simply stating it's 'better' doesn't really add anything to the conversation.
- api 10y agoWe host a big domain there and it's like five bucks a month. Of course we don't use the more expensive features just basic DNS and the API.
- joepie91_ 10y agoRight, but this is the pretty much precisely the problem. It's just the Nth generation of "just centralize the internet through us and we'll take care of everything for you", but this time marketed at startups. All the usual problems with centralization still apply. (It's still not really "DDoS protection", by the way. They just don't offer that on their free plan.)
- NEDM64 10y agoFree SSL. Enough reasons for me.
- pmlnr 10y agoLetsencrypt?
- dredmorbius 10y agoTBF that's only just getting started. Sites have been up for a while.
- joepie91_ 10y agoWhile true, StartCom and WoSign have been around for a while (even if they have some shadiness issues of their own). I wouldn't necessarily hold it against somebody to have picked CloudFlare because of this in the past, but in 2016 it's simply no longer a reason to keep using CF.
- bigbugbag 10y agoFree MitM attack. Enough reason not to. https://scotthelme.co.uk/tls-conundrum-and-leaving-cloudflare/?PageSpeed=noscript https://scotthelme.co.uk/tls-conundrum-and-leaving-cloudflar... https://stirling.co/blog/cloudflare-mitm/ https://stirling.co/blog/cloudflare-mitm/
- manigandham 10y agoThese are posts that always repeat the same thing: don't use Flexible SSL. Fine, that's your choice as the site operator to use or not use that option. Why blame the provider for your configuration choice?
- joepie91_ 10y agoNo, they don't. At least one of those posts is specifically about Full SSL, as is my article. You cannot proxy through CloudFlare without an MITM risk, by design. No matter how you configure it.
- drdaeman 10y agoDDoS protection on a budget. A typical hosting provider would shut down the port if they see any heavy ingress traffic. Or maybe won't shut it down if their network can tolerate it, but won't bother to filter either, so the server would be overwhelmed and down anyway. There are providers that help, but they cost extra. CloudFlare, on the other hand, is $20/mo (or even free). Not much protection at this level, but it well-scares kiddies away with "uh, it's behind the CloudFlare", and if someone still hates you (and you haven't screwed up concealing where the real server is), you can upgrade the plan and still try to remain online. Don't see any other value, except, maybe, for caching/CDN stuff. TLS is done wrong (as described in the OP article), DNS management is a toy (the old fart in me always prefers the zonefiles), minification should be done (and we do) at packaging phase - not runtime and WAF doesn't have any details about what it does (half of the rules are, basically, "enable the we-dont-tell-you-what-it-does rule and hope it won't break your site in a subtle manner").
- joepie91_ 10y agoThe article mentions several alternatives that are less than $20/month for actual DDoS mitigation.
- api 10y agoThat can be said of lots of stuff. Developers can be marketed to just like anyone else, and cargo culting is very common. "You don't use CloudFlare? Are you enterprise?" Amazon is also adept at this. Many of their database and storage services are great but EC2 is overpriced and they overcharge for bandwidth. I see loads of people who only use them for compute and who would be much better served by Digital Ocean or Vultr. But you're not a serious deployment if you don't over-provision on Amazon... and then put the whole thing behind CloudFlare. Go to a dev or IT conference and you can see this marketing in full force. The style of it reminds me a lot of performance automotive marketing that you would see around a Nascar event.
- anexprogrammer 10y agoIt just gets in the way for users these days. The periodic pre-load "checking your browser" delay, and the absolutely infuriating, and almost constant, captcha makes it a positively user hostile service. I won't use the net from public wifi without VPN active, which now means cloudflare asks for that captcha for every site in its control, and re-asks every 30 minutes. A year ago it was rare for the captcha to pop up, now it's near permanent. Most of the time now I'll just go elsewhere.
- yoo1I 10y agoAnd let's not forget their laissez-fair approach to abuse reports, which they generally answer with > We are a reverse proxy, we are not responsible disregarding any evidence that spamming/DOS/malware/phishing operations are protected by their rproxy services (essentially hiding the actual hoster, which prevents sending abuse reports there) and enabled by their providing authoritative DNS and TLS certificates. They do this pretending anything that comes from their network is not their responsibility, while at the same time giving tor users a hard time. Thanks CloudFlare!
- beardog 10y agoThey do not target Tor users directly (although since Tor is a country code there is an off-by-default option to block/annoy all Tor users), they merely target any IP that is associated with malicious traffic, which is what many Tor exit nodes are. (I do agree that they should make it easier to send abuse reports to the real owner, however)
- rando289 10y agoKind of funny that they are the middle man for traffic on behalf of website distributors, and they are not helpful when it comes to serving malicious traffic, and tor is the biggest middle man for traffic on behalf of website users, and they are very punishing to tor users because of malicious traffic. So by their example, we should be unforgiving and unfriendly to cloudflare.
- mgalka 10y agoCompletely agree. It actually made my site slower, killed many speed optimization I had implemented.
- bckygldstn 10y agoPrevious discussion, with comments from the author: https://news.ycombinator.com/item?id=12096321 https://news.ycombinator.com/item?id=12096321
- cm2187 10y agoOne reason I know CloudFlare is increasingly used is that I am too often welcomed with a CloudFlare page when I expected to see the site. I am not convinced this is good UX.
- _Understated_ 10y agoIt's horrific UX. I use a VPN and I constantly get hit with the cloudflare page and a lot of the sites I see it on are small, amateur sites or personal sites that just need a Wordpress page. They don't need Cloudflare. Getting bloody sick of this new centralization of the web. It's a worrying new trend that the very nature of how the Internet works is being reshaped and controlled by a handful of entities.
- Sylos 10y agoHere's a fun game for the family: Search for "cheesecake" in your search engine of choice and then count how many links you have to check before you find a webpage which does not connect to one of: Google, CloudFlare, Akamai, Amazon, Facebook, Twitter For me, it was 34 links. And that 34th link was the Wikipedia-article for cheesecake...
- _Understated_ 10y ago^ My point exactly. There are a handful of entities that now control the flow of the Internet's information and that worries me deeply.
- viraptor 10y agoCloudflare has multiple uses. You may want it for their dos protection for example. In that case it doesn't matter if it's small WordPress site or something else.
- detaro 10y agoOn the other hand, how often do pages that suddenly become popular get hugged to death, because they are just a small Wordpress page on a VPS or shared hosting somewhere? Throwing a CDN in front to catch these traffic spikes can do a lot.
- manigandham 10y agoThis whole post is ridiculous and comes off as some personal attack without much technical merit: - Every big network company is at the mercy of government. Not sure what the point is here... so we should ban all big companies? Everyone from the ISP to the website host to the network equipment manufacturer can and might be compromised. - Every CDN today is a reverse proxy and MITM is what they do. That's just how it fundamentally works. No magical way around this. - CF supports websockets now in addition to HTTP(S) for every plan. If you need more protocol support than use a service specialized for that, CF clearly states that they don't focus on mail or game servers. - Who cares if they do mitigation? What I want is my origin to be protected, that's it. If they soak it up with network capacity or have advanced processes doesn't matter to me. - Free plans are free, so they have every right to kick you off if you consume too many resources and are getting DDOS'ed all the time. Pro plans also get plenty of protection, you have to be seriously under attack to have them contact you about it. And in that case, 200/month is probably one of the cheapest options considering most other hosts (like AWS) will be happy to bill you like crazy or just cant even handle it. - The "under attack" option is supposed to pose problems, because you're under attack. It's pretty clear that it's not the normal mode of operation. Don't turn this on unless you really need it. - Not sure what the issue is with having to whitelist bots with them. A whitelist approach is far better than trying to maintain an infinite blacklist. Also they are more advanced than simple IP filters, that approach stopped working a decade ago. - Connectivity is not good, even in much of the western world, and varies widely between location, device, capacity, etc. Latency is a real physical limitation that can only be overcome by being closer to users. Try browsing a site in another continent that's not using a CDN and see what happens. Also CF is a CDN, not sure how "use a CDN" was an answer to this. The only real criticism is their Flexible SSL option that doesn't encrypt the connection to the origin and this has been debated endlessly. I think their recent announcement of free origin certs are a way to improve this but ultimately it's a potential security risk and up to the website operator to understand. We use CF because they provide DNS, CDN, SSL, free bandwidth, DDOS protection and better features than others for a single flat price. It works really well for us but it's about understanding how it really works and the trade-offs. If this doesn't work for you and your security or business needs, then use something else.
- joepie91_ 10y ago
- benevol 10y agoFrom an admin standpoint, the SSL/MITM security issue is just huge. From a user perspective, I just don't visit sites anymore that force me to solve a stupid captcha. And I also hate the fact that I am additionally forced to submit to being tracked by Google (via the captcha).
- deleted 10y ago[deleted]
- Veratyr 10y agoOhhh boy. > Single-homed bandwidth can be gotten for $0.35/TB, DDoS mitigation services are plentiful and sometimes even provided by default, and the web is generally Fast Enough. This only works when you're buying _a lot_ of bandwidth or you're buying cheap bandwidth (which usually has sub-standard routing). If you host your app servers on a standard cloud like AWS you're paying dollars per TB (but you're on a damn good network). DDoS mitigation services in many cases consist primarily of "we'll blackhole your IP if one happens". DDoS mitigation services that are affordable and leave your site running are costly. The web is _maybe_ generally Fast Enough when you're lucky to be on an ISP and network connection that gives you a decent path to wherever your content is hosted but that's not a given, particularly these days when the majority of most services' users are mobile, users are increasingly geographically distributed and consumer ISPs are increasingly hostile towards service providers (e.g. if your transit was through Cogent, Comcast's Netflix dispute may have interfered). > Essentially, there's not really a reason to use CloudFlare anymore, and the majority of sites won't see any real benefit from it at all. I'll go into the alternatives further down the article, but I want to address some of the problems that CloudFlare introduces first. You haven't provided nearly enough evidence to backup this statement. > Encryption Yes, like any CDN, CloudFlare needs to have access to your content in order to cache it. Like any CDN, if the connection between the edge nodes and your own servers is not secure, a hostile ISP can do whatever it wants with it. This isn't CloudFlare specific or even CloudFlare universal. This here is a fault in your backend service. CloudFlare offers you the option to encrypt that traffic and you've chosen not to. > In contrast, CloudFlare is just a reverse proxy with a very fast connection. Layer 3/4 attacks (those aimed at the underlying network infrastructure, rather than the application or protocol itself) will only ever reach up to the point where it's handled by a server rather than just passed through, and in a "reverse proxy"-type setup, that server is CloudFlare. They're not actually mitigating anything, it just so happens that they are the other side of the connection and thus "take the hit"! So what you're saying is that a DDoS isn't hitting my servers and my users still get their content? That's called DDoS mitigation. Just because it doesn't work the way you're used to doesn't mean it's not working. > Indeed it is essentially impossible to archive something that's in "I'm Under Attack" mode, despite that usually being the exact moment where archival is necessary! Preventing automated systems from making requests to your site when you're in the middle of a DDoS seems sensible enough. If it's truly necessary (and permitted), contact the site and ask for the IP of the backend. If your work is appreciated, they'll give it to you. As a site operator, if you want to archive my site, I'd rather you contact me. I'll give you my backend IP and hell, might even give you rsync access or something. Archiving through a browser is the least desirable way to have my stuff archived. > In most of the Western world, connectivity is pretty good. You can go from most places in the US to Europe and back - across the ocean! - in about 140 milliseconds. A commonly used metric in the web development industry is that your page and all your assets should be loaded in under 300 milliseconds. I'm located in Silicon Valley and a ping to Germany takes 172ms, a ping to Canada takes 90, a ping to Amsterdam takes 154 and so on. A ping to San Jose where my nearest CloudFlare/Akamai/everything POP is located takes 14ms. > Assuming you're declaring all the assets on your page directly, that would make it two roundtrips totalling about 280 milliseconds, since the assets can be retrieved in parallel. This is incredibly optimistic. Open up the Network tab in Chrome's dev tools and open Amazon, Facebook, even a WordPress blog sometime. Hell, HN's front page barely loads that fast. > CloudFlare can't cache the actual pageloads locally, because they are dynamic and different for everybody. This depends entirely on the content of the page. Not all content is dynamic. Blogs and news sites for example are largely static. Further, CloudFlare can cache the static _parts_ of the page and send only the dynamic content: https://blog.cloudflare.com/cacheing-the-uncacheable-cloudflares-railgun-73454/ https://blog.cloudflare.com/cacheing-the-uncacheable-cloudfl... > So why not just use a CDN? Using a CDN means you can still optimize your asset loading, but you don't have to forward all your pageloads through CloudFlare. Static assets are much less sensitive, from a privacy perspective. CloudFlare is a CDN. Why not use CloudFlare as a CDN for your static assets? CloudFlare isn't making you turn it on for all your domains. You can totally turn CloudFlare on for static.mysite.com and leave mysite.com on your own server. > And this is the problem with CloudFlare in general - you can't usually make things faster by routing connections through somewhere, because you're adding an extra location for the traffic to travel to, before reaching the origin server. This is the same for every CDN and like every CDN, you're relying on the CDN's internal network to get somewhere faster than your own would, and for the CDN's cache to eliminate the need even to do the round trip. If the content is already in Asia, the CDN doesn't need to make the request back to the origin at all. That eliminates entire intercontinental round trips and that's massive. > Unfortunately, all of these issues together mean that CloudFlare is essentially breaking the open web. Extreme centralization, breaking the trust model of SSL/TLS, a misguided IP blocking strategy, requiring specific technologies like JavaScript to be able to access sites, and so on. None of this benefits anybody but CloudFlare and its partners. No, you have opinions biased by (valid but not universal) philosophies and concerns. These features are desired and beneficial to many people. This is way too much text for me so I'll stop here. TL;DR: This article mainly complains about things that are common to every CDN, while demonising CloudFlare specifically for unknown reasons. The rest is mainly complaints about Under Attack Mode.
- 0xmohit 10y agoCloudflare "make web properties faster and safer". Such statements are amusing at best. Seems analogous to an advertisement of a chocolate drink claiming to turn morons into Einsteins.
- chungy 10y agoCloudFlare is basically making much of the web unusable over Tor. That's my main beef against them.
- manigandham 10y agoThey're trying to fix this: https://blog.cloudflare.com/the-trouble-with-tor/ https://blog.cloudflare.com/the-trouble-with-tor/
- 0xmohit 10y agoResponse from Tor: https://blog.torproject.org/blog/trouble-cloudflare https://blog.torproject.org/blog/trouble-cloudflare
- nikcub 10y ago> you can't protect the rest of your infrastructure (mailservers, chat servers, gameservers, and so on) That leads to my technique in discovering origin servers when pen testing CloudFlare customers: brute force all the DNS names and record types, map out all the blocks, scan them for open ports, ID the web server ports, attempt to find the vhosts on those ports in requests with the hosts header You'll almost always find the origin web server (sans protection) and also dev/staging instances of apps.
- manigandham 10y agoThis only works if there are any DNS names that aren't proxied... we don't have any exposed so there would be nothing for you to find.
- ZoF 10y agoOf course, but that's his point. Most of the time people don't go through the effort of putting their mailservers/nameservers/etc. behind a proxy. I'm pretty comfortable guessing that 95% of CPanel/Plesk users that use cloudflare(or another CDN) _and_ host their own mail/name-servers don't put the latter behind a proxy; and they often are on the same box as the webserver. Edit: Which is to say that this doesn't effect someone doing it 'right', but almost everyone is sloppy(most people just don't care as they're not actively being DDOS'd). In reality even using this to find the webserver they will eventually get wise to how you're finding the IP(likely) and swap to a new one(depending on their hosting situation) this time putting all other DNS resources 'behind proxies'.
- manigandham 10y ago> Most of the time people don't go through the effort If people don't put in the effort for the security they need, then they won't have that security. This applies to any concept and I dont see how this has anything to do with a single vendor who just provides the tools and service.
- 10y ago
- iRobbery 10y agoNice read, I couldn't agree more, though a paragraph about their lack of responsibility when they proxy malicious crap via their network would have been appropriate too. So often have i send complaints where they are part of serving malicious content and they send you some copy paste reply 'we are not hosting the content' while they could easily do something about it, by for example stop proxying that crap. And their HN posts annoy me too, now that is just my problem, but for some reason they almost always seem to get posted twice..
- SShrike 10y agoLooks like I'll have to actually get around to properly setting up SSL on my website after reading this, only used CloudFlare because I was lazy.
- daenney 10y agoI'm a bit disappointed that for all the "oh no they break TLS, oh securitay" in the article the author ends up recommending using Caddy. It's written in Go using Go's TLS implementation, which is only a partial implementation of TLS 1.2, of which the authors themselves have said it's not been thoroughly reviewed, there's a few known attacks against it and it shouldn't be used for things exposed to the world wide west.
- jpgvm 10y agoOut of curiosity do you have examples of known attacks against the Go TLS stack? I am going to go have a look myself but would appreciate the head start. Edit: I found these but they don't seem super terrible and are fixed in the versions of Go most people are using: https://www.cvedetails.com/vulnerability-list/vendor_id-14185/Golang.html https://www.cvedetails.com/vulnerability-list/vendor_id-1418...
- daenney 10y agoNo, I do not. Unfortunately that's no guarantee they're not around though :(. All the data on this is extremely old and no one seems to recently have done a deep-dive into Go's TLS stack. I really hope someone will (or that Google will fund the research themselves). It would be beneficial to the ecosystem to have a thoroughly reviewed implementation and a clear understanding of what the state is. Right now all I can go on is a statement of the author about 3 years ago, around the time of Go 1.2: Cryptography is notoriously easy to botch in subtle and surprising ways and I’m only human. I don’t feel that I can warrant that Go’s TLS code is flawless and I wouldn’t want to misrepresent it. There are a couple of places where the code is known to have side-channel issues: the RSA code is blinded but not constant time, elliptic curves other than P-224 are not constant time and the Lucky13 attack might work. I hope to address the latter two in the Go 1.2 timeframe with a constant-time P-256 implementation and AES-GCM. Nobody has stepped forward to do a review of the TLS stack however and I’ve not investigated whether we could get Matasano or the like to do it. That depends on whether Google wishes to fund it. https://blog.golang.org/a-conversation-with-the-go-team https://blog.golang.org/a-conversation-with-the-go-team I've also had a discussion with one of the Caddy developers who recommended for production usage to front it with something that does TLS for you, precisely because no one really seems to know the state of TLS in Go. Arguably other TLS implementations have other issues but there's something to be said for "the devil you know".
- mschuster91 10y agoThe advantage of Cloudflare is, indeed, not protection from bots speaking HTTP. Its main advantage is that it protects you as a site operator from SYN floods, traffic reflection attacks (ohai NTP, DNSoverUDP) and similar attacks. Oh, and it also protects your server from idiots doing portscans.
- tremon 10y agoit also protects your server from idiots doing portscans. Why does your server need protection from that?
- joepie91_ 10y ago> Its main advantage is that it protects you as a site operator from SYN floods, traffic reflection attacks (ohai NTP, DNSoverUDP) and similar attacks. It doesn't. It protects their servers, not yours. This is precisely why "CloudFlare resolvers" are a thing.
- sebcat 10y agoThe plaintext TLS part reminded me of the "SSL added and removed here :v)" slide regarding google's infrastructure
- daxorid 10y agoIn 2011, however, it was pretty much impossible to get working DDoS mitigation for less than $100 a month I would have loved to know who provided this service so cheaply back then. IIRC in 2011, Prolexic and BlackLotus were your only options starting at $5k/mo, and you also had to be large enough to own an ASN because GRE was your only option.
- joepie91_ 10y agoI forgot the name, but it was some reseller of Awknet. They offered DDoS-mitigated hosting services on their own infrastructure. I think GigeNET also had a slightly more expensive offering, but I'm not sure whether that was ever publicly announced.
- jfindley 10y agoWhile I agree with many of the points made, his estimation of the number of round trips is way off. For a start, TLS negotiation requires several round trips before you even start speaking HTTP. Secondly, browsers (depending on vendor, version and number of domains) have a limit to the number of in flight requests. Thirdly, many pages load some assets via javascript execution, which adds another set of round trips. As Cloudflare are very widely peered (I think they are now the most widely peered company), and as such are almost certainly closer to the end user than the origin server. This does really matter when making lots of round trips, which is in practice closer to inevitable (unless you have a small SPDY or HTTP/2 site, which is approximately no one).
- joepie91_ 10y ago> While I agree with many of the points made, his estimation of the number of round trips is way off. It was admittedly a simplified equation, more for illustrative purposes than for argumentative purposes. > For a start, TLS negotiation requires several round trips before you even start speaking HTTP. While true, I'm using just-HTTP as a baseline. There are various techniques for reducing TLS roundtrip time, and it's so heavily dependent on the environment that it doesn't make for a practical baseline. > Secondly, browsers (depending on vendor, version and number of domains) have a limit to the number of in flight requests. Correct. But this is typically solved by bundling assets (on the server side) or increasing that amount (on the client side). On a well-designed site, this should not pose issues. > As Cloudflare are very widely peered (I think they are now the most widely peered company), and as such are almost certainly closer to the end user than the origin server. The point is that the same applies to Anycast CDNs (which CloudFlare is not, really, it's a proxy), but without the privacy issues. CF isn't really a good solution to this.
- giovannibajo1 10y agoI don't think anybody is arguing that Cloudflare provides unique features that can't be obtained otherwise. The point is that CF is VERY convenient to use compared to having to do everything you mentioned through different services and then even some more. With Cloudflare you essentially get distributed DNS, a very fast and universally peered CDN, SSL support, IPv6 support, DNSSEC support, HTTP/2 support, website optimizations like responsive images or JS packing, all essentially with one click and for free, and without having to change a line in your code. And if you hit a DDOS, you swipe your card and you are done. This is their USP. Stating that "you can write code and/or do/configure/buy things so that in the end you can avoid using it" is true, but it's a hard sell for an average business. The only way to avoid the Cloudflare monoculture is that true competitors arise. As much as you can hate it, a reverse proxy seems like what people want for this, and Cloudflare has even developed a workaround for the trust issues (keyless SSL) that competitors could offer to non enterprise costumers. I think there's space in that market.
- lllorddino 10y agoI use Cloudflare because I host my static website on Github. The flexible ssl mode is good enough because there's no user data being passed around only articles of mine. I've used the full ssl mode on self hosted servers and can't see what the dilemma is besides you being paranoid that Cloudflare will tamper with data passing through them. Evidence?
- Sir_Substance 10y ago>and can't see what the dilemma is besides you being paranoid that Cloudflare will tamper with data passing through them. Evidence? Why would you sit and wait for something to go wrong, when you could close a potential security problem now?
- lorenzhs 10y agoGitHub pages does support SSL now, so you can use "Full" SSL mode (not "Full (strict)") with GitHub pages now. We do this for glowing-bear.org, which is just a bunch of static files too.
- joepie91_ 10y agoThen why would you use CloudFlare at all? You already have TLS.
- lorenzhs 10y agoWe want to use a custom domain, but TLS with custom domains isn't possible with github pages. https://glowing-bear.github.io/glowing-bear/ https://glowing-bear.github.io/glowing-bear/ isn't exactly nice to type.
- joepie91_ 10y ago> there's no user data being passed around only articles of mine That's not quite true. The sensitive data that is getting passed around in this case isn't your articles, but who is reading them. > besides you being paranoid that Cloudflare will tamper with data passing through them. Evidence? Why would this require evidence? It's a threat, plain and simple. Threat modeling isn't based on evidence, it's based on assuming the worst-case realistic scenario, because overestimating is less harmful than underestimating.
- chflags 10y ago"... breaks the trust model of SSL/TLS," Certainly some of the encryption one can get via SSL/TLS is worth something. (But then one could use that encryption outside of TLS, too.) And maybe some elements of the protocol are worth something. But on the open internet is the "trust model" really worth anything? It is so ridiculously easy to subvert. Cloudflare does it on a mass scale. But one does not need to be Cloudflare to do it. The "incovenience" of subverting SSL/TLS is minimal. Any website who is delegating their DNS to some third party is potentially vulnerable not to mention any user who is delegating their DNS lookups to a third party. Those are very large numbers. Note I said open internet. I am not referring to internal networks. Also - Question for the author: Was the archiving of dnshistory.org successful? Did they recently shut down and use Cloudflare to block ArchiveTeam?
- jsn 10y agoNot sure I understand what you are saying. If you are saying that "Any website who is delegating their DNS to some third party is potentially vulnerable" to subverting SSL/TLS, then you are absolutely wrong. Malicious DNS can help the attacker to insert her servers between the user and the web service the user is trying to access, but it doesn't subvert TLS/SSL man-in-the-middle protection in any way.
- cherioo 10y agoMalicious DNS can request cert for the domain via e.g. let's encrypt, then it can do whatever it wants.
- jsn 10y agoMy understanding is that it doesn't apply at least to EV certificates. Also, the parent says that "any user who is delegating their DNS lookups to a third party", but that can't apply to such users either.
- joepie91_ 10y ago> But on the open internet is the "trust model" really worth anything? It is. I'd be the first to admit that the CA model is absolutely not a solution that works well overall[1], but regardless of that, it's very hard to get away with a non-targeted attack on TLS (eg. by compromising a CA). Only targeted attacks are really viable, dragnet surveillance is not. The problem with the way CloudFlare breaks the trust model, is that it's broken for everybody - not just high-risk individuals in a targeted attack, but every single person that talks to a site going through CF. It's completely viable to do dragnet surveillance or modification without anybody realizing it, and this makes it a much bigger breach than the CA model. > Any website who is delegating their DNS to some third party is potentially vulnerable not to mention any user who is delegating their DNS lookups to a third party. Those are very large numbers. Not without making a lot of noise. In the context of not having a good way to establish trust for previously unknown entities (Web-of-Trust doesn't really work there), the best we can do - at least, until we find a better solution - is making tampering as public and noisy as possible, so that it becomes risky for a malicious actor to carry out large-scale attacks. Keep in mind that DNS requests are not directly done by clients, but rather through hierarchical caching resolvers - assuming that CAs used something like Google's DNS servers, an attacker on the DNS provider's network would have to spoof the DNS responses to Google, and as such have a very large portion of the internet end up on the wrong DNS record. With the amount of DNS history services and security companies monitoring DNS discrepancies, it'd be pretty much impossible to get away with this quietly. Any attempt at subverting the verification process by changing DNS records would immediately show up everywhere. > Also - Question for the author: Was the archiving of dnshistory.org successful? Did they recently shut down and use Cloudflare to block ArchiveTeam? Unfortunately, our archival effort was interrupted by the operators of dnshistory.org enabling "I'm Under Attack" mode. We did not have enough time to implement the bypass before the service shut down (although it is what caused me to write the bypass code linked from the article). I have to say it was a rather strange case anyway. We'd contacted them well in advance - multiple times, I believe - to ask about obtaining a copy of their data (which would mean we didn't have to scrape their servers), and they'd completely ignored the messages. Only after we'd contacted them to ask about the block, did they reply with a biting message about "causing issues for other users on the site". Why they thought the impending shutdown and removal wouldn't cause issues for their users, I don't know. [1]: http://cryto.net/~joepie91/blog/2015/05/01/on-mozillas-forced-ssl/ http://cryto.net/~joepie91/blog/2015/05/01/on-mozillas-force...
- jguegant 10y agoI almost never used cloudflare. But I really appreciate their blog, it's very a effective advertisement.
- aftbit 10y agoWhere can I get bandwidth for $0.35/TB?
- joepie91_ 10y agoHurricane Electric: https://he.net/ https://he.net/ Seems they're actually down to $0.32/TB now. At least, the price per TB has historically mirrored the per-mbps price (you have to pay for both, separately), so I'm assuming that it's $0.32/TB now as well. Some VPS providers - I can't immediately recall which - will also charge about $0.50/TB without having to pay per mbps at all. That's usually a mix of HE and Cogent.
- james33 10y agoI have to disagree on the CDN point made. We did extensive benchmarks several months ago and found CloudFlare to be the fastest or near the fastest in every metric (and is saving us $100's per month). It works fantastically well as a low-cost CDN, and yes CDN's have a lot of value to a lot of sites. http://goldfirestudios.com/blog/142/Benchmarking-Top-CDN-Providers http://goldfirestudios.com/blog/142/Benchmarking-Top-CDN-Pro...