Hacker News Reader

Comment by dontbenebby | Hacker News Reader

>FreeBSD WireGuard drama

Can you fill me in? I experimented with Wireguard a while back but it's been a few.

(It sounds like concern about design choices not... gossip? Infosec has been insane the past fourish years.)

The original implementation had a lot of issues, but more importantly it was pushed to head and deployed in production without a review:

https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...

This is a lie. The bad code was never "deployed in production", it was pulled before a release. FreeBSD users were never exposed to it. HEAD code branch is where reviews happen in BSDs, this code failed that review and was removed.

It’s also a lie that it wasn’t available for review. It was in review for about 10 months before it started to land in a release.

How about you provide links that backup your claims.. It's well documented that you'll go to great lengths to act in bad faith and make nonsense claims on the internet.

https://www.wipo.int/amc/en/domains/search/text.jsp?case=D20...

https://opnsense.org/opnsense-com/

https://reviews.freebsd.org/D26137

It looks a lot like that was landed without completion of a proper review, and with several changes made without any review. I appreciated Netgate's commitment to improve the FreeBSD operating system, and to build the pfSense product. It's the attitude of Netgate's team, where an opportunity to offer a mea culpa and move forwards with the expertise of a core FreeBSD developer/maintainer and the subject matter expert was presented, was instead met with open hostility. It made it appear as if getting it done was more important than getting it right. Sometimes we get things wrong, we put a lot of work into code that we're proud of, then our project manager and peers come along and absolutely tear it down and rebuild it. It's an opportunity for growth, not a waste of effort or money.

I'm glad things improved and that you guys brought on Christian McDonald.

It was released to production by Netgate in pfSense. That's why they threw such a hissy fit over it when the code quality was revealed and blew up publicly.

A a larger backer and contributor to freeBSD pushed wireguard kernel mode support out in one of their production releases and then slowly walked it back. Whether freeBSD likes it or not, this sort of thing reflects poorly on freeBSD as a whole when a large donor/backer and contributor that advertises freeBSD then releases something that is a pile of half baked shit.

https://www.netgate.com/blog/wireguard-removed-from-pfsense-...

https://lists.zx2c4.com/pipermail/wireguard/2021-March/00650...

I once deployed linux-next in production, it reflects poorly on linux.....

But yeah dont use pfsense but opnsense...but everyone should know that already....right?

https://news.ycombinator.com/item?id=30719403

Reply on news.ycombinator.com