Nebula is pretty great.

However, the Android client does not allow for specifying a DNS server and breaks the Android system DNS over TLS. Google thinks the VPN app/client should handle DNS and Nebula app development seems very slow. This means you cannot use adblocking DNS while using Nebula.

The semi-official (worked on by folks involved with the core product from, as far as I can tell, early on, but not released by Slack like core Nebula is) mobile clients don't have a license associated with them, which is a bit of a blocker to further development or distribution on certain stores (FOSS-only ones, for instance, and really no-one else can distribute them at all right now without risk).

Thankfully both Nebula and Wireguard are built on top of the Noise Framework.

So neither is a compromise security-design wise.

> Thankfully both Nebula and Wireguard are built on top of the Noise Framework.

> So neither is a compromise security-design wise.

Security involves much more than the crypto framework being used; just crypto requires much more than the framework. Noise could be implemented insecurely, as a basic example.

Yeah that’s probably true. But I meant in the sense of it’s not roll your own crypto.

Yes, absolutely. That reduces a lot of likely error.