From owner-freebsd-net@freebsd.org Tue Feb 18 14:32:32 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E41D23B5E2 for ; Tue, 18 Feb 2020 14:32:32 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "frisell.zx2c4.com", Issuer "frisell.zx2c4.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48MNbz2cPXz3GXj; Tue, 18 Feb 2020 14:32:30 +0000 (UTC) (envelope-from Jason@zx2c4.com) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7a52d2d7; Tue, 18 Feb 2020 14:29:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=mail; bh=mVd Q51LvjRVcy9KFDwZHR3/xFv0=; b=OTAhdA5nUVrkeMTICLZdzoBMZJ62V968Ba3 fgr7fkfAQD9hHbM8EegK3GOScIFE81bEMcYgoSDccplukxvGTgsEtvfqoHxipuLO DO0b4qKL+e7KgqzN0Qg2xAzTXZn0m7LKcaFqocvebNz06miz+T5oxmCSbP7yUGFB Gm40x0f87jXPC0AN9bnidMGuZrqaGu4kAvOVVzUPN8xuOkNs4GbzFLDYxgCpIfEY oFJopqCc9AP2rbV9pibB88VfWImYffWK3VG95LK/CkuV+HZh3vvG0Fn0iDu84ZYI zchcmss9VXEaDM0a73NaWyy4huwzBT00hU7WyojSxhMWj1CeDbQ== Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 8a21a270 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 18 Feb 2020 14:29:51 +0000 (UTC) Received: by mail-oi1-f179.google.com with SMTP id d62so20224369oia.11; Tue, 18 Feb 2020 06:32:29 -0800 (PST) X-Gm-Message-State: APjAAAWheAAqVp2zQfQAxsyyp12dM+CZsT7miIyM1DLo7cvsSNlzk2bi hCBZoiHx7TIfT+FxTIQzcyFHk60hngPhpGC+ZvQ= X-Google-Smtp-Source: APXvYqwPld+RXfnmTNY+ZkLlo9iaIvQwLElnu5mExIATm8mUuGyyDBMaGt6/f8DvKeYfoB9S93/USjHB1PV200GRmWU= X-Received: by 2002:a05:6808:4cc:: with SMTP id a12mr1473198oie.115.1582036348292; Tue, 18 Feb 2020 06:32:28 -0800 (PST) MIME-Version: 1.0 From: "Jason A. Donenfeld" Date: Tue, 18 Feb 2020 15:32:17 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: wireguard implementation in progress with zero coordination or communication with wireguard project? can we help? To: mmacy@freebsd.org Cc: freebsd-net@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 48MNbz2cPXz3GXj X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zx2c4.com header.s=mail header.b=OTAhdA5n; dmarc=pass (policy=none) header.from=zx2c4.com; spf=pass (mx1.freebsd.org: domain of Jason@zx2c4.com designates 192.95.5.64 as permitted sender) smtp.mailfrom=Jason@zx2c4.com X-Spamd-Result: default: False [-2.15 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[zx2c4.com:s=mail]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.16)[ipnet: 192.95.0.0/18(-2.84), asn: 16276(2.06), country: FR(0.00)]; DKIM_TRACE(0.00)[zx2c4.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[64.5.95.192.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_ALLOW(-0.50)[zx2c4.com,none]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:192.95.0.0/18, country:FR]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2020 14:32:32 -0000 Hi Matthew, I'm Jason, the lead of the WireGuard project. Somebody brought it to my attention that Netgate has been sponsoring you to write a WireGuard kernel implementation for FreeBSD. What a terrific development! However, this is in fact the first I've heard of such an initiative, which is quite surprising and possibly alarming. While I can sort of vaguely imagine possible commercial reasons for this from Netgate's perspective, I can't imagine that dis-coordination is something desirable on the part of FreeBSD. I'd like to find some way we can work together on this. In parallel, the WireGuard project has been working on an implementation for OpenBSD's kernel that we intended to eventually port to FreeBSD. We're also working on other implementations for other platforms as well. It will be interesting to learn if your work is "from scratch", or if you've already begun porting the in-progress OpenBSD work. Our goal as a Project is to keep things as uniform and inter-operable as possible, to offer the same good experience across platforms. Another goal is to keep the security and security-related semantics uniform. We view WireGuard as more than just the development of a protocol, but rather as a set of implementations that we feel good about. To that end, I was wondering if whatever development has been going on for the FreeBSD kernel could begin to work with the WireGuard project. Personally, I'd be interesting in auditing the code, reviewing the design, matching up configuration semantics, and generally the set of things we've done on each platform so far to make sure things going. In other words, how can the WireGuard project get involved with this great FreeBSD development? How can we begin to coordinate? Thanks, Jason