wireguard-windows - WireGuard client for Windows

	Commit message (Collapse)	Author	Age	Files	Lines
*	build: bump golang version to 1.15.5	Jason A. Donenfeld	2020-11-19	8	-26/+26
\| \| \| \|	Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	go-patches: drop CreateWaitableTimerEx	Jason A. Donenfeld	2020-11-16	1	-406/+0
\| \| \| \| \| \|	It causes mysterious crashes. We'll revisit for 1.16. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	go-patches: support 8 callback arguments on arm	Jason A. Donenfeld	2020-11-13	9	-8/+68
\| \| \| \|	Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	build: add linker patches for llvm-rc	Jason A. Donenfeld	2020-11-13	8	-77/+545
\| \| \| \|	Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	go: update to 1.15.2	Jason A. Donenfeld	2020-09-11	2	-8/+148
\| \| \| \|	Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	go: use highres timer on newer Windows 10	Jason A. Donenfeld	2020-08-18	1	-0/+395
\| \| \| \| \| \| \| \| \| \| \|	WireGuard makes heavy use of timers, and the low precision of Windows timers as currently used in Go isn't very nice, and also seems to result in worse battery life because of the gross winmm.dll timerBeginPeriod trick. John Starks suggested this new parameter to make a high resolution timer on NT, and Alex implemented it, so import Alex's test patch to see how this goes. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
*	go: remove exit(2) from ctrl+c handler	Jason A. Donenfeld	2020-08-18	1	-0/+44
	Simon reported that he'd have hard to diagnose exits at boot time with Go 1.14 but not with 1.13. It turns out that the ctrl+c handler added by 1.14 at some point in the cycle includes some wrong behavior forcing exits on various services signals. In an attempt to address this, this commit backports my patch from 1.16 that removes this errant path. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>