621 karma · joined April 19, 2017
If you can't comfortably expose your app to the internet, you probably don't have zero trust.
The problem is, "exposed to the internet" is pretty much how most things are today, in a world where everything is trying to be "smart." There is a pathway to most assets and resources and that's what causes breaches. So all services and resources should be assumed as "exposed" until proven otherwise, therefore all infrastructure (and development) should apply zero trust principles.
The tools do different things. Pomerium plays well with Tailscale.
It's a wild time, I'm telling you
All education should aim for this bar
It's actually mildly inspired by Savage 2 from S2Games which I think was just ahead of their time.
I have some ideas on how to seed it with players to avoid the Spellbreak fiasco but that would be part of how I design it and I don't want to write all my ideas out in the wild :)
Basically one player is playing starcraft against 99 players trying to reach the middle of an island. The 99 players are playing first person survival battle royale - their goal is to beat the other players to the middle of the island where there's a throne to ascend and win the game.
The player playing as God gets to bring in environmental spells into the game and can direct a roving band of animals. The God player's goal is to prevent the 99 players from reaching the middle but can only do so in very specific ways that basically come down to herding players together and hoping they fight or dropping supply drops somewhere on the map where players are encouraged to fight over the drop.
There would be a limited amount of servers that players can fight over to become the next "God" of the island. Expanded features would allow players to design their island, yadda yadda.
I've basically been designing it slowly for if I can ever pitch it.
This is pretty sus coming from an AI lol
At first glance, this seems like a very difficult business model to scale, as if it works as described you would be denying yourself insight into what makes a user pay and their behaviors.
It's a work in progress.
https://discuss.pomerium.com/t/this-little-nas-that-could/80
- Kubernetes Ingress Controller: You can now dynamically provision routes from Ingress resources and set policy based on annotations for Kubernetes workflows.
- Desktop App: Power users that need TCP-based services now have an easy-to-use VPN alternative. We’ve created a desktop application to support secure access to non-web traffic protocols such as RDP, SSH, MySQL, Postgres, REDIS, and more!
- Device Identity: One of the core tenants of zero trust is to leverage device identity into policy decisions. Pomerium uses the open standard WebAuthn to bring device-aware policy evaluation into access decisions.
- Pomerium Policy Language (PPL): You can now use a YAML-based notation for creating simple yet flexible authorization policies. It’s now possible to express policy for contextual factors like time-of-day, groups, users, device identity as well as details about the incoming request.
This release also includes other new features, general improvements, and bug fixes. A complete list can be found in the announcement post.
Could you share more with the team and community so we can improve the setup experience for other users going into the future?
Our Slack here! https://slack.pomerium.io/
Or join Discuss and document your thoughts for other users here! https://discuss.pomerium.com/
If someone comes out telling me something will crash but they don't show me they're shorting it, that makes it suspect. My next immediate question is: what's your gain in convincing people that something will crash?
See: Jamie Dimon talking smack while JP Morgan invests in crypto.
Also wouldn't be surprised if Comcast got off scott-free.