wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update to libevent 1.3e while retaining our local changes.	brad	2008-05-02	1	-81/+66
\| \| \| \| \|	"No objection" millert@ "the diff looks and works fine" reyk@
*	Update to libevent-1.3b while retaining our local changes. beck@ OK	millert	2007-03-19	1	-5/+3
\|
*	make write-end of signal socketpair non-blocking.	deraadt	2005-12-02	1	-1/+3
\| \| \| \| \| \| \| \| \| \|	every signal received writes 1 byte to the socketpair. if you are outside the libevent main loop too long, the socketpair might fill up. that write would then block, in a signal handler. related to this, yesterdy we changed the signal handler to not trash errno. as for the read end, there will be multiple libevent reads off the socketpair (100 bytes at a time) until the socketpair is empty again ok provos
*	lookup out of evsigcaught[] must be sig_atomic_t too	deraadt	2005-12-02	1	-2/+2
\|
*	save errno in signal handler since it does a system call	deraadt	2005-12-01	1	-4/+8
\| \| \| \| \|	only access sig_atomic_t variables, to make it further save ok aaron
*	zap trailing whitespaces, no binary change	grunk	2005-07-02	1	-2/+2
\| \| \| \|	ok brad@ beck@
*	update to libevent 1.0c; keep local changes	brad	2005-04-22	1	-16/+58
\| \| \| \| \| \| \| \| \| \|	no shared lib so no ABI/API check is necessary thanks to Alexander von Gernler for submitting another diff in an attempt to update libevent and for a use-after-free fix. ok henning@ deraadt@
*	backout. not discussed, and very wrong. bad brad	deraadt	2005-04-19	1	-58/+16
\|
*	update to libevent 1.0c; keep local changes	brad	2005-04-19	1	-16/+58
\|
*	update to libevent 0.8; keep local changes	brad	2004-04-28	1	-11/+9
\| \| \| \|	ok markus@
*	get rid of config.h; ok miod@, millert@, deraadt@	markus	2003-07-10	1	-1/+3
\|
*	update to libevent-0.7a.tar.gz; keep local changes	markus	2003-07-09	1	-0/+164