ockam

May I suggest a tool built for application level portals instead? https://github.com/build-trust/ockam One binary, easy to use, no ssh getting stuck! (yep, I work at Ockam :)

disclosure: I work at Ockam. The Portals for Mac app is an example of the type of thing you could build using the open source stack of protocols. The README (linked by parent) links out to all of the relevant parts of the protocol documentation to explain how these work together. The NAT Traversal (https://github.com/build-trust/ockam/blob/develop/examples/a...) part of the README is probably the best explanation of why the free relay you get via Ockam Orchestrator is a useful part of this demo. As for why would anyone trust this: The protocols are designed so you absolutely don't have to trust the relay. Trust is pushed out to the edges that you control and so you're not susceptible to a MITM attack if something like a relay is compromised. The protocol design for all of this is open and documented, and was independently audited by (IMO)

Another free + open source alt (for Mac) https://github.com/build-trust/ockam/blob/develop/examples/a...

We’ve been working on something (https://github.com/build-trust/ockam) that enables exactly this, among a whole host of other use cases. If you check out some of the code examples in the docs you’ll see how to setup a tunnel using the CLI. For other use cases there’s also the programming libraries (only Rust atm, though I was spiking a TypeScript/Node PoC this week) which might provide more flexibility. Personally I’m excited by the idea of being able to move this kind of secure by design connectivity all the way into the application layer though.

Disclosure: I work at Ockam. What you describe here sounds a lot like what we’ve been building at Ockam: https://github.com/build-trust/ockam

Ockam https://github.com/build-trust/ockam

would you like to schedule some time with us to dig into this further. This sounds really interesting and pretty close to things we've seen others do before. To move this off of HN and to a channel that we look at more regularly, I'd like to suggest a couple alts: 1) GitHub Discussions: https://github.com/build-trust/ockam/discussions/categories/... 2) We can schedule a zoom call: https://www.ockam.io/contact/form

Key/Route Discovery, Credential Issuance/Presentation, Secure Channel Handshakes and Message Routing that is decoupled from transport protocols have been our main focus. We chose to build the more reliable e2ee strategy first - Relays. UDP hole puncturing is in development right now. However there is extensive research that proves it in only successful in making connections in 60 to 80% of real world networks. This is why Signal does relays for example. Relays provide a highly reliable strategy. So we knew we'll want to support both and give devs and option to choose what is right for their application. Or failover from one to the other. In addition, relays also allow store and forward and integration to other enterprise systems like Kafka. This is how we're able to to move end-to-end encrypted data through Kafka https://github.com/build-

Thanks for trying out the examples: 1. No benchmarks yet. We'd welcome contributions & research in that area. 2. Here's an example of using the TCP transport without using an Inlet / Outlet. https://github.com/build-trust/ockam/blob/develop/documentat... Give it a try. Would love to know if that fits what you're going for.

A hands-on example, try it: https://github.com/ockam-network/ockam/tree/develop/integrat...