From: jungle boogie <jungleboogie0@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [ANNOUNCE] WireGuard Merged Into OpenBSD
Date: Sun, 21 Jun 2020 14:48:08 -0700 [thread overview]
Message-ID: <83ceb9ac-d620-f569-e694-77f6a6bd3678@gmail.com> (raw)
In-Reply-To: <CAHmME9pAwNty0q_+WD8RebgfdMdaFbh-OsKXaAb7wdhKBR+6Sg@mail.gmail.com>
On 6/21/20 12:18 PM, Jason A. Donenfeld wrote:
> Hey everyone,
>
> I'm happy to announce that WireGuard has been merged into the OpenBSD
> kernel, with integration into userland as well.
>
> https://marc.info/?l=openbsd-cvs&m=159274150512676&w=2
>
> Matt Dunwoodie and I have been working on this for quite some time
> now, with at some point Matt even showing up at my door in Paris to
> push the effort further. This marks the culmination of quite a bit of
> effort, and certainly a multi-year project for Matt. I should also
> note that the upstreaming process to OpenBSD was extremely pleasant.
> We did three patch revisions, with useful feedback on each one and a
> very supportive community.
Jason and Matt - outstanding, outstanding job. I've comfortably ran
Wireguard on OpenBSD with Jason's first build script for roughly 1 1/2
years, but I'm happy to see Wireguard is now in-kernel and development
will continue there.
Thank you two for all of your efforts you've made.
I hope everyone else is as excited about this as I am!
For those that don't know, OpenBSD's homepage:
https://www.openbsd.org/
OpenBSD Journal:
https://www.undeadly.org/cgi?action=front
Reddit:
https://www.reddit.com/r/openbsd/
>
> I imagine that this work will ship with OpenBSD 6.8.
>
> Enjoy!
> Jason
>
next prev parent reply other threads:[~2020-06-21 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 19:18 Jason A. Donenfeld
2020-06-21 21:48 ` jungle boogie [this message]
2020-06-21 22:05 ` Laslo Hunhold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ceb9ac-d620-f569-e694-77f6a6bd3678@gmail.com \
--to=jungleboogie0@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).