Cloudflare One
blog.cloudflare.com
blog.cloudflare.com
Then, instead of taking the big leap, they took an incremental step with WARP, (their VPN), and let consumers bang on it for a year (approx 10mm end users). All along - they've been working towards this vision - which is really comprehensive.
Reminds me of how Amazon destroyed the original IAAS/PAAS providers Loudcloud, etc... not by trying to compete with them, but by doing 1% of what Loudcloud did, but very well, for a lot of people. Then 2%, then 4% ....
Amazing how companies that start off building small "trivial" things can use that to lever themselves up to complex and comprehensive ecosystems.
WARP, Magic Transit, CNI - all of them were precursors to this vision. Which, if they pull it off, is going to be $$$.
Unfortunately, these servers were incredibly prone to griefing particularly DDOS attacks. And though the private server developers were very talented and supremely motivated, they didn't have the resources or infrastructure expertise to mitigate even relatively small DDOS attacks from 1 or 2 nodes.
Who was there as the universal solution to DDOS attacks? Freaking Cloudflare, and it worked, and it was affordable even by teenagers who had at most two nickles to rub together. Where are those ridiculously talented teenagers who built those private servers now? Probably running the world's infrastructure.
To be clear, they do exist and many of them "do their part" (I, personally, spent ~7 years as the senior (technical) person at an ISP and did my best to ensure that neither we nor our customers were ever part of the problem). The "good ones" are, however, seemingly outnumbered by those who simply can't be bothered.
One reason that is often cited is the lack of a financial incentive to "clean up" their networks. At some point, it may be necessary for the rest of the Internet to "provide" them with one. Note that this is one of the reasons that, to this day, spam e-mail is a thing we all still have to deal with.
Unfortunately, especially for all of us "tech" folks (like here on HN), not every problem can be fixed with a technical solution.
Digital Ocean is a weird bird because to me it's more of an educator than a hosting company (but people will of course abuse it the same way). I'd never run prod on it and I usually end up blocking their ASNs, though I feel a little worse about it.
I wish they'd sell technical writing as a service. Their documentation (especially for common tasks that they don't even directly sell, like OpenVPN setups) is superb.
I'm not sure this is fixable for single endpoints: if you want to tell everyone something different, but there are millions coming per second, you're not going to succeed, be it in real life or a webserver.
So the answer seems to be: avoid centralizing too much, and pick existing, DDOS-resistant protocols whenever you can.
(edit) is this like zerotier, tailscale, beyondcorp etc?
The products are designed to be compatible, which is what the name "Cloudflare One" is designed to reflect, but there isn't just one product/feature being offered here. It's more of a vision statement than anything else.
What they're announcing is the compatibility of three previously released features:
1. Cloudflare WARP, their public VPN product for end users https://blog.cloudflare.com/1111-warp-better-vpn/
Note that despite being a "VPN," when WARP launched, it wasn't designed to connect to any company's internal corporate network. WARP is/was a "public VPN," the sort of thing an ordinary user would use to hide their IP address from web sites for privacy reasons. (Cloudflare claimed that WARP would also improve your network performance.)
2. Cloudflare Magic Transit, which is basically a reverse VPN product for on-premise datacenters, providing DDOS protection and packet filtering.
Magic Transit is kinda like Cloudflare's HTTP CDN product, but for all of a datacenter's traffic, geared toward IT professionals.
3. Cloudflare Network Interconnect (CNI), which lets you connect corporate offices to each other over Cloudflare's backbone infrastructure. Like Magic Transit, it was designed to allow IT staff to do traffic management and packet filtering.
Perhaps you'd have thought that these products would work together in some way, but they didn't, and now they kinda do.
Another bit of fluff that may have confused you is that they refer to this as a "Zero Trust" architecture, which sounds a little bit like BeyondCorp. IMO, this is basically a lie. BeyondCorp lets users connect to corporate resources behind a proxy, without a VPN.
If you squint and think of a VPN as a giant proxy, even traditional VPN solutions can seem like "Zero Trust," but that is not at all what anybody meant by that term.
What they are hoping to mitigate is the problem where anybody inside your VPN can access anything else they want inside your VPN, which is how most corporate VPNs work today. That sucks, but they're fixing this with a centralized configurable cloud-based VPN solution, in which you have to trust.
BeyondCorp is about trusting nothing and allowing what is allowed. It's an inversion of being Inside or Outside the network, in that everyone is outside. When they say "without a VPN" what they mean is that you arent connecting to inside the trust and then gaining access to everything.
This product from cloudflare, by integrating with an identity manager, is offering that same kind of deny by default, and allow the allowlist type paradigm. Whether or not it is VPN tech is a bit irrelevant, and misses the point of BeyondCorp. Googles implementation was a proxy by choice, but it's not the only way to accomplish the same idea. I get that you get that, but drawing the beyondcorp/not-beyondcorp line at vpn/proxy is missing the forest for the trees.
I thought this was referring to the combination of Access (identity constraints on connections) and the tunnel system and your app servers only connect outbound to the CDN nodes, forcing all connections to be made through Access. That seems like zero-trust to me, doesn’t it?
This can also be accomplished with rules and micro-segmentation of various types.
Tailscale is a Wireguard configurator and P2P hole puncher with IAM integrations and a nice GUI. Runs at layer 3 so it can't do some things that ZeroTier can do, but most stuff runs over IP so only some segments of the market care.
BeyondCorp is more of a concept. Google has their own implementation of it and so do many others.
I too have trouble wrapping my head around this technically speaking. I get the sense that it's basically something that puts your WAN over Cloudflare's network and lets you do access control everywhere in the cloud, which would make it closer to the now-defunct Pertino or some cloud-backhaul-based SD-WAN solutions... but that's probably only a part of it. "One" here seems to refer to "one" bundle of a whole bunch of things.
Access denied
This website is using a security service to protect itself from online attacks.
Ray ID: 5e1522cb6c3cd1c3
Timestamp: 2020-10-13 01:02:34 UTCIt's a bit of a messy space for a couple reasons. Every vendor who made any one of these products is quickly racing to become a kitchen sink through development and/or acquisition. At the same time, they are splitting up what was once bundled into components you can buy separately to piece into a larger puzzle. Because most companies already have relationships with multiple vendors providing these services, they are fighting each other to both create walled gardens AND SIMULTANEOUSLY interoperable compatible components for larger multi vendor buildouts. (Palo Alto buying CloudGenix SD-WAN, while at the same time being the leading supplier of on Edge firewall VM's for Velocloud devices. Velocloud will both tell you you can run Palo Alto, ZScaler, or Checkpoint, but also that they have in house Carbon Black. What risk are you taking by integrating two vendors that are both trying to crush each other, despite the best in breed solution being part of each of their products.) "We have Cisco for this, so maybe Duo makes sense, but then that overlaps Okta, and that overlaps what we already get from Microsoft, which overlaps what we get from VMWare, which is starting to overlap what we have from Palo Alto.
https://www.sdxcentral.com/articles/news/sase-acquisitions-d...
Anyone in the "Zero Trust" space is likely rebranding bundles as SASE. https://telegra.ph/ZeroTrust-Vendors-04-23
On the topic of Cloudflare. They have a leg up over EVERYBODY because they are building on top of Wireguard, and everybody else is stuck with legacy IPSEC that they cant leave anytime soon. From a future proofing perspective, if you don't already have commitments elsewhere, this is likely a VERY ATTRACTIVE bundle. One of the killer products buried in this is Cloudflare for Teams Access. No more need for AnyConnect. And like I said, most/all the other ZeroTrust Access gateways either a) only come in a bundle with other products 2) are a me-too product offered by a vendor that specializes in something else 3) are ipsec. https://www.cloudflare.com/teams/access/
I feel the same way about Cloudflare as I did about Velocloud. When Velocloud came out, their pitch was that they WERENT "WAN optimization." They purposely werent compressing the data on the edge to squeeze a couple extra bytes down a tiny pile. By starting from the ground up, and not transforming a legacy product, they kept their hardware costs down. They didnt need the extra horsepower to do things that werent necessary in a modern paradigm. Instead they offered a unique cloud service that made their product a bit different than the rest, and at a lower price.
Cloudflare here has that same competitive advantage of being able to design everything from first principal, with no regard for how things were before. Maybe even moreso.
This is nothing new and during the dot-com boom I think the naming nonsense spread to websites, in addtion to software. Software people have been obsessed with wacky names as long as I can remember.
I find this so repulsive and unworkable (e.g., name conflicts, needless keystrokes) that on personal computers I actually name programs I write for myself using an alpha prefix and a numerical suffix. For quick reference I keep a separate index of what each program does. Every program has a unique, sequential number in its name. Every name has the same number of characters.
As always: if I do everything in accordance with the way Cloudflare says, and my company suffers a loss due to Cloudflare screwing up, to what extent is Cloudflare liable?
The usual answer is "for a month of what you paid them, or maybe a year, but certainly not anything more". This situation is not unique to Cloudflare.
The real answer is always "What does your contract with Cloudflare say? What does your insurance policy say?"
It's worrisome that Cloudflare has a DNS provider, a domain registrar, a certificate authority, and a Border Gateway Protocol system. They can redirect traffic of any site to Cloudflare, generate a fake TLS cert that decrypts the traffic, observe or modify the traffic, and send it on to the destination site. Worse, they could be ordered to do this by a government.
What could possibly go wrong?
https://community.letsencrypt.org/t/using-bgp-to-acquire-bog...
When you get your hands on a significant portion of world's traffic, you start feeling a temptation to pivot to a data company, like Google of FB. That's the danger I hope they will avoid as well.
I remember when they offered text obfuscation protection service (i.e. hiding emails unless you click on them). It was literally ceasar cypher encoded text with the N argument right there next to it.
I'm sure they are much beyond that now but I find your blind trust and assumption rather hilarious.
Anyway, I wasn't aware about that case, do you have a link to learn more?
official docs: https://support.cloudflare.com/hc/en-us/articles/200170016-W...
Assuming keys vary [pseudo-]randomly, even the Caesar cipher is a viable protection in this particular case (mass e-mail harvesting).
The only thing email harvester would need is awareness of this and few lines of code. The field even clearly identifies itself!
Source: I wrote a generic web-scraper for these emails several years ago :D
Like recently, when a single BGP configuration mistake brought down their entire backbone?
If I want to run a livestream for church, why do I have to send the packets all the way to Google's servers in California just so it can be on YouTube? I wish Cloudflare could host that right here in the same city. That's where most people are watching from anyway.
Or what about social networking? I'll continue to use Facebook to keep in touch with friends in other places, but the majority of my social life is with people nearby. I don't see why the messages sent from me to a friend in the same city should leave the country.
I don't know if Cloudflare would be willing to do this themselves, but perhaps there's a space for new startups in edge hosting, not just edge caching. Cloudflare's expansion could be good for privacy, so I support them - for now.
They have data centers all over the world just like Cloudflare does.
Just like with mobile, we have happily traded security, privacy, and control for convenience. Privacy, security, and openness advocates keep failing to understand this because they fail to grasp just how massively valuable convenience is in a time-impoverished overly-complex world.
Oh, and we'll call it "Flexible SSL" so it doesn't sound so horrendously insecure...
Even the encryption: "full" setting is useless, since it doesn't verify certificates in any way, so an MITM attacker can just sign their own cert in your name.
I suspect CF does this so they can have their "one-click" on boarding for panicking under-attack companies. It really shows that despite all the blog posts about lava lamps and how important security is for them, in the end sales and the shareholder's interest (profit) is king. The very least they should do is have huge warnings about switching to "full (strict)" asap, but really the other two shouldn't be an option at all.
I'm reminded of this whenever I add a new site to CF, since when port 80 is not open, CF just does not work at all, it just shows "backend server down", even when TLS/443 is set up correctly.
And arguing that "it's fine because it protects the connection between the user and the CF server which is the most vulnerable point" is ridiculous. Your nearest CF server is probably in a neighboring city, so the whole path between that city and the other side of the world is readable and modifiable by whoever.
Off topic: I posted an off topic comment on one such announcement a few months ago asking why new domain registrations were still not open (only transfers are allowed), and got a reply about squatters being a problem, which I didn’t really understand because that could be the case even with domain transfers (in my understanding). I posted a follow up [1], but apparently that wasn’t seen. So I’m linking it here again for visibility if @eastdakota or @jgrahamc or someone else at Cloudflare can respond.
E: ah sorry, I must be a randomly selected tester. I didn't think I'd be in any sort of early bird group as I'm a complete Cloudflare freeloader besides domains at the moment
[1]: https://support.cloudflare.com/hc/en-us/articles/36001991067...
0: https://blog.cloudflare.com/introducing-cloudflare-access/
- Apple One
- Fitbit One
- Google One
- HTC One
- Motorola One
- Sonos One
- SpaceShipOne
- Xbox One
Then sinofsky started chanting "one windows."
Then xbox one happened. The rest followed suit
- Ubuntu One
Have we even reached peak One yet? I had thought so a few years ago but it seems to be constantly getting worse.
Name Ideas:
Cloudflare Zero
Cloudflare Connect
Cloudflare Trust
Cloudflare Assist
You can have those for free, just maybe consider opening a fullstack role in SF :)
One as a name addon originates in NY graffiti scene of the 70s, adding a written "One" is still popular among graffiti writers or true-school rappers.
[0] https://www.youtube.com/watch?v=KOO5S4vxi0o&feature=youtu.be
There's something about "One" that signals a complete lack of creativity.
Smart
Power
Turbo
Next
Dyna
Electric
Sure I'm forgetting some ...Instead, it's a solution to tie together IT identity services and other bits and pieces for more secure corporate SaaS I guess.
So, Cloudflare PMs are active on news.yc? They've seemed to cloned two of the best consumer (and enterprise) networking products to have launched on news.yc in the past two years:
https://nextdns.io -> https://www.cloudflare.com/teams-gateway/
https://tailscale.com -> https://blog.cloudflare.com/introducing-cloudflare-one/ (for some reason, these are left unused: one.cloudflare.com and cloudflare.com/one)
Tailscale is ergonomic tunnel management//authentication. Which in itself is a great product, but it's not nearly as granular. Being able to restrict access based on identity provider, individual, etc is a must for a corporate solution.
One of Tailscale's selling points is the data isn't routed through their servers, just between peers. That's the opposite of Cloudflare; their value proposition is centralized granular control, no plumbing, just plug'n play.
Can you point to something more?
Is the browser isolation product a "modern web proxy" that presents say, a social media management site (like Tweetdeck) or an internal app via a rewritten URL, rewriting the HTML, JS, and HTTP headers to hide authentication from the user?
If so - wow, to get that to work performantly requires deep understanding at all levels of the HTTP stack. I had a web proxy written in Haskell some years back that implemented online, nested HTML and JS rewriting and injection, and I was so close to getting modern web apps like Facebook and Gmail to render perfectly. Server side rendered sites were feature complete, but sites using a virtual DOM required care to proxy out DOM builtins like createElement and setting attributes, and that surface area is quite large.
For sites using chunked transfer encoding, it worked on a chunk-by-chunk basis, as opposed to blocking until the entire document had been transferred to the proxy. The additional latency was just the time to parse a chunk. Orders of magnitude better perf than any of the web proxies that many of us on HN used as kids to subvert school network restrictions, and much better compatibility.
It's a little sad my project never saw a release, but I would be very excited to see a company ship something very similar or even better.
> S2 Systems NVR technology intercepts the remote Chromium browser’s Skia draw commands, tokenizes and compresses them, then encrypts and transmits them across the wire to any HTML5 compliant web browser (Chrome, Firefox, Safari, etc.)
[0] https://blog.cloudflare.com/cloudflare-and-remote-browser-is...
I wonder how that impacts accessibility, screen readers and ARIA. If they're rendering a Canvas element as a framebuffer, I have to imagine they've lost support.
Also I got really confused by "Google Workspaces". Turned out it's just gsuite re branded. So typically Google!
My opinion is that, in its current form, tailscale essentially provides a cross-platform super-configurable discovery and key-management layer to a P2P network overlay on top of the public internet, secured by Wireguard.
It's like stunnel or ghosttunnel but for L3, and that let's you replace the gargantuan IPSec with something that's way simpler and nimbler like wireguard.
As for LAN vs BeyondCorp... tailscale has BeyondCorp influences. It uses federated identity (OpenID for instance) and device credentials (see: wireguard crypto-routing) to let you in on any mesh network that you have access to be [on]. It is not something novel but super complicated to do it as simply as possible. And wireguard is a key enabler for just that.
BeyondCorp is obviously much more than just SSO. You might also be interested in: https://www.beyondcorp.com/
They keep saying it all as if centralizing the internet around a single point of failure and letting it also see unencrypted data of millions of websites is a good thing. Maybe I'm too old, but I'm just not having it. That's not at all how the internet is supposed to work.
It's more helpful to ask yourself why people use it instead of just harping on the downsides.
Anyone planning to implement any kind of open or federated system today needs to take note of this and bake in mitigations against it from the very first line of code.
Can someone please elaborate on this metaphor? I don't quite get it in context.
The difference is that we don't issue that identity. We aren't an identity provider, like Okta or Azure AD. Instead, teams integrate our Access product with their identity provider which tells us which sources of identity to trust (in the same way a bouncer or border guard doesn't create your identity card for you, but they know what a valid one looks like).
How big will they get? Do they have any competition?