3 ms·
Yes, that's unfortunate and I think he's handled it well there. It was the same with the guy who did a windows implementation, didn't want to work with the upst
by newaccoutnas 8y ago
Yes, that's unfortunate and I think he's handled it well there. It was the same with the guy who did a windows implementation, didn't want to work with the upstream so is rife for fragmenting the protocol long-term
- _pmf_ 8y agoI don't get what's unfortunate about it. Cloudflare is probably being upfront about their implementation suiting their needs; I think it's laudable and avoids bad blood in the future, should the goals diverge. Given that WireGuard has been designed to be relatively simple, maybe multiple widely used implementations will make sure it stays that way.
- newaccoutnas 8y agoBecause they've refused to engage with the upstream, it puts them in the 'driving seat' as it were as their available resource eclipses the community's.
- SEJeff 8y agoThe official upstream windows implementation is making excellent progress however. In specific, WinTUN[1] was just released. Disclaimer: My employer sponsored a lot of the work with Jason for the windows wireguard port. (Search for "Accelerating Windows Development on https://www.wireguard.com/donations/ https://www.wireguard.com/donations/) [1] https://lists.zx2c4.com/pipermail/wireguard/2019-March/004038.html https://lists.zx2c4.com/pipermail/wireguard/2019-March/00403...