wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Kernel drops fewer messages in sendsyslog(2), adapt syslogd(8)	bluhm	2021-03-09	1	-1/+7
\| \| \| \| \|	tests. Kernel stashes logs temporarily, test it. Fix some races in existing tests.
*	Fix some races in syslogd tests. Fewer handshakes in TLS 1.3 make	bluhm	2020-11-06	1	-2/+3
\| \| \| \|	the error messages and behavior less deterministic.
*	With TLS 1.2 the step by step handshake created precise error	bluhm	2020-10-16	1	-1/+5
\| \| \| \| \| \| \| \| \| \|	conditions. TLS 1.3 shortens the handshake, so some errors cannot be reported properly to the other side. Instead the connection is closed and the other side receives a SIGPIPE when it tries to write the next TLS protocol message. Ignore this SIGPIPE signal in TLS client and server and adapt error messages when grepping the log files. discussed with tb@ and jsing@
*	If KTRACE environment is set, generate ktrace output also for client	bluhm	2020-07-24	1	-2/+4
\| \| \| \|	and server. Together with the syslogd ktrace this helps debugging.
*	Check that the hostname added by syslogd -h in file and server log	bluhm	2017-09-13	1	-2/+4
\| \| \| \| \|	is correct. Use generic redo functions. Do syntax check for all Perl files.
*	Test syslogd(8) "last message repeated" feature and -r option.	bluhm	2017-04-17	1	-2/+2
\|
*	Test listening on multiple sockets simultaneously.	bluhm	2017-01-02	1	-1/+3
\|
*	The TCP socket buffer size for syslogd has changed. Adapt tests	bluhm	2016-09-23	1	-1/+11
\| \| \| \| \| \|	where we count the dropped messages. A different number gets stuck in the kernel buffers now which is not included in the syslogd statistics.
*	Test syslogd TLS client certificate validation.	bluhm	2016-09-21	1	-2/+9
\|
*	Test that rsyslogd can send over TLS to OpenBSD syslogd.	bluhm	2015-11-02	1	-1/+7
\|
*	Add tests for syslogd TLS accept and receive encrypted messages.	bluhm	2015-10-09	1	-4/+25
\|
*	Test that syslogd can process 8 full size messages from sendsyslog(2)	bluhm	2015-09-09	1	-2/+3
\| \| \| \|	or UDP socket or UNIX domain socket at once.
*	Test that long syslog messages are truncated correctly.	bluhm	2015-02-02	1	-11/+22
\|
*	Add tests for syslogd sending and receiving over IPv6 sockets.	bluhm	2014-08-25	1	-2/+2
\|
*	Run syslogd regressions tests. As only one syslogd can run per	bluhm	2014-08-20	1	-0/+62
	machine, each test kills any syslogd first. At the end the system's syslogd gets restarted. The test framework runs a client, and a server, and a syslogd. The messages are passed via the log socket or via UDP from the client to syslogd. From there UDP transport is used to reach the server. All processes write log files where the message has to show up. The test arguments are kept in the args-*.pl files. The content of a log file, the data sent to a pipe process and what the server received are checked. The invocation of the sendsyslog(2) syscall is checked with ktrace, the open file descriptors of syslogd are checked with fstat.