Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-21 Thread Matt Caswell
On 20/06/18 23:17, Yann Ylavic wrote: > They are not really transactions since the client isn't supposed to > send anything in between, This is not the case. The client can be sending data before, during/in between, and after the period that the server is issuing tickets. Matt --

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Dennis Clarke
On 06/20/2018 08:46 PM, Salz, Rich via openssl-users wrote: Thanks, it does not happen with mozzilla implementation (tls13.crypto.mozilla.org), is this openssl specific or part of the specification? The specification allows a server to send one or more tickets, at its

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Yann Ylavic
On Thu, Jun 21, 2018 at 12:17 AM, Yann Ylavic wrote: > > Right but if s_server had handled SSL_CB_HANDSHAKE_START/DONE in its > info callback (like s_client), you'd see "SSL negotiation finished > successfully" after each ticket, even if the server knows (or could). Hm, actually I tried that and

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Yann Ylavic
On Wed, Jun 20, 2018 at 11:49 PM, Matt Caswell wrote: > > On 20/06/18 22:31, Yann Ylavic wrote: >> >> but I wonder if >> announcing the start then end of the same handshake multiple times >> could/should be avoided (i.e. handshake ends after last ticket only)? > > They really are individual

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Matt Caswell
On 20/06/18 22:31, Yann Ylavic wrote: >>>Thanks, it does not happen with mozzilla implementation >> (tls13.crypto.mozilla.org), is this openssl specific or part of the >> specification? >> >> The specification allows a server to send one or more tickets, at its >> discretion. > >

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Yann Ylavic
>>Thanks, it does not happen with mozzilla implementation > (tls13.crypto.mozilla.org), is this openssl specific or part of the > specification? > > The specification allows a server to send one or more tickets, at its > discretion. OK thanks, I could find the relevant PR and

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Salz, Rich via openssl-users
>Thanks, it does not happen with mozzilla implementation (tls13.crypto.mozilla.org), is this openssl specific or part of the specification? The specification allows a server to send one or more tickets, at its discretion. -- openssl-users mailing list To unsubscribe:

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Yann Ylavic
On Wed, Jun 20, 2018 at 8:59 PM, Viktor Dukhovni wrote: > > >> On Jun 20, 2018, at 2:55 PM, Yann Ylavic wrote: >> >> Hi, >> >> connecting s_client to s_server with TLS 1.3 seems to cause two >> successive session tickets to be sent by the server (see below). >> >> Is this expected? > > Yes.

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Salz, Rich via openssl-users
>connecting s_client to s_server with TLS 1.3 seems to cause two successive session tickets to be sent by the server (see below). >Is this expected? Yes. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Viktor Dukhovni
> On Jun 20, 2018, at 2:55 PM, Yann Ylavic wrote: > > Hi, > > connecting s_client to s_server with TLS 1.3 seems to cause two > successive session tickets to be sent by the server (see below). > > Is this expected? Yes. -- Viktor. -- openssl-users mailing list To unsubscribe:

[openssl-users] Double TLS 1.3 session ticket?

2018-06-20 Thread Yann Ylavic
Hi, connecting s_client to s_server with TLS 1.3 seems to cause two successive session tickets to be sent by the server (see below). Is this expected? $ openssl s_server -accept 127.0.0.1:4443 -cert ... -key ... -state Using default temp DH parameters ACCEPT SSL_accept:before SSL initialization