wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	update to 1.6.0 with official syslog support backported from the 1.7 branch	robert	2014-06-12	131	-2645/+7704
\| \| \| \|	tested by several, ok sthen@
*	Allow -p prefix to override user home directory for chroot() (Like	chris	2014-05-10	1	-5/+12
\| \| \| \| \| \| \| \|	openbsd-apache ServerRoot behavior) Work continues to unify nginx behavior (Principle of Least Astonishment) ok henning@
*	Allow nginx to chroot to a directory other than /var/www	chris	2014-05-10	4	-6/+24
\| \| \| \|	ok henning@
*	nginx dudes unrolled SSL_OP_ALL by hand so we also have to delete	tedu	2014-04-29	1	-2/+0
\| \| \| \|	SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS from here to benefit. ok miod
*	bugfix and security update to 1.4.7:	robert	2014-03-29	3	-3/+14
\| \| \| \| \| \|	CVE-2014-0133 does not affect OpenBSD because SPDY is not enabled ok florian@
*	bugfix update to 1.4.6	robert	2014-03-11	7	-68/+69
\|
*	security update to nginx 1.4.4 which fixes CVE-2013-4547	robert	2013-11-21	2	-2/+4
\|
*	bugfix update to 1.4.3	robert	2013-10-18	10	-20/+19
\|
*	bugfix update to 1.4.2	robert	2013-08-08	10	-24/+59
\|
*	Put back r1.7	miod	2013-06-23	1	-0/+4
\|
*	update the internal pcre library to 8.33	robert	2013-06-14	7	-291/+562
\|
*	update to nginx-1.4.1 and enable the SPDY module by default	robert	2013-06-01	75	-1349/+10796
\|
*	update to 1.2.9; several bugfixes and security fix for CVE-2013-2070	robert	2013-05-15	22	-55/+80
\|
*	decl's before code. please push to upstream.	deraadt	2013-03-22	1	-4/+4
\|
*	re-add a build fix for vax that was overwritten by the update	robert	2013-03-21	1	-1/+1
\|
*	update to 1.2.7	robert	2013-03-17	41	-430/+1418
\|
*	disable symbol visibility on vax in order to unbreak the build	robert	2013-02-14	2	-2/+8
\|
*	update the internal pcre to 8.32	robert	2013-02-10	14	-4577/+5629
\|
*	update to nginx-1.2.6	robert	2013-01-14	14	-76/+188
\|
*	If compiling with gcc 3, initialize a local variable to prevent -Wuninitialized	miod	2012-12-01	1	-0/+3
\| \| \| \|	from firing a false positive; ok robert@
*	update to 1.2.5	robert	2012-11-14	18	-71/+211
\|
*	use the default SYSLOG_FACILITY definition which is LOCAL5	robert	2012-10-28	1	-1/+1
\| \| \| \|	noted by ajacoutot@
*	strip the chroot path from auth_basic_user_file if necessary	robert	2012-10-28	1	-0/+4
\|
*	unbreak build on vax by initializing a variable	robert	2012-10-28	1	-5/+5
\|
*	add syslog support to nginx	robert	2012-10-25	6	-3/+439
\|
*	update to 1.2.4	robert	2012-10-08	28	-96/+138
\|
*	merge in pcre-8.31	robert	2012-08-21	10	-2612/+3032
\|
*	update to nginx-1.2.3	robert	2012-08-21	28	-99/+192
\|
*	update to 1.2.2 and start using /var/www/cache instead of /var/www/tmp	robert	2012-07-07	30	-141/+695
\|
*	use /var/www/tmp/ for the temp directories even if not chrooted	robert	2012-06-26	1	-13/+12
\|
*	update to 1.2.1	robert	2012-06-13	24	-430/+579
\|
*	move the chroot path stripping into a different function to make sure	robert	2012-05-15	1	-4/+4
\| \| \| \| \|	that we always include aliases as well, to make "user directories work" tested by jasper@ and sthen@
*	backport changeset 4619 from nginx trunk:	robert	2012-05-13	2	-6/+46
\| \| \| \| \| \| \| \| \| \| \| \|	Accept moderation in case of EMFILE/ENFILE. In case of EMFILE/ENFILE returned from accept() we disable accept events, and (in case of no accept mutex used) arm timer to re-enable them later. With accept mutex we just drop it, and rely on normal accept mutex handling to re-enable accept events once it's acquired again. As we now handle errors in question, logging level was changed to "crit" (instead of "alert" used for unknown errors).
*	update to nginx-1.2.0	robert	2012-05-13	118	-1588/+7757
\|
*	update to 1.0.15	robert	2012-04-14	3	-71/+213
\|
*	use a shared stripping function for chroot and make sure	robert	2012-04-12	4	-14/+16
\| \| \| \| \|	that the path starts with the chroot prefix before doing anything with it
*	Set the correct string lengths when stripping the chroot prefix	robert	2012-04-04	3	-12/+10
\| \| \| \| \| \|	from the paths because ngx_str_set() does not set it correctly for us. This change also avoid a use after free() case which was discovered by sthen@ Based on a diff from Steffen Daode Nurpmeso, tested by me and sthen@
*	make sure we strip the chroot prefix from all root variables, not just the	robert	2012-04-02	1	-7/+8
\| \| \| \|	first one
*	bring back an overwritten change which is essential for the chrooted	robert	2012-04-02	1	-1/+9
\| \| \| \|	version to strip the chroot prefix from root paths
*	stupid cvs (dir has 'core' in the name...)	sthen	2012-03-15	1	-2/+2
\|
*	resolve conflicts	sthen	2012-03-15	6	-11/+31
\|
*	update to 1.0.13	robert	2012-03-06	37	-243/+236
\|
*	create the tmp dirs nginx needs for doing proxying inside the chroot	robert	2012-02-22	1	-8/+20
\| \| \| \|	because these get created before the actual chroot happens
*	update pcre to 8.30 to be in sync with ports	robert	2012-02-18	15	-1706/+2756
\|
*	update to 1.0.12	robert	2012-02-18	247	-249/+613
\|
*	update to nginx-1.0.11	robert	2012-01-05	26	-284/+535
\|
*	merge pcre-8.21	robert	2011-12-14	6	-452/+809
\|
*	Update to nginx 1.0.10. Bugs fixed include a segmentation fault in a worker	sthen	2011-11-15	5	-12/+14
\| \| \| \|	process if the resolver receives a large DNS response. OK robert@
*	sync to pcre 8.20	robert	2011-11-12	8	-186/+506
\|
*	update to 1.0.9	robert	2011-11-12	43	-224/+389
\|