wireguard-windows/conf, branch masterWireGuard client for Windowshttps://git.zx2c4.com/wireguard-windows/atom/conf?h=master2026-09-22T19:48:03Zglobal: use crypto/ecdh for X255192026-09-22T19:48:03ZJason A. DonenfeldJason@zx2c4.com2026-09-22T19:36:51Zurn:sha1:7b2f7adcaa4346d10d340f93c840bda82fbc204b
Use crypto/ecdh directly, because the old x/crypto 25519 library was
wrapping it.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
global: rand.Read never errors2026-09-22T10:48:23ZJason A. DonenfeldJason@zx2c4.com2026-09-22T10:48:21Zurn:sha1:4a47e2142ffd031b44055f1a2b683cf7ebd3446d
Part of the API contract, apparently.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: clear the pending peer when entering an interface section2026-09-20T11:34:53ZJason A. DonenfeldJason@zx2c4.com2026-09-19T14:29:46Zurn:sha1:a087f25aaa1de9f5312ebcc7d13170cef9c196a1
Otherwise it gets appended again at the next peer section or EOF. This
also prevents the single-peer kill switch from being enabled.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: fail write if flushing file buffers fails2026-07-14T14:43:06ZJason A. DonenfeldJason@zx2c4.com2026-07-13T21:53:10Zurn:sha1:68b3680f8130cbf31fc9b596128550d075692434
If the flush fails, the data is not durably on disk, so the rename
must not be published. Delete it in this case.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: preserve comments across serialization2026-07-14T14:11:51ZJason A. DonenfeldJason@zx2c4.com2026-07-13T16:45:01Zurn:sha1:29de783cf48c938866a53299f9173c518ec9f7cb
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: deal with ::0 endpoints properly2026-07-14T14:11:51ZJason A. DonenfeldJason@zx2c4.com2026-07-13T16:43:33Zurn:sha1:78346e0e18202e5271c14d8cbea583c685054b20
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: flush file buffers before atomically renaming into place2026-06-13T11:09:35ZJason A. DonenfeldJason@zx2c4.com2026-05-18T14:00:16Zurn:sha1:878ae6219cd7de9f50269f932cc2720c2b4ec289
NTFS journals the rename's metadata change but does not journal user
data. Without an explicit flush a power loss between the cache
manager publishing the rename and writing back the file's pages can
leave the destination at its final name with zero or partial
contents, while the prior file is gone.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: keep retrying when the config-directory watcher fails to start2026-06-13T11:09:35ZJason A. DonenfeldJason@zx2c4.com2026-05-14T07:49:09Zurn:sha1:2b143c5025f41d703f492a4fffe4136d9df2c89d
The watcher's setup is guarded by sync.Once, which is consumed the
moment the goroutine is spawned. If tunnelConfigurationsDirectory or
FindFirstChangeNotification fails on the first attempt the goroutine
exits, but every subsequent RegisterStoreChangeCallback sees the Once
already done and skips the spawn, so changes are silently never
reported again. Retry these initial failures on the existing
startover loop instead of bailing out.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: don't strip '#' from PreUp/PreDown/PostUp/PostDown values2026-06-13T11:09:35ZJason A. DonenfeldJason@zx2c4.com2026-05-18T07:33:05Zurn:sha1:743c2f2286efd40c1e5de3f6d0b97012861e5cde
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
conf: reject reserved names with any extension2026-06-13T11:09:35ZJason A. DonenfeldJason@zx2c4.com2026-05-18T13:56:17Zurn:sha1:706da65f4c94d485c8676cf55983fd03ccc41e1e
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>