[ANNOUNCE] WireGuard Snapshot `0.0.20170517` Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, A new snapshot, `0.0.20170517`, has been tagged in the git repository. Please note that this snapshot is, like the rest of the project at this point in time, experimental, and does not consitute a real release that would be considered

Re: Text-based IPC for Userspace Implementations

On Wed, May 17, 2017 at 8:07 PM, Toke Høiland-Jørgensen wrote: > My point was not so much "just use JSON". My point was "you are > disguising something that requires stateful parsing as a simple > key/value scheme, which is bound to lead to bugs eventually". I.e. if > someone were

Re: Text-based IPC for Userspace Implementations

"Jason A. Donenfeld" writes: > Hello list, > > Re:JSON -- > > JSON is difficult to parse and requires large libraries, especially > for something like JSON-RPC. I'd rather not have these dependencies or > complications. > > On the contrary, a simple key=value newline scheme can

Re: Wireguard is not building on Fedora with 4.12 rc1 kernels

On Wed, May 17, 2017 at 10:25:46 -0500, Bruno Wolff III wrote: On Wed, May 17, 2017 at 17:16:20 +0200, "Jason A. Donenfeld" wrote: Hi again, I think I might have fixed this. git fetch && git reset --hard origin/master And then see if it builds now? It

Re: Wireguard is not building on Fedora with 4.12 rc1 kernels

On Wed, May 17, 2017 at 17:16:20 +0200, "Jason A. Donenfeld" wrote: Hi again, I think I might have fixed this. git fetch && git reset --hard origin/master And then see if it builds now? It builds now. In about 15 minutes I'll have it tested.

Re: Wireguard is not building on Fedora with 4.12 rc1 kernels

Hi again, I think I might have fixed this. git fetch && git reset --hard origin/master And then see if it builds now? Alternatively, find me on IRC (I'm zx2c4) and we can talk in real time. Jason ___ WireGuard mailing list WireGuard@lists.zx2c4.com

Re: Wireguard is not building on Fedora with 4.12 rc1 kernels

Hey Bruno, Youch. I'm guessing this is because checking for the existence of a .c file isn't sufficient, since it might not be supplied. I'll change things around and you can retest. Jason ___ WireGuard mailing list WireGuard@lists.zx2c4.com

Wireguard is not building on Fedora with 4.12 rc1 kernels

It looks like the test for memneq is broken and both the kernel and compat versions get used at the same time. [bruno@cerberus src]$ make make -C /lib/modules/4.12.0-0.rc1.git0.1.fc27.x86_64/build M=/home/bruno/WireGuard/src modules make[1]: Entering directory

Re: Text-based IPC for Userspace Implementations

On Wed, May 17, 2017 at 4:14 PM, B wrote: > On Wed, 17 May 2017 16:01:16 +0200 > "Jason A. Donenfeld" wrote: >> Right. I'd indeed be very amused to see a JSON parser land in the >> Linux kernel. > > Perhaps, this could do the trick:

Re: Text-based IPC for Userspace Implementations

On Wed, 17 May 2017 16:01:16 +0200 "Jason A. Donenfeld" wrote: > > Right. I'd indeed be very amused to see a JSON parser land in the > Linux kernel. Perhaps, this could do the trick: https://github.com/martinh/libconfuse Jean-Yves

Re: Text-based IPC for Userspace Implementations

Hi Manuel, On Wed, May 17, 2017 at 4:04 PM, Manuel Schölling wrote: > Great to hear that wireguard gets a nice IPC interface. > Do you already know when this is about to land in the wireguard > releases/repos? When Trevor wakes up today and publishes rev32b of Noise,

Re: Text-based IPC for Userspace Implementations

Hi Jason, Great to hear that wireguard gets a nice IPC interface. Do you already know when this is about to land in the wireguard releases/repos? Bye, Manuel On Wed, 2017-05-17 at 16:01 +0200, Jason A. Donenfeld wrote: > On Tue, May 16, 2017 at 9:26 PM, Jörg Thalheim >

Re: Text-based IPC for Userspace Implementations

On Tue, May 16, 2017 at 9:26 PM, Jörg Thalheim wrote: > For the kernel, netlink will be used, which is already does its own > serialization format. The use of JSON here, would not make sense here. Right. I'd indeed be very amused to see a JSON parser land in the Linux

Re: Text-based IPC for Userspace Implementations

Hello list, Re:JSON -- JSON is difficult to parse and requires large libraries, especially for something like JSON-RPC. I'd rather not have these dependencies or complications. On the contrary, a simple key=value newline scheme can be parsed trivially by anyone in a safe way, and allows for

Re: Text-based IPC for Userspace Implementations

On Tue, May 16, 2017 at 6:33 PM, Guanhao Yin wrote: > In the “configuration protocol” section, I think “wg(8) responds to > ...” should be “An userspace implementation respondes to ...”? Nice find, thanks. > A text based format is certainly easier to deal with than C >