Anyone have any reservations about Nebula security vs Tailscale?

I’ve got a bit of work experience with Tailscale, though have reservations about it for personal use. In it’s place I’m thinking about GitHub - slackhq/nebula: A scalable overlay networking tool with a focus on performance, simplicity and security

The data plane may be decentralized, but tailscale.com (or your headscale node) being a single point that compromising will in effect compromise the whole network makes me uneasy, since by their nature they also have to be relatively wide open to Internet traffic.

There is taillock which helps a lot, but tailscale still has a number of other features that an attacker might find useful to leverage (perhaps some of these are mitigated by taillock) such as:

  • The network ACLs
  • Routing rules
  • MagicDNS
  • Tailscale SSH
  • Tailscale Funnel

There’s also some potential to collect significant amount of network recon by enabling listing services, amongst whatever metadata tailscale.com can see.

At it’s core I see tailscale’s focus being towards it’s saas platform and commercial customers. That’s a good business model.

Nebula on the other hand I have no experience with, but I think the following is true:

  • There’s no default third party saas involved
  • The public network service (lighthouse) is untrusted by design
  • The single point of compromise is the CA key, however I believe that’s much easier to mitigate against than a network service like tailscale.com or headscale
  • The network ACL configuration is at the discretion of each node (I think?)
  • The cryptography is probably solid, it’s based on the well known noise framework and there’s a reasonable chance Slack has paid for an audit, but I still have more faith in wireguard
  • It’s more work to setup and less userfriendly than tailscale
  • At it’s core it’s a self hosted mesh VPN first, the defined.net company is a spin off
  • It won’t win data transfer benchmarks, but it’ll be fast enough (for me)

Also as a convenience for us Debian users Nebula is also in the official repos.

Now to me as a security conscious fellow I like tailscale, but feel that nebula might be the better choice for my humble home networking needs.

But nebula isn’t very popular at all, I was wondering if I was missing anything.

Then why not simply use WireGuard?
It is not that hard, you only have to setup NAT or IPv6 and DynDNS.

The NAT hole punching, the peer discovery, the easier to write network ACLs (with groups!), the routing taken care of - I’m suspecting is worth the trade off of setting up Nebula (or Tailscale etc).

With n nodes in the mesh, the n^2 possible connections makes management a bit of a PITA.

I’m guessing n will start around 5-10 (phones, PCs, laptops, routers, rpis, adds up fast!), but with new VMs involved might well end up around 20.

The main security disadvantage I think Nebula has today, which Tailscale also shares, is no attempt at post quantum security. Netbird meanwhile has the edge there:
https://docs.netbird.io/how-to/enable-post-quantum-cryptography

This doesn’t weigh much into the decision for me, it’s definitely a feature some would prefer.

Later on I found this to be the case:

Nebula has undergone a paid security vulnerability assessment, along with numerous internal security reviews. We are adding Nebula to our official bug bounty program…
– Introducing Nebula, the open source global overlay network from Slack - Engineering at Slack

For my business, which has team members all over the globe, it was imperative that I chose the best VPN solution. I installed and tested:
Nebula, Tailscale, Headscale, Netbird, Cloudflare WARP, ZeroTier, and Netmaker.

Cloudflare WARP offered the best solution, but we did not use it because you are stuck with Carrier Grade NAT IPs. Long story short, we went back to plain ole’ Wireguard hosted on our OPNsense server.

1 Like

I personally use zerotier with my.zerotier.com

BUT

There is a fairly competent third party webui for self-hosted “controller”

The controller doesnt have to one online 24/7 and it can be behind a NAT/firewall.

It needs to be online only to let the other nodes know that some node is banned from the network, joined network or to push new IPs or “flow rules”.

Plain ole’ wireguard on opnsense server I presume has the opnsense host as the hub that can see all traffic in plaintext.

I may still go down that path, but I like the properties of e2e encrypted mesh overlay networks more.

Zerotier looks like a nice product, but I’m on the FLOSS bandwagon :).