On Tue, May 19, 2020, Matt Caswell wrote:
> > SSL_accept:error in TLSv1.3 early data
> This comes from this code in the info callback which you lifted from s_cb.c:
> Please could you modify this as follows:
> +ERR_print_errors(bio_err);
That's basically already in the code:
while ((l
On 19/05/2020 11:49, Claus Assmann wrote:
> On Mon, May 18, 2020, Viktor Dukhovni wrote:
>
>> I'll strongly second Matt's request for a PCAP file.
>
> If tcpdump is "good enough" then that should be attached.
> If wireshark and some TLS decoding is needed, then I need
> some time to figure
On Mon, May 18, 2020, Viktor Dukhovni wrote:
> I'll strongly second Matt's request for a PCAP file.
If tcpdump is "good enough" then that should be attached.
If wireshark and some TLS decoding is needed, then I need
some time to figure that out.
> The client trace looks rather odd, why is
On Tue, May 19, 2020, Jan Just Keijser wrote:
> FWIW: adding TLS 1.3 support to my EAP-TLS code got me stumped for a while as
> well. I eventually added up the following snippet:
> SSL_CTX_set_session_cache_mode(ctx, SSL_SESS_CACHE_CLIENT |
> SSL_SESS_CACHE_NO_INTERNAL_STORE);
>
Hi Claus,
On 18/05/20 20:59, Claus Assmann wrote:
On Mon, May 18, 2020, Alexander Gryanko wrote:
[thanks for the hints, I will try that ASAP]
But first of all, check your cert type. Looks like you are using non-RSA
cert which is not supported by S8.
As I wrote: it works fine if I don't use
