wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	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.
*	Mark the IO::Socket::SSL server socket with SSL_server to avoid	bluhm	2017-01-31	1	-1/+2
\| \| \| \|	OCSP error messages.
*	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	-5/+6
\|
*	Add regression tests for syslogd TLS client certificates.	bluhm	2016-07-12	1	-6/+10
\|
*	Add tests that call the syscalls sendsyslog(2) and sendsyslog2(2)	bluhm	2015-12-04	1	-3/+3
\| \| \| \|	directly.
*	Add a test where the TLS handshake fails because of null ciphers.	bluhm	2015-01-28	1	-1/+7
\|
*	Add a test for syslogd that reconnects to a TCP syslog server after	bluhm	2015-01-15	1	-2/+22
\| \| \| \|	an established connection has been closed.
*	Create CA and certificates for TLS tests consistently. Better	bluhm	2014-12-31	1	-6/+6
\| \| \| \|	logging of SSL errors. Do not import unneeded Socket constants.
*	Add regression tests where OpenBSD syslogd is sending messages to	bluhm	2014-12-28	1	-6/+6
\| \| \| \| \| \|	rsyslogd from ports. If the rsyslog package is installed, rsyslogd is used as drain to test interoperability. This will be especially useful for syslog via TCP and TLS.
*	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/+83
	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.