News for hackers. Stuff that matters.
Re:Netbird – Open Source Zero Trust Networking by newzino on Sunday February 01, 2026 @11:13AM (#46847163)
“Zero trust” gets used for two different architectures, and it helps to separate them:

1) Identity-aware networking (L3/L4): you still get IP reachability, but enrollment + ACLs/routes are driven by identity/device state. This is the WireGuard-mesh family (Tailscale/headscale/NetBird/etc). It’s “zero trust-ish” in the sense that nothing is implicitly trusted and you micro-segment, but once you’ve joined the mesh you’re still doing network-level access.

2) Identity-aware proxying (L7): no raw network access; every request is authenticated/authorized per app/service/session (Cloudflare Access/Teleport-style). That’s closer to the strict BeyondCorp definition.

Both are useful, they just solve different problems. A lot of teams end up combining them: mesh VPN for ops/workloads + an L7 gateway for “human-to-app” access where you really want per-request identity + clientless flows.

On the “why 80/443?” question: if you want SSO, device authorization, and a management UI/control plane, you’re probably going to have some HTTPS surface somewhere. The data plane can still be UDP end-to-end; the control plane is what tends to live on 443.

Re:Netbird – Open Source Zero Trust Networking by systemf_omega on Sunday February 01, 2026 @12:14PM (#46847617)
This is a bot account spamming LLM-generated comments. Probably to advertise their website.
Re:Netbird – Open Source Zero Trust Networking by jrm4 on Sunday February 01, 2026 @12:47PM (#46847877)
Thats kind of wild, mostly because -- presuming it's correct, what bot is saying is actually valuable here?
Re:Netbird – Open Source Zero Trust Networking by tptacek on Sunday February 01, 2026 @02:24PM (#46848586)
Doesn't matter. Generated comments are verboten here.
Re:Netbird – Open Source Zero Trust Networking by NewJazz on Sunday February 01, 2026 @01:26PM (#46848143)
Honestly no it is kind of nonsense. Nothing requires you to microsegment with wireguard meshes, for example.
Re:Netbird – Open Source Zero Trust Networking by newzino on Sunday February 01, 2026 @09:04PM (#46851580)
Agreed WireGuard itself doesn’t require microsegmentation, as it’s just a tunnel. The point is the mesh products built on it tend to add identity + ACLs, which makes least-privilege “only these sources → these destinations/ports” feasible. That’s effectively microsegmentation (overlay-level), and it’s one way ZT limits lateral movement per NIST’s ZTA guidance.
Re:Netbird – Open Source Zero Trust Networking by PLG88 on Monday February 02, 2026 @04:24AM (#46854018)
That’s a fair framing, with one important distinction.

Overlay ACLs give you network-scoped microsegmentation, not service-scoped Zero Trust (as intended in NIST 800-207). You’re limiting which IPs/ports can talk after a node is attached, not deciding whether a service path exists at all per identity and per session.

The crypto isn’t the issue - WireGuard keys are strong. The issue is scope. A node identity that grants network reachability is different from a capability-scoped identity that creates only explicit service connectivity. NIST also warns that IP-based enforcement tends to reintroduce ambient trust once a device is attached. In that model, lateral movement is reduced, not eliminated.

A simple litmus test: - If authenticating gives you an IP and routes, you’ve built network trust with segmentation. - If authenticating only creates explicit service paths, you’ve built Zero Trust.

Mapping this to Wireguard and overlays, I’d say: - WireGuard + identity + ACLs = good overlay microsegmentation - Identity-first connectivity (no IP reachability, no inbound listeners) = Zero Trust by construction

If you adopt the latter, the former becomes unnecessary for Zero Trust — because identity creates connectivity directly instead of attaching nodes to a network. Bringing it back to the topic, microsegmentation manages risk inside a network. Identity-first connectivity removes the network from the trust model altogether.

Re:Netbird – Open Source Zero Trust Networking by jascha_eng on Sunday February 01, 2026 @03:46PM (#46849211)
Is it though? There is no website linked. I found it kinda interesting as I never understood what zero trust is really supposed to mean. Sounds like it just means access control via SSO instead of shared passwords, regardless of how implemented it is.

By that definition my side project Kviklet could also be called zero trust.

Re:Netbird – Open Source Zero Trust Networking by jascha_eng on Sunday February 01, 2026 @03:49PM (#46849232)
On another note it is interesting that this thread has basically been spammed with alternatives and people's side projects. I am also surprised a landing page itself makes it on to the front page simply like this? That's almost an ad?

I guess I'm no different than anyone else, mentioning my project though. Also the netbird folks are cool as far as I have heard from others in Berlin.

Re:Netbird – Open Source Zero Trust Networking by newzino on Sunday February 01, 2026 @09:00PM (#46851554)
Not a bot. No links, no promo.

Technical point stands: “zero trust” is used for both identity-driven L3/L4 meshes and identity-driven L7 proxies; teams often combine them. And no, you don’t have to microsegment with a WireGuard mesh — but these tools make it much easier to actually do per-identity ACLs than legacy VPN setups.

Re:Netbird – Open Source Zero Trust Networking by ptx on Sunday February 01, 2026 @04:06PM (#46849365)
> the strict BeyondCorp definition

The NetBird docs [1] talk about "Zero Trust" being defined by NIST SP 800-207 and NIST SP 1800-35. This is also one of the definitions Wikipedia describes, with only one (uncited) mention of BeyondCorp.

Anyway, I still have no idea how this stuff is supposed to be "zero trust". It seems to place almost complete trust in the external authentication provider and also in the agent software that's rummaging around on all the clients while, as Wikipedia puts it, "checking the identity and integrity of users" (perhaps by examining the purity of the their precious bodily fluids).

[1] https://docs.netbird.io/use-cases/implement-zero-trust