3 ms·
Unfortunately the NetBSD side's story was not widely known or reported. Otherwise it would give a different perspective to the case here.
by ksec 6y ago
Unfortunately the NetBSD side's story was not widely known or reported. Otherwise it would give a different perspective to the case here.
- deleted 6y ago[deleted]
- gonzo 6y agoSalter couldn’t even get the CEO’s name right, but he did manage to drag Macy’s spouse into his article. Guy is a muck-racking misogynist.
- tw04 6y agoCurious what the end result was though. It appears they collectively agreed to talk it out in September, then... nothing? Github shows a handful of commits, but nothing major. No chatter on the mailing list. NetBSD hasn't renamed "wireguard" which they said they were considering as an option if Jason was going to keep pushing back on the existing code. The lack of major changes to the code makes me think they also didn't take him up on his offer to scrap the whole thing and start from scratch or port the OpenBSD implementation. Anyone happen to have any further insight?
- ksec 6y agoI sometimes wonder why Jason himself doesn't just do it himself on NetBSD and FreeBSD. Although OpenBSD doesn't seems to have any issues which is also worth mentioning.