wireguard-windows/embeddable-dll-service, branch master

overlay: stub out crypto/rand FIPS140 garbage

2026-09-22T21:05:45Z

The Go crypto library used to be simple and nice and an example of how to do things well. Unfortunately, the addition of FIPS140 to it has brought disgusting enterprise patterns and gummed up the code. One place this really comes out is in the insane infrastructure behind the RNG. It really only should be calling the system random functions and nothing more. But in contemporary Go, simply calling into the RNG brings along with it in the binary: - A bizarre voodoo magic userspace entropy collector - A specialized SHA384 implementation for said entropy collector - An AES implementation - An AES-NI accelerated AES implementation - A CTR implementation for AES - A GCM implementation for AES - Some CPU detection code - An implementation of some FIPS-specified DRBG algorithm - An HMAC implementation - A SHA256 implementation - An AVX2-accelerated SHA256 implementation - A SHA3 implementation (including cSHAKE) - An AVX2-accelerated SHA3 implementation - A SHA512 implementation - Some generic XOR-bytes routines - The actual syscall wrappers for getting random numbers Obviously this is completely insane. There's a tangled mess of components including eachother, a disorganized patchwork of FIPS code and BoringCrypto code and enterprisey API hooks and self checks and auto-included initializers. It seems like a mess of a library these days. So, here we beat down this madness by using a Go build overlay to replace various parts of the crypto library with stub functions. This is pretty nasty. But at least it compiles out some of this junk. I'm trying to fix this upstream in the meanwhile [1], and so we'll see what comes of that. Link: https://github.com/golang/go/issues/81639 Signed-off-by: Jason A. Donenfeld

build: restore separate Go directory on Windows

2026-09-22T19:48:03Z

Keep the Go toolchain under .deps\go to match the Linux build layout. Signed-off-by: Jason A. Donenfeld

global: use crypto/ecdh for X25519

2026-09-22T19:48:03Z

Use crypto/ecdh directly, because the old x/crypto 25519 library was wrapping it. Signed-off-by: Jason A. Donenfeld

global: rand.Read never errors

2026-09-22T10:48:23Z

Part of the API contract, apparently. Signed-off-by: Jason A. Donenfeld

embeddable-dll-service: csharp: fix allowed IP layout

2026-09-20T11:54:54Z

The CIDR byte follows the 16-byte address and two-byte address family, placing it at offset 18. Add the missing flags field at offset 20 and its Remove flag to match the native structure. Signed-off-by: Jason A. Donenfeld

global: raise min windows version to 10

2026-03-21T11:23:55Z

Since we're also bumping the PE subsystem header to 10.0, this means we need a _load_config with the proper flags. So there's some work to be done here. This also means bumping LLVM and Go builds. In the case of Go, the patch is still pending: https://go-review.googlesource.com/c/go/+/756680 , so it's a custom build. Remove lots of compatibility code and hacks. Also update the installer to display a useful message. Signed-off-by: Jason A. Donenfeld

global: bump date

2026-03-18T22:45:25Z

Signed-off-by: Jason A. Donenfeld

build: make code signing method configurable

2024-10-17T12:27:00Z

Existing code signing was hard-coded to use a locally installed certificate (hardware security dongles included). However, signtool.exe is extensible to allow any kind of digest signing plugin with /dlib and /dmdf switches. This is used for cloud-based code signing (e.g. Microsoft Trusted Signing). Signed-off-by: Simon Rozman

embeddable-dll-service: build: .gitignore outputs

2022-03-28T11:19:14Z

Signed-off-by: Simon Rozman

embeddable-dll-service: build: integrate tunnel.dll signing

2022-03-28T11:17:34Z

Signed-off-by: Simon Rozman