zx2c4

5 ms·

1.
WireGuard for Windows Reaches v1.0(lists.zx2c4.com)
146 points by zx2c4 5mo ago|9 comments
2.
by zx2c4 5mo ago
It's associated per-peer, so it assures a cryptographic mapping between src ip and public key.
3.
by zx2c4 5mo ago
It's like a routing table on the way out and an ACL on the way in. Maybe an easier way to think of it.
4.
by zx2c4 5mo ago
I likewise wonder from time to time whether I should replace WireGuard's allowedips.c trie with something better: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
5.
by zx2c4 5mo ago
Thank you! I'm glad somebody appreciates it. A lot of thought has gone into the installer and upgrade aspect.
6.
Version 1.0 Released: WireGuard for Windows and WireGuardNT(lore.kernel.org)
22 points by zx2c4 5mo ago|2 comments
7.
Version 1.0 of WireGuard for Windows and WireGuardNT Released(lists.zx2c4.com)
6 points by zx2c4 5mo ago|0 comments
8.
by zx2c4 5mo ago
Good question! I've never tried. The NT driver makes use of some of the more advanced features of the networking stack, so possibly not. But you never know. I'd love a Wg4React.
9.
by zx2c4 5mo ago
This was just for WireGuardNT, the kernel driver for the NT kernel that Windows uses. This project -- https://git.zx2c4.com/wireguard-nt/about/ -- is used by this app -- https://git.zx2c4.com/wireg
10.
by zx2c4 5mo ago
As I mentioned in the mailing list post, the Microsoft paperwork shuffling matter got dealt with rather quickly, following all the attention the HN thread from the other day got. And now we're finally out with an update! NT programming
11.
WireGuard makes new Windows release following Microsoft signing resolution(lists.zx2c4.com)
549 points by zx2c4 5mo ago|166 comments
12.
by zx2c4 5mo ago
Microsoft got in touch. All sorted out now.
13.
by zx2c4 5mo ago
Hopefully soon, Microsoft-willing.
14.
by zx2c4 5mo ago
No. The humans just said 60 days.
15.
by zx2c4 5mo ago
Encouraged by this thread, I tweeted about it: https://x.com/EdgeSecurity/status/2041872931576299888
16.
by zx2c4 5mo ago
This is the same problem I'm currently facing with WireGuard. No warning at all, no notification. One day I sign in to publish an update, and yikes, account suspended. Currently undergoing some sort of 60 days appeals process, but who
17.
WireGuard to only support Windows 10 and up(lists.zx2c4.com)
3 points by zx2c4 6mo ago|0 comments
18.
by zx2c4 9mo ago
Voila: https://github.com/WireGuard/wireguard-android/pull/82 https://github.com/WireGuard/wireguard-android/pull/80 In that first one, the double pasted AI retort in the last
19.
by zx2c4 1y ago
On Linux, there's no need to use this. Modern Linux kernels implement getrandom() in the vDSO, which does similar buffering, and keeps those buffers safe in the event of forks or VM forks and kernel reseed events. The readme says: >
20.
by zx2c4 1y ago
I was curious upon seeing this and found the thread where its inclusion was turned down: https://sourceforge.net/p/sevenzip/discussion/45797/thread/a...
21.
by zx2c4 1y ago
> about 4x to 10x faster than channels. I'd be interested to learn why/how and what the underlying structural differences are that make this possible.
22.
by zx2c4 1y ago
Similar project of mine from a long while ago: https://git.zx2c4.com/cscript/about/
23.
by zx2c4 1y ago
Linus merged it on July 24, 2024, so about a year I guess. Kernel is released ~8 weeks after the merge window, so I suppose September or so. I think neither are unbelievably slow. I dunno, take some measurements and see, maybe it suits you.
24.
by zx2c4 1y ago
If you don't need "predictable randomness", like for repeatable statistical simulations, then absolutely, you should only use getrandom(). On recent Linux, this is implemented in the vDSO and is super fast. Few excuses now to
25.
by zx2c4 1y ago
Careful with the "chacha csprng" when the seed from the seed() function appears to be 32 or 64 bits. That's not enough for the cs part. (Also the output stream appears to wrap after 2**32 blocks. Could make this larger.)
26.
by zx2c4 2y ago
Should be fixed now. App Store needed an EU declaration.
27.
by zx2c4 2y ago
> By the end of the training, they learned to name an average of 7.08 pitches (ranging from 3 to 12) at an accuracy of 90% or above and within a response-time (RT) window of 1,305–2,028 ms. That doesn't actually seem very promising,
28.
by zx2c4 2y ago
Saw that. Looks appealing, but I'm not particularly keen on, "We only require that you keep one sudo-enabled account on the system for us to use as needed for troubleshooting." [1] Do I want to give root access to the project
29.
by zx2c4 2y ago
No, it's considerably more involved than that. For example, there's extensive CI: https://www.wireguard.com/build-status/ This thing builds a fresh kernel and boots it for every commit for a bunch of systems.
30.
by zx2c4 2y ago
The WireGuard project is also in the same situation, due to Equinix Metal shutting down. If anybody would like to host us, please reach out to team at wireguard dot com. Thanks!

More ›