wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

Age	Commit message (Collapse)	Author	Files	Lines
2019-05-10	Regress libedit needs header files generated during src libedit	bluhm	2	-11/+10
	build. Improve dependencies to resolve this more reliably. requested by claudio@
2017-07-07	Remove all references to "make depend" from regress.	bluhm	2	-4/+2

2017-07-05	Implement the generated dependency with a stamp file to avoid needless	bluhm	10	-12/+17
	recompiling of the test programs. Add some RCS ids.
2017-07-04	Fix building the libedit regress programs.	bluhm	2	-7/+5

2017-07-03	Generate source and header files for regress on demand.	bluhm	4	-25/+18
	OK espie@
2017-02-25	Add missing includes to avoid implicit function declarations.	jsg	1	-0/+1

2016-09-18	The libedit regress tests require header files generated during the	bluhm	3	-11/+18
	build. Add a dependency to run make depend in /usr/src/lib/libedit. Problem found by otto@; OK schwarze@
2016-09-08	fix test after the errno reshuffle; ok swarsche@	otto	1	-2/+2

2016-09-06	These tests didn't work without setting READLINE because we don't	schwarze	2	-3/+3
	install <editline/readline.h> by default; make them work by using the copy from the source tree. Issue reported by otto@.
2016-06-01	Add detailed error messages and restructure to make the individual	schwarze	1	-112/+118
	test functions shorter and easier to understand. The total number of lines remains unchanged.
2016-06-01	Test history_get() return value;	schwarze	1	-0/+30
	from Bastian Maerkisch <bmaerkisch at web dot de>.
2016-05-31	The argument of remove_history() only counts existing entries,	schwarze	1	-0/+7
	not those that were previously deleted.
2016-05-31	Style unification and whitespace cleanup, in part suggested by	schwarze	1	-35/+36
	Christian Heckendorf. No functional change.
2016-05-25	deal with the el_errno -> read_errno cleanup, read.c rev. 1.43	schwarze	2	-7/+5

2016-05-22	cope with simplified chared/read interface	schwarze	2	-8/+3

2016-05-10	Enable the readline(3) regression test provided by Bastian Maerkisch,	schwarze	1	-2/+2
	all bugs tested so far have been fixed.
2016-05-10	adapt to recently changed internal interface of read_getcmd()	schwarze	1	-3/+3

2016-05-06	A few regression tests for libedit readline(3) compat code.	schwarze	2	-0/+276
	Not linked to the build for now because these tests still fail for our libedit and because readline compat is not enabled in our build. Test suite written by Bastian Maerkisch <bmaerkisch@web.de>. KNF and some minor tweaks by me.
2016-04-11	cope with the deletion of Char, use wchar_t	schwarze	5	-14/+18

2016-04-11	drop -DWIDECHAR, it's no longer needed	schwarze	3	-6/+3

2016-03-22	initialize el_state.metanext before testing read_getcmd()	schwarze	1	-0/+1

2016-03-20	Fix the CHARSET_IS_UTF8 case in read_char().	schwarze	1	-3/+2
	For now, this mainly help programs explicitly using wide-character functions like el_wgetc(3) and el_wgets(3). 1. After reading an invalid byte sequence, do not throw away additional valid bytes; fix by me using mbrtowc(3), obsoleting utf8_islead(). 2. When read(2) returns EOF, return that information to the caller, do not prod on and potentially access garbage data in the buffer; from Linas Vepstas via NetBSD read.c rev. 1.70 2013/05/27. 3. After read__fixio() failure, restore errno to the one set by read(); from Steffen Nurpmeso via NetBSD read.c rev. 1.68 2012/09/10. 4. After read__fixio() success, restore errno to the initial state upon function entry; fix by me. OK czarkoff@. Also committed to NetBSD.
2016-03-01	After the bugfix in libedit/chared.c rev. 1.17,	schwarze	1	-3/+2
	chared unit tests now work, so enable them.
2016-03-01	More unit tests for libedit.	schwarze	13	-42/+458
	Those that still fail are commented out in the Makefiles for now; i have patches for them.
2016-02-11	Test the C/POSIX locale too, in addition to UTF-8.	schwarze	2	-17/+37

2016-02-11	Slowly start a unit test suite for libedit; Christos is right that	schwarze	3	-0/+178
	fiddling with the internals of that code is dangerous without it. Intentionally not linked to the build yet, because many of the tests still fail: The related bugfixes are too intrusive right now and will go in after unlock.