I noticed that some regress test fail since February 7: - run-args-server-tls-reconnect.pl - run-args-server-tls-tcp.pl - run-args-tls-cipher-null.pl
(http://bluhm.genua.de/regress/results/regress-ot6.html) It is related to changes in LibreSSL. Is this intended? Should the regress tests be adapted? Below diff makes two of the tests succeed. Remi Index: args-server-tls-tcp.pl =================================================================== RCS file: /cvs/src/regress/usr.sbin/syslogd/args-server-tls-tcp.pl,v retrieving revision 1.10 diff -u -p -r1.10 args-server-tls-tcp.pl --- args-server-tls-tcp.pl 22 May 2018 15:01:16 -0000 1.10 +++ args-server-tls-tcp.pl 2 Mar 2020 21:30:01 -0000 @@ -41,7 +41,7 @@ our %args = ( loggrep => { qr/syslogd\[\d+\]: loghost .* connection error: /. qr/handshake failed: error:.*:SSL routines:/. - qr/CONNECT_CR_SRVR_HELLO:wrong version number/ => 1, + qr/\(UNKNOWN\)SSL_internal:unknown failure occurred/ => 1, }, }, ); Index: args-tls-cipher-null.pl =================================================================== RCS file: /cvs/src/regress/usr.sbin/syslogd/args-tls-cipher-null.pl,v retrieving revision 1.8 diff -u -p -r1.8 args-tls-cipher-null.pl --- args-tls-cipher-null.pl 5 Apr 2017 22:32:14 -0000 1.8 +++ args-tls-cipher-null.pl 2 Mar 2020 22:22:32 -0000 @@ -16,7 +16,7 @@ our %args = ( qr/Logging to FORWTLS \@tls:\/\/localhost:\d+/ => '>=4', qr/syslogd\[\d+\]: loghost .* connection error: /. qr/handshake failed: error:.*:SSL routines:/. - qr/CONNECT_CR_SRVR_HELLO:sslv3 alert handshake failure/ => 1, + qr/ST_CONNECT:sslv3 alert handshake failure/ => 1, get_testgrep() => 1, }, cacrt => "ca.crt",
