Item — HN Reader

> both endpoints would need the keys and private IP/subnet addresses of their peers in order to communicate.

That’s how every other implementation works. It’s not a requirement of the protocol though, and that inspired this tweak in my implementation.

FWIW, it still allows configuring known peers separately from unknown ones.

Sorry for the double reply, I had meant to address that in the first.

1 comments

Thanks for your explanations. I recognize that you're offering this as a product within the AWS ecosystem, but because it's an evolution of WireGuard, which has a GPLv2 license, you should probably provide some way for users to obtain your source code, unless you've acquired a separate license directly from Jason Donenfeld.

I don't use any code from others here, it's a ground-up implementation of the protocol in C# targeting .Net 10 AoT.