Replace deprecated IO::Socket::INET6 with IO::Socket::IP.

With TLS 1.2 the step by step handshake created precise error
conditions. TLS 1.3 shortens the handshake, so some errors cannot
be reported properly to the other side. Instead the connection is
clo

With TLS 1.2 the step by step handshake created precise error
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@

show more ...

If KTRACE environment is set, generate ktrace output also for client
and server. Together with the syslogd ktrace this helps debugging.

Mark the IO::Socket::SSL server socket with SSL_server to avoid
OCSP error messages.

The TCP socket buffer size for syslogd has changed. Adapt tests
where we count the dropped messages. A different number gets stuck
in the kernel buffers now which is not included in the syslogd
sta

The TCP socket buffer size for syslogd has changed. Adapt tests
where we count the dropped messages. A different number gets stuck
in the kernel buffers now which is not included in the syslogd
statistics.

show more ...

Test syslogd TLS client certificate validation.

Add regression tests for syslogd TLS client certificates.

Add tests that call the syscalls sendsyslog(2) and sendsyslog2(2)
directly.

Add a test where the TLS handshake fails because of null ciphers.

Add a test for syslogd that reconnects to a TCP syslog server after
an established connection has been closed.

Create CA and certificates for TLS tests consistently. Better
logging of SSL errors. Do not import unneeded Socket constants.

Add regression tests where OpenBSD syslogd is sending messages to
rsyslogd from ports. If the rsyslog package is installed, rsyslogd
is used as drain to test interoperability. This will be especial

Add regression tests where OpenBSD syslogd is sending messages to
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.

show more ...

Add tests for syslogd sending and receiving over IPv6 sockets.

Run syslogd regressions tests. As only one syslogd can run per
machine, each test kills any syslogd first. At the end the system's
syslogd gets restarted.
The test framework runs a client, and a se

Run syslogd regressions tests. As only one syslogd can run per
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.

show more ...