On Tue, Feb 05, 2019 at 02:43:03PM -0800, Sam Roberts wrote:
> I tracked down my problem, its due to a change in the relative order
> of handshake completion (as detected by the info callback, anyhow),
> and the callback to SSL_CTX_set_tlsext_ticket_key_cb().
>
> With TLS1.2, I can rotate ticket
I tracked down my problem, its due to a change in the relative order
of handshake completion (as detected by the info callback, anyhow),
and the callback to SSL_CTX_set_tlsext_ticket_key_cb().
With TLS1.2, I can rotate ticket keys on the server when the handshake
completes, and they will only appl
> On Feb 5, 2019, at 10:41 AM, Sam Roberts wrote:
>
>> However, because in TLS 1.3, session
>> tickets are sent *after* the completion of the handshake, it is
>> possible that the session handle you're saving is the one that does
>> not yet have any associated tickets, because they've not yet bee
On Mon, Feb 4, 2019 at 9:46 PM Viktor Dukhovni
wrote:
> On Mon, Feb 04, 2019 at 03:54:48PM -0800, Sam Roberts wrote:
> However, because in TLS 1.3, session
> tickets are sent *after* the completion of the handshake, it is
> possible that the session handle you're saving is the one that does
> not
On 04/02/2019 23:54, Sam Roberts wrote:
> And is it possible that this is different for TLS1.2 and 1.3?
>
> Using TLS1.3, SSL_session_reused() is always returning false, I'm not
> sure if that's because I'm doing something else wrong, and the ticket
> is not being accepted and a full handshake
