wireguard-windows/updater, branch master

updater: drain the entire response when fetching version list

2026-05-19T15:37:20Z

WinHTTP can short-read across TLS or HTTP chunk boundaries, so a single Read may truncate the signed file list. Signify verification catches it, but the user sees a spurious update-check failure instead of a successful fetch. Signed-off-by: Jason A. Donenfeld

updater,fetcher: disable HTTP/3

2026-05-06T13:42:37Z

We had reports of it failing. Reported-by: Ben Yoder Signed-off-by: Jason A. Donenfeld

global: regenerate syscall code from latest x/sys/windows wrapper

2026-04-20T10:57:17Z

Signed-off-by: Jason A. Donenfeld

updater: response is unsigned anyway

2026-04-16T13:26:26Z

Signed-off-by: Jason A. Donenfeld

updater: fix error message text to specify hex, not base64

2026-04-16T13:26:26Z

Signed-off-by: Jason A. Donenfeld

updater: read proper number of numbers

2026-04-16T13:26:26Z

There's no way it'd be valid anyway, but this index is for utf16 chars, not utf8 chars. Signed-off-by: Jason A. Donenfeld

updater: more gracefully handle read errors in winhttp

2026-04-16T13:26:26Z

Otherwise we keep trying infinitely. Signed-off-by: Jason A. Donenfeld

updater: do not return swallowed error

2026-04-10T16:25:35Z

Before we were still returning the swallowed error. Signed-off-by: Jason A. Donenfeld

updater,fetcher: enable http/3 opportunistically

2026-03-30T12:01:41Z

Signed-off-by: Jason A. Donenfeld

updater: do not verify EV status

2026-03-23T13:48:11Z

We'll keep signing with EV. But this is not a security check. Anybody can add an EV signature. It's not very expensive to do. And we've never checked that it's actually _our_ signature. For that, there's the normal ed25519-based mechanism, which is a lot nicer and faster. Signed-off-by: Jason A. Donenfeld