Re: enforce ALPN overlap?

2021-06-09 Thread Tomas Mraz
but leave the connection open: > > [...] > New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 > Server public key is 2048 bit > Secure Renegotiation IS NOT supported > Compression: NONE > Expansion: NONE > No ALPN negotiated > Early data was not sent > [...] > --- > read R BLOCK >

Re: enforce ALPN overlap?

2021-06-09 Thread Jan Schaumann via openssl-users
Jan Schaumann via openssl-users wrote: > New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Same for TLS 1.2, btw. (I accidentally copied the default output when writing the email.) -Jan

enforce ALPN overlap?

2021-06-09 Thread Jan Schaumann via openssl-users
E Expansion: NONE No ALPN negotiated Early data was not sent [...] --- read R BLOCK In Go, a recent commit changed their behavior to enforce ALPN overlap: https://github.com/golang/go/commit/90d6bbbe42c15d444c1da0a1c293192d6f735a8e Is there any plan or consideration to follow that approach? -Jan