Hypothetically.
1 karma · joined March 4, 2021
Hypothetically.
Even just seeing a few variables or objects passed around, I still don't know exactly what it's doing, or hiding. I can more quickly understand the high level idea with the former example without the details potentially confusing me.
Turtles.
- Often if you use a central database such as Active Directory for your internal users, you may need to set up your OAuth endpoint (say, an AWS Cognito User Pool) and then have an AD admin allow that user pool to be a relying party. This means there is some lag time to setting this up, and that it isn't done with automation. So if you have an application you want to spin up a custom domain with a temporary user pool, test something, and then destroy it later, it's probably not going to work without some custom workarounds. No need for this with a traditional VPN.
- If you have 50 different apps, with 50 different URLs, you're going to need to do the above 50 times. Also have 50 staging and dev portals? Same deal. Now try managing changes to all of those at once. The manual steps, plus all the integration with all the product teams, now means this whole thing is becoming burdensome. This is a lot more work than just "use this VPN client and whitelist these CIDRs".
- If you're working for one of those weird companies that loves to do split-horizon DNS with lots of custom internal-only domains, guess what? Probably not gonna work without a VPN.
- Onboarding can be complicated. You now need to help your users manage their accounts, such as password resets, being a part of different domains, using a supported device, MFA registration, troubleshooting internet connections, using a supported CLI tool for non-web-interface APIs, etc. Versus just saying "are you connected to the VPN?".
- A VPN allows a central network team to manage access control across the entire network (or wherever that network team manages networks). BeyondCorp needs to be managed for all of your products by one team, or you may end up with an uneven and difficult process of supporting users across teams. A lot of companies (maybe most) are just not set up to allow independent product teams to manage internal user access. Even then, authorization maybe, not probably not both AuthN + Z.
- If you have a single domain serving multiple apps in multiple URLs requiring different authorization, things can get more complex.
Ultimately I think most of the protocols used for BeyondCorp today have too many drawbacks to say we could all drop our VPNs in support of it. We'll probably need at least another generation of protocols and management workflows in order for it to become the new norm.
1. It's the exception, not the rule. Most of the time there aren't collaborative solutions. Most of the time people work in their silos and make something work for themselves. Often it's corporate-funded, and those corporations have no consideration for others being able to pick up the work once they've abandoned it. The fact that there's 10 of the same thing to integrate is proof enough. It's just gotten so ridiculous that somebody finally had to address it. Turns out it's a company that has to deal with all of those implementations anyway.
2. This is one tool figuring out how a bunch of other tools can integrate into it. It's like what I'm proposing, if you assume the least work possible to achieve maximum laziness for your own specific tool and use case.
Their solution wasn't "hey, it looks like a lot of things use secrets. maybe it'd be cool if we made one way for any system with secrets to interoperate with any other system, and try to get it adopted by existing vendors." Their solution was "hey, we just need to get all these other things to work for the one tool we're using." Rather than "how can we make this more composable, more compatible, easier to implement, for everybody... even if they're not using our tool...", it became "how can we make this easier for just us?"
That's what is always happening, has always been happening, in this space, for nearly 10 years. Either everybody latches their custom tech onto a single platform and no real open source solutions get made, or everybody spits out incompatible, overbuilt, underthought, opinionated solutions for their own problem. We don't build standard solutions in the cloud world, we build log cabins.
I mean, just read the PR. They're talking about coding into this 'standard' support for each different implementation. Like "this is a vault secret, and this is a gsm secret." That's the opposite of what I want. I want it to say, "this is what a secret looks like. now you figure out how to use it.", or, "give me your secret. I don't care who or what you are, because we all speak the same secret language." That is what an internet standard is supposed to be. Not "this is a bind9 DNS record, this is an AD DNS record, this is a RedHat DNS record, this is a Route53 DNS record".
The "container landscape" shouldn't remotely resemble what it does today. The idea of a "container" should have been standardized in an agnostic way, without requiring all the (admittedly useful, but also completely unnecessary, and often burdensome) features Docker threw into their tool. Yes, many people's lives were made easier. But a whole lot of other lives were made harder, to the point of small economies built out of badly re-implementing and custom-integrating into one precious and incompatible concept.
I would call Kubernetes the open source Active Directory, but Active Directory is literally ten times more standards compliant.
Instead, the standard solution today is custom integration, which leads to a lot of reinventing the wheel and incompatibility with extremely similar products.
I think the more companies rely on technology, the more screwed they are, because they don't realize how much harder it is to run a business dependent on technology. The fact that SRE exists proves that, I think. The system is by default a garbage fire, because by default you can't push back on product in order to fix your tech debt. Most other businesses seem to grasp the concept that they need to perform maintenance on their machines or they won't be in business for long, but as soon as it's "the magical box with the 0s and 1s inside", they pretend it doesn't require long term investment or a different strategy.
Let's not lie to ourselves. It's the option you prefer, not the only viable one.
It's also a lie to pretend that Google is any more evil than DDG. Both are capitalist corporations marketing a story to convince people to give them money (in this case, to convince you to make money for them). Neither of these organizations have morals, they have profit margins and consumer strategies. "Privacy" is just the tech equivalent of "Organic", a marketing tool to convince you to choose their brand. Eventually Google will get on the "privacy train" and people will completely forget they were "evil", just like with Microsoft. It's all so much Eurasia versus Eastasia.
But even if it is, you can actually hack the entire system with just a BGP hack. Today, if you issue some false BGP routes, you can MITM LetsEncrypt (or one of the other 329 CAs) to sign a valid cert for you. It's not hard because validation is automated and depends on proving you own IP space... and IP space is just what your router's BGP table says it is at the moment you issue a cert.
I would not depend on the kindness of banks giving back money on very large scales. They care about themselves more than they care about you.
You're right, DNS registrar and nameserver attack is another great attack and usually they're pretty vulnerable, so that's another good option.
There's always a better way. But when you're going up against gigantic incumbents with way more power than everyone else, you don't get the better way. You get the way the powerful decide it will work. It's like politics, or economics. When a system is so large and unwieldy, significant change can't come unless the ridiculously powerful minority forces it. If they have no reason to do so...
Then I learned how much cheaper, modular, and more robust your furniture can be if you invest in some hand tools and built it yourself. You have a higher initial outlay, but the results last longer, can be repaired much easier, as well as broken down and repurposed. Most furniture can be assembled with a cheap hand saw and chisels, or if you're lazy, skilsaw, drill, drill bit set, and screws.
I don't know that i'll ever buy a piece of furniture again unless it's second-hand and deeply discounted. There's so much good shit out there already.
Aside: it seems we've long been able to feed the world (in terms of meeting caloric and nutritional needs) based on American farm capacity alone, it's just that nobody wants to pay for it.
But having people all the same then introduces non-communication problems. Lack of genetic diversity is a potential catastrophe. Lack of outside perspective makes novel thinking difficult. Lack of change breeds complacency.
So you need your software to work pretty much all the same way, but you need diversity in how it works to survive environmental challenges.
Nature has a solution for this (as in most things): evolution. You mutate a bit every so often and eventually something works better. Then you stick with that and repeat. It's a continuous improvement cycle driven by measurably better outcomes from experiments.
This can work for hardware too but it's definitely not as straightforward. But no matter what you use it on, you can't have some clunky, hierarchical, reactive, conservative, single-minded power structure holding the process back. The stack will always suffer as long as there's a giant anchor at the top keeping it from being agile and mutating. It's not so much a cultural thing as an organism; if the organism can't agree on how to grow, it's not gonna fare well against competition.
I have, with OpenShift, several times. The worst one took hours to get it partially back online, days to fully recover. At least I got to have one free drink before I had to leave our holiday party to start fixing it. (Ok, technically it was non-prod; luckily prod was ECS... long story)
> I don’t believe single instance is going to give you better availability when single machine faults happen
Depends on your definition and context of availability. It is possibly the simplest thing to destroy any existing nodes (and in the event that a node can't be destroyed, null-route it and/or disable its network port) and bring up a new node. So single instance is fairly easy to recover. But with multiple nodes, for each function of each instance that is required to reach consensus, the likelihood of consensus failure increases; you actually need more nodes and variety in the cluster to resist consensus failure. Yet ironically, the more nodes you have, the higher the probability of failure. In the end, the real-world reliability of the system is based on additional factors besides the network model.
In a month / year / etc when this thread gets deleted, there'll just be a HN comments section speculating about a missing twitter thread. The least we could do here is ask posters to capture the thread in a blog post along with a summary of points, so it doesn't have to be re-created in the comments here. This is potentially an important post that we want a historical record of, and Twitter is just not built for that.
For most container purposes, host networking and the default process namespace is absolutely fine, and reduces a lot of problems with interacting with containerized apps. 95% of the use case of containers is effectively just a chroot wrapper. If you need more features, this should be optional. This would also make rootless federated containerized apps just work. But nobody wants to go back to incremental features if Docker gives them everything at once.
The last two capitalistic organizations I've worked for, all my co-workers were cheery, friendly, helpful, and enjoyed their jobs. The people frustrated were the ones that did their jobs as good as they could and were frustrated by a lack of excellence in the face of large scale and complexity. I wouldn't call this misery. And one of those companies was literally rated the most hated corporation in America. I've also worked for places were people were lazy, bureaucratic, and did the least work possible to collect their paycheck (heck I was that person). Ultimately corporations are made up of people, and there's all different kinds of people out there, so there's also all different kinds of corporations.
> led by a class of people who are completely unaccountable to anyone but themselves, who therefore have no incentive to make things decent for the workers.
They're accountable to shareholders and government regulatory bodies, and in very rare circumstances, to unions. Certainly there should be more accountability within the organization from the bottom-up, but it's fallacious to think they don't answer to anybody. The actual incentives vary, but usually stem from either competition, or seeking to drive quality and efficiency. Business management is more art than science.
Sometimes NFS is your only option. When you have legacy applications which nobody is going to rewrite, and you need to scale some operations on a set of files over many nodes, NFS works. Its failure nodes are well documented, so you can plan for and work around them.
It's also supported by most vendors as the default networked filesystem. Whether you're using a desktop PC, a million dollar NAS, or cloud storage, it supports NFS.
It's also acceptable when time is of the essence and you just need to get something working now and don't have time to build something better. I rather like "good enough solutions" as a way to get teams "shipping", with an agreed-upon plan to replace it later.
But as someone who's used it for nearly 20 years, internally I start screaming and throwing things whenever someone suggests using it. Externally I propose redesigning for a more efficient solution :)