Live data from Hacker News

WireGuard in FreeBSD

cgit.freebsd.org

41–50 of 84 posts

Re: WireGuard in FreeBSD

#41

Good post from Phoronix on the topic, also giving a bit of context as to why they're "bringing back" the driver: https://www.phoronix.com/news/FreeBSD-WireGuard-Lands-2022

I don't know what is good about this post. The ars technical post linked in another comment really sheds some light on to this.

Re: WireGuard in FreeBSD

#42

Between the FreeBSD WireGuard drama and WireGuard's maintainer's (Jason Donenfeld) reaction to the NetBSD implementation, I think it's a good idea to look at not only what's happening, but why and by whom. There's something slightly fishy about it all. https://mail-index.netbsd.org/current-users/2020/08/20/msg03... https://mail-index.netbsd.org/current-users/2020/08/22/msg03... Jason Donenfeld has, to this day, never…

>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.)

Re: WireGuard in FreeBSD

#43

Between the FreeBSD WireGuard drama and WireGuard's maintainer's (Jason Donenfeld) reaction to the NetBSD implementation, I think it's a good idea to look at not only what's happening, but why and by whom. There's something slightly fishy about it all. https://mail-index.netbsd.org/current-users/2020/08/20/msg03... https://mail-index.netbsd.org/current-users/2020/08/22/msg03... Jason Donenfeld has, to this day, never…

Thanks for the background. However, I believe your question

> Jason Donenfeld has, to this day, never answered direct and simple questions about WHY he felt so strongly that NetBSD's wg implementation should be removed from NetBSD.

gets answered by Jason:

> In its current form, there are implementation flaws and violations that I do not consider acceptable, and deploying this kind of thing is highly irresponsible and harmful to your users. Rather than playing never ending whack-a-mole misery with this -- which is not a path I'm willing to go down here -- I'd like to re-examine how this is built from the ground-up and do some serious code study.

(This response of his is corroborated by the article https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice... which someone else posted further down.)

He also mentions that he's not against having a WireGuard implementation included in NetBSD in general.

Re: WireGuard in FreeBSD

#44
post #40

Earlier quoted context omitted.

no, there might even be detriment Because of the way FreeBSD modifes openssh. OpenBSD might be an improvement to Ubuntu security wise.

No openssl: https://www.wireguard.com/papers/zinzindohoue-bhargavan-prot...

I meant in the context of a Bastion ssh server, which is what the patent meant i think.

Re: WireGuard in FreeBSD

#45

Between the FreeBSD WireGuard drama and WireGuard's maintainer's (Jason Donenfeld) reaction to the NetBSD implementation, I think it's a good idea to look at not only what's happening, but why and by whom. There's something slightly fishy about it all. https://mail-index.netbsd.org/current-users/2020/08/20/msg03... https://mail-index.netbsd.org/current-users/2020/08/22/msg03... Jason Donenfeld has, to this day, never…

The "why" is IMHO simple if you look at the pattern: they didn't ask him for advise. I guess he really expects this. While I personally find this attitude/his comments in different places a bit toxic, he has unfortunately been proven right in the past (like in the freesbd case). I guess it sometimes just requires such people to something right with just enough rigour. I am also be really thankful for this beautiful bit of software in such a messed up space. However, I also totally understand the people who have not asked for his opinion before releasing (I guess this can be a downside).

Re: WireGuard in FreeBSD

#47

Between the FreeBSD WireGuard drama and WireGuard's maintainer's (Jason Donenfeld) reaction to the NetBSD implementation, I think it's a good idea to look at not only what's happening, but why and by whom. There's something slightly fishy about it all. https://mail-index.netbsd.org/current-users/2020/08/20/msg03... https://mail-index.netbsd.org/current-users/2020/08/22/msg03... Jason Donenfeld has, to this day, never…

>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...

Re: WireGuard in FreeBSD

#48

Between the FreeBSD WireGuard drama and WireGuard's maintainer's (Jason Donenfeld) reaction to the NetBSD implementation, I think it's a good idea to look at not only what's happening, but why and by whom. There's something slightly fishy about it all. https://mail-index.netbsd.org/current-users/2020/08/20/msg03... https://mail-index.netbsd.org/current-users/2020/08/22/msg03... Jason Donenfeld has, to this day, never…

Thanks for the background. However, I believe your question > Jason Donenfeld has, to this day, never answered direct and simple questions about WHY he felt so strongly that NetBSD's wg implementation should be removed from NetBSD. gets answered by Jason: > In its current form, there are implementation flaws and violations that I do not consider acceptable, and deploying this kind of thing is highly irresponsible and…

What about that describes why it should not be implemented? All he says is "I don't like it and it is not acceptable". If you write a paper and have it proof-read by many competent people, then hand that paper in to a teacher and get back an F with "This is no good, it has flaws I do not consider acceptable", would you think that was reasonable explanation for failing your paper?

Re: WireGuard in FreeBSD

#49
post #47

Earlier quoted context omitted.

>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...

[deleted]

Re: WireGuard in FreeBSD

#50
post #47

Earlier quoted context omitted.

>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.
Post reply on HN