Re: [Update] net/wireguard-tools : Update to 1.0.20191226

On Fri, Dec 27, 2019 at 8:59 PM Stuart Henderson wrote: > > On 2019/12/27 19:06, Jason A. Donenfeld wrote: > > On Fri, Dec 27, 2019 at 6:46 PM Klemens Nanni wrote: > > > > > > On Fri, Dec 27, 2019 at 05:38:20PM +0100, Jason A. Donenfeld wrote: > > > > -V

Re: [Update] net/wireguard-tools : Update to 1.0.20191226

On Fri, Dec 27, 2019 at 6:46 PM Klemens Nanni wrote: > > On Fri, Dec 27, 2019 at 05:38:20PM +0100, Jason A. Donenfeld wrote: > > -V = 0.0.20191212 > > -DISTNAME = WireGuard-$V > > +V = 1.0.20191226 > > +DISTNAME = wireguard-tools-$V > > P

[Update] net/wireguard-tools : Update to 1.0.20191226

Hi folks, We recently moved to a new repo for the tools upstream and bumped the version number. This patch below adjusts the ports makefile. Reference: https://lists.zx2c4.com/pipermail/wireguard/2019-December/004787.html I haven't checked that this works on a real OpenBSD machine, though it

Re: WireGuard for OpenBSD

Hi Anthony, On Thu, Jun 21, 2018 at 3:05 AM Anthony J. Bentley wrote: > Oops, I accidentally sent out my (unfinished, broken) wireguard-go draft > from last week. Attached is the working version I meant to send out. Thanks. A few notes on what you just sent: > - ipcErrorProtocol =

Re: WireGuard for OpenBSD

Hi Anthony, Thanks for sending this along. Two questions: > ALL_TARGET = wg Do you need to add wg-quick as a target too? > sed -i s,git.zx2c4.com/wireguard-go,all, What is the purpose of this? Why do you need this? The makefile should successfully fake a gopath. This install script currently

Re: WireGuard for OpenBSD

Alright, we now have a release that fully supports OpenBSD, so the full instructions for the two packages are: 1. wireguard-tools, providing wg(8) and wg-quick(8) Runtime dependencies: libc, bash, wireguard-go Buildtime dependencies: gmake, c compiler, libc Fixup: sed -i 's/install

Re: WireGuard for OpenBSD

On Wed, May 23, 2018 at 3:59 PM, Landry Breuil wrote: > I wouldnt count on it, since generally openbsd is wary of adding > unecessary options, adding -v to mv and cp lead to quite a bit of > bikeshedding, and mv -P was recently strongly turned down. Yikes! I didn't realize I

Re: WireGuard for OpenBSD

On Wed, May 23, 2018 at 3:24 PM, Landry Breuil <lan...@openbsd.org> wrote: > On Wed, May 23, 2018 at 02:28:13PM +0200, Jason A. Donenfeld wrote: >> On Wed, May 23, 2018 at 10:55 AM, Anthony J. Bentley <anth...@anjbe.name> >> wrote: >> > Attached is one. It wil

Re: WireGuard for OpenBSD

On Wed, May 23, 2018 at 10:55 AM, Anthony J. Bentley wrote: > Attached is one. It will need to be updated to use the next tag once > it's released. Looks good to me. Indeed I don't like this manually carrying files from the next release in ${FILES}, but that problem goes away

WireGuard for OpenBSD

[cross-posted to the WireGuard mailing list] Hello OpenBSD Ports List, I sent a very similar email [0] to the FreeBSD ports list yesterday. I'm the author of WireGuard [1], a secure network tunnel protocol [2] and a set of implementations of it. It was originally designed for the Linux kernel,