Searched hist:d8bc0d06 (Results 1 – 5 of 5) sorted by relevance
| /openbsd/regress/usr.sbin/syslogd/ |
| H A D | args-server-tls-error.pl | d8bc0d06 Fri Oct 16 22:46:45 GMT 2020 bluhm <bluhm@openbsd.org> 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@
|
| H A D | args-client-tls-fake.pl | d8bc0d06 Fri Oct 16 22:46:45 GMT 2020 bluhm <bluhm@openbsd.org> 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@
|
| H A D | args-tls-cafile-fake.pl | d8bc0d06 Fri Oct 16 22:46:45 GMT 2020 bluhm <bluhm@openbsd.org> 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@
|
| H A D | Server.pm | d8bc0d06 Fri Oct 16 22:46:45 GMT 2020 bluhm <bluhm@openbsd.org> 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@
|
| H A D | Client.pm | d8bc0d06 Fri Oct 16 22:46:45 GMT 2020 bluhm <bluhm@openbsd.org> 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@
|