librebyte@lemmy.mlM to LibreByte@lemmy.ml · 4 months agoheadscale - An open source, self-hosted implementation of the Tailscale control server (VPN)github.comexternal-linkmessage-square3linkfedilinkarrow-up116arrow-down10cross-posted to: opensource@programming.devopensource@lemmy.mlopensource@programming.devhackernews@lemmy.bestiver.se
arrow-up116arrow-down1external-linkheadscale - An open source, self-hosted implementation of the Tailscale control server (VPN)github.comlibrebyte@lemmy.mlM to LibreByte@lemmy.ml · 4 months agomessage-square3linkfedilinkcross-posted to: opensource@programming.devopensource@lemmy.mlopensource@programming.devhackernews@lemmy.bestiver.se
minus-squareeleijeep@piefed.sociallinkfedilinkEnglisharrow-up2·4 months ago That’s it. No certificates, no certificate authorities, no HMAC negotiation. Just Curve25519 key pairs and ChaCha20-Poly1305 encryption. Surely an actual human has written an article like this that you could share instead. I enjoyed this blog post about how Tailscale does NAT traversal, which covers the second half of your linked article: https://tailscale.com/blog/how-nat-traversal-works
minus-squareZachariah@lemmy.worldlinkfedilinkarrow-up1·4 months agoThanks, I appreciate the additional info. I just use Wireguard myself, and handle everything else manually, so I’ve been reading all about head/tail-scale.
Surely an actual human has written an article like this that you could share instead.
I enjoyed this blog post about how Tailscale does NAT traversal, which covers the second half of your linked article: https://tailscale.com/blog/how-nat-traversal-works
Thanks, I appreciate the additional info. I just use Wireguard myself, and handle everything else manually, so I’ve been reading all about head/tail-scale.