Now that syslogd(8) supports SSL shutdown when the TLS connection
terminates, do SSL shutdown in the test client. This will detect
SSL handshake errors also with TLS 1.3 if the CA of the client
cert

Now that syslogd(8) supports SSL shutdown when the TLS connection
terminates, do SSL shutdown in the test client. This will detect
SSL handshake errors also with TLS 1.3 if the CA of the client
certificate is invalid.
test races reported by anton@; debugged with Carsten Arzig

show more ...

Fix some races in syslogd tests. Fewer handshakes in TLS 1.3 make
the error messages and behavior less deterministic.

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 ...

Syslogd's debug and error messages have changed a bit, adapt test.

Adapt regex in syslogd test to the new shiny libssl error messages.

The libssl and libcrypto error messages have changed. Adapt the
regex for the expected output in the log files.

The TLS error message depends on the generated fake certificate.
Make the test's expectation less strict.

Test syslogd TLS client certificate validation.