zx2c4

30 ms·

121.
by zx2c4 7y ago
From the most recent wireguard-linux-compat release notes: https://lists.zx2c4.com/pipermail/wireguard/2020-January/004... > Please note that until Linux 5.6 is released, this snapshot is a snapshot rather
122.
by zx2c4 7y ago
> Wireguard needs to put actual logging into the product before anyone should consider using it in production. The kernel already has this: # modprobe wireguard && echo module wireguard +p > /sys/kernel/de
123.
by zx2c4 7y ago
Likely yes. I'm discussing that possibility with them.
124.
by zx2c4 7y ago
Right. We'll stamp a 1.0 on the backports as soon as 5.6 is released and goes through the normal mainline release process. Stamping a 1.0 on the compat backport before mainline would be premature, but doing it the day of is the plan.
125.
by zx2c4 7y ago
Thanks for posting this; we appreciate it. More generally, donation options for the project are listed here: https://www.wireguard.com/donations/
126.
by zx2c4 7y ago
> There are a number of things that the blog post gets wrong. First of all, it was not Jason A. Donenfeld, the author of Wiregard, which added the ChaCha20-based cryptographic random number to Linux. It was me[1], as the maintainer of Li
127.
by zx2c4 7y ago
We merged "Frankenzinc" for 5.5, some sort of contorted compromise solution. I'll be working on fixing lingering warts during the 5.5 and 5.6 cycles there.
128.
by zx2c4 7y ago
Debian will probably ship it as a module, like the other networking modules they ship, which means as long as they don't change ABI, after your `apt upgrade`, you can do the usual `rmmod wireguard && modprobe wireguard` to hot-
129.
by zx2c4 7y ago
Yes. A 1.0 is now on the horizon.
130.
by zx2c4 7y ago
No, I'm referring to that PPA, which includes the error-prone DKMS stuff. I'm glad it worked for you. Indeed we've put a lot of effort into ensuring that our DKMS stuff mostly _does_ work properly. Sometimes it doesn't t
131.
by zx2c4 7y ago
It means that WireGuard will be included in your distro's kernel, which will ease installation. Before, you had to do some ugly kernel module compilation steps, usually using dkms, which was prone to failure and was a general nightmare
132.
by zx2c4 7y ago
Release announcements are here: https://lists.zx2c4.com/pipermail/wireguard/2019-December/00... https://lists.zx2c4.com/pipermail/wireguard/2019-December/00... https:/&#x
133.
by zx2c4 7y ago
I wrote to wgml about it: https://lists.zx2c4.com/pipermail/wireguard/2019-December/00...
134.
by zx2c4 7y ago
Yea... not nice at all. And now we'll probably have to simultaneously support nftables. This isn't a route I really want to go down. Suggestions on alternatives are welcome.
135.
by zx2c4 7y ago
We're working around this CVE in WireGuard's wg-quick(8) with a rule something like: iptables -t raw -I PREROUTING ! -i wg0 -d 10.182.12.8 -m addrtype ! --src-type LOCAL -j DROP where wg0 is the WireGuard interface and 10
136.
by zx2c4 7y ago
We'll change the language on the site once we're upstream in the Linux kernel. Hopefully that's around the corner.
137.
by zx2c4 7y ago
WireGuard uses the correct kernel function, get_random_u32(). WireGuard does not use RdRand directly. WireGuard instead uses the proper kernel function for asking for a unsigned 32-bit number. The kernel implements get_random_u32() under th
138.
by zx2c4 7y ago
WireGuard uses the correct kernel function, get_random_u32(). WireGuard does not use RdRand directly. WireGuard instead uses the proper kernel function for asking for a unsigned 32-bit number. The kernel implements get_random_u32() under th
139.
by zx2c4 7y ago
WireGuard uses the correct kernel function, get_random_u32(). WireGuard does not use RdRand directly. WireGuard instead uses the proper kernel function for asking for a unsigned 32-bit number. The kernel implements get_random_u32() under th
140.
by zx2c4 7y ago
Thanks for that feedback about the battery drain. If you do notice something is off there again, please don't hesitate to email us about it, as that kind of thing is very useful feedback.
141.
by zx2c4 7y ago
[Prior reply got detached in some cleanup, so adding again here.] An update on the WireGuard situation: they have reinstated the app _without_ the donation link. From what I can tell from talking to Google insiders, there has been no change
142.
by zx2c4 7y ago
An update on this: they have reinstated the app WITHOUT the link, and there has been no change in policy, according to insiders. Officially, Google has not communicated at all with us about it.
143.
by zx2c4 7y ago
Oh, super. Thanks for confirming. I'll wait a day for some response from Google, I suppose, and then decide whether or not to re-add it. I certainly don't want to inconvenience users again.
144.
by zx2c4 7y ago
Could you double check 0.0.20191013? My phone just updated, and I'm seeing the APK version that has the donation link removed, 0.0.20191016. I haven't received any further emails from Google (yet?), so I'm still uncertain as
145.
by zx2c4 7y ago
I agree with your sentiment in theory. Unfortunately, in practice, Google Play Store rips off my signature after I upload and sticks their own one on instead. Blah.
146.
by zx2c4 7y ago
It indeed is unfortunate. But what other recourse did we have? The first objective, before we even consider donations or anything, is to make our software available and functional to our users. So we had to resubmit. And it's not like
147.
by zx2c4 7y ago
> have you not wanted to replicate multi-screen setup on your laptop (while traveling or when not on your desktop)? P Remember the Thinkpad W701ds? With its retractable second screen, this was a thing of beauty: https://i.kin
148.
by zx2c4 7y ago
That commit is just a fixup of the prior which the author probably intended to rebase and squash together. The actual commit for this vuln is here: https://github.com/Exim/exim/commit/2600301ba6dbac5c9d640c87.
149.
by zx2c4 7y ago
Meanwhile Gentoo's portage took almost 7 minutes to build qemu... zx2c4@thinkpad ~ $ genlop -t qemu Sat May 18 15:36:44 2019 >>> app-emulation/qemu-4.0.0-r2 merge time: 6 minutes and 49 seconds.
150.
Deterministic Cryptographically Authenticated Network Signatures on Windows NLA(lists.zx2c4.com)
3 points by zx2c4 7y ago|0 comments

More ›