Viewing profile — zx2c4
zx2c4
HN member- Joined
- Sun, May 22, 2011, 8:58 AM UTC
- HN karma
- 7,628
- Public activity
- 762 items
- HN profile
- View on Hacker News ↗
About zx2c4
[1] https://www.zx2c4.com/ [2] https://www.edgesecurity.com/ [3] https://www.wireguard.com/ [4] https://www.passwordstore.org/ [5] https://git.zx2c4.com/cgit/about/ [6] https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/linux.git/ [7] https://git.zx2c4.com/
Recent public activity
- story
-
comment
Comment #47832266
It's associated per-peer, so it assures a cryptographic mapping between src ip and public key.
-
comment
Comment #47831803
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.
-
comment
Comment #47831126
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...
-
comment
Comment #47819507
Thank you! I'm glad somebody appreciates it. A lot of thought has gone into the installer and upgrade aspect.
- story
- story
-
comment
Comment #47722093
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.
-
comment
Comment #47720267
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://gi…
-
comment
Comment #47720228
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. A…
-
story
WireGuard makes new Windows release following Microsoft signing resolution
Recent and related: Microsoft terminated the account VeraCrypt used to sign Windows drivers - https://news.ycombinator.com/item?id=47686549
-
comment
Comment #47701674
Microsoft got in touch. All sorted out now.
-
comment
Comment #47696634
Hopefully soon, Microsoft-willing.
-
comment
Comment #47694844
No. The humans just said 60 days.
-
comment
Comment #47690022
Encouraged by this thread, I tweeted about it: https://x.com/EdgeSecurity/status/2041872931576299888
-
comment
Comment #47687884
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 un…
- story
-
comment
Comment #46314052
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 comm…
-
comment
Comment #44612473
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 V…
-
comment
Comment #44509719
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...
-
comment
Comment #44414966
> 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.
-
comment
Comment #44216821
Similar project of mine from a long while ago: https://git.zx2c4.com/cscript/about/
-
comment
Comment #44160383
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. …
-
comment
Comment #44159100
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 t…
-
comment
Comment #44159058
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 afte…