Re: What's the rationale behind ssl-trace not being built by default?

2021-06-07 Thread Arran Cudbard-Bell
> On Jun 7, 2021, at 4:57 PM, Matt Caswell wrote: > > > > On 07/06/2021 20:01, Arran Cudbard-Bell wrote: >> The tables to convert extension IDs and compression methods to humanly >> readable names are not available outside ssl/t1_trace.c. >> SSL_trace() itself produces reams of helpful

Re: What's the rationale behind ssl-trace not being built by default?

2021-06-07 Thread Matt Caswell
On 07/06/2021 20:01, Arran Cudbard-Bell wrote: The tables to convert extension IDs and compression methods to humanly readable names are not available outside ssl/t1_trace.c. SSL_trace() itself produces reams of helpful information as handshakes progress, and is particularly useful for

What's the rationale behind ssl-trace not being built by default?

2021-06-07 Thread Arran Cudbard-Bell
The tables to convert extension IDs and compression methods to humanly readable names are not available outside ssl/t1_trace.c. SSL_trace() itself produces reams of helpful information as handshakes progress, and is particularly useful for dealing with encrypted handshakes, where wireshark et

Compile opensslß1.1.1k on CentOS8

2021-06-07 Thread Lothar Belle
Hi, recently I compiled openssl-1.1.1k on CentOS-8 but when I am using libcrypto.so.1.1 I get errors like: libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b Obviously RedHat added additional features into there own libraries, but using the same version/naming. See