wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Nicolai <nicolai-wireguard@chocolatine.org>
To: wireguard@lists.zx2c4.com
Subject: Re: Removing WireGuard Support From FreeBSD Base
Date: Tue, 16 Mar 2021 18:24:30 +0000	[thread overview]
Message-ID: <20210316182430.GA42183@chocolatine.org> (raw)
In-Reply-To: <CAHmME9rFU8dknvVfWmRgbLud2bkQMNvVSBqNUfUiBcnTgV90yA@mail.gmail.com>

On Tue, Mar 16, 2021 at 11:37:59AM -0600, Jason A. Donenfeld wrote:

> Here's the technical background you asked for:
> - We found tons of issues with the original code base.
> - We spent a week rewriting that codebase.
> So here's the rationale:
> - Merging a week-old codebase into an operating system kernel is a bad idea.

Yeah, when I saw the recent sudden work to get WireGuard into FreeBSD
13, I was excited but also nervous since it's been in beta/RC for a
while, just a bit late to introduce important features.  I think the
current plan is sensible and will produce a result everyone likes.

> We probably can even offer prebuilts at some point for people who want
> to test out snapshots.

That's a great idea!  WireGuard is what finally got me to run
OpenBSD-current, so I could test the snaps.

Nicolai

  reply	other threads:[~2021-03-16 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 16:48 Removing WireGuard Support From FreeBSD Base Kyle Evans
2021-03-16 17:13 ` Jeffrey Walton
2021-03-16 17:37   ` Jason A. Donenfeld
2021-03-16 18:24     ` Nicolai [this message]
2021-03-16 17:30 ` Jason A. Donenfeld
2021-03-17 12:53 ` Gordon Bergling
2021-03-17 18:34   ` Jason A. Donenfeld
2021-03-17 19:29     ` Wireguard for FreeBSD without iflib Frank Behrens
2021-03-17 22:17       ` Jason A. Donenfeld
2021-03-19  7:47     ` Removing WireGuard Support From FreeBSD Base Gordon Bergling
2021-03-19 10:43       ` Evilham
2021-03-18 16:52 ` Kyle Evans
2021-03-18 16:57   ` Jason A. Donenfeld
2021-03-18 18:49 John Jacobs

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=20210316182430.GA42183@chocolatine.org \
    --to=nicolai-wireguard@chocolatine.org \
    --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).