Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-18 Thread J Decker
On Mon, Feb 18, 2019 at 2:18 PM Jakob Bohm via openssl-users < openssl-users@openssl.org> wrote: > On 17/02/2019 14:26, Matt Caswell wrote: > > On 16/02/2019 05:04, Sam Roberts wrote: > >> On Fri, Feb 15, 2019 at 3:35 PM Matt Caswell wrote: > >>> On 15/02/2019 20:32, Viktor Dukhovni wrote: >

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-18 Thread Jakob Bohm via openssl-users
On 17/02/2019 14:26, Matt Caswell wrote: On 16/02/2019 05:04, Sam Roberts wrote: On Fri, Feb 15, 2019 at 3:35 PM Matt Caswell wrote: On 15/02/2019 20:32, Viktor Dukhovni wrote: On Feb 15, 2019, at 12:11 PM, Sam Roberts wrote: OpenSSL could delay the actual shutdown until we're about to

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-17 Thread Matt Caswell
On 16/02/2019 05:04, Sam Roberts wrote: > On Fri, Feb 15, 2019 at 3:35 PM Matt Caswell wrote: >> On 15/02/2019 20:32, Viktor Dukhovni wrote: On Feb 15, 2019, at 12:11 PM, Sam Roberts wrote: >>> OpenSSL could delay the actual shutdown until we're about to return >>> from the SSL_accept()

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-15 Thread Sam Roberts
On Fri, Feb 15, 2019 at 3:35 PM Matt Caswell wrote: > On 15/02/2019 20:32, Viktor Dukhovni wrote: > >> On Feb 15, 2019, at 12:11 PM, Sam Roberts wrote: > > OpenSSL could delay the actual shutdown until we're about to return > > from the SSL_accept() that invoked the callback. That is

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-15 Thread Matt Caswell
On 15/02/2019 20:32, Viktor Dukhovni wrote: >> On Feb 15, 2019, at 12:11 PM, Sam Roberts wrote: >> >> In particular, I'm getting a close_notify alert, followed by two >> NewSessionTickets from the server. >> >> The does SSL_read()/SSL_get_error(), it is returning >> SSL_ERROR_ZERO_RETURN, so I

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-15 Thread Viktor Dukhovni
> On Feb 15, 2019, at 12:11 PM, Sam Roberts wrote: > > In particular, I'm getting a close_notify alert, followed by two > NewSessionTickets from the server. > > The does SSL_read()/SSL_get_error(), it is returning > SSL_ERROR_ZERO_RETURN, so I stop calling SSL_read(). > > However, that means

Re: [openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-15 Thread Matt Caswell
On 14/02/2019 22:51, Sam Roberts wrote: > In particular, I'm getting a close_notify alert, followed by two > NewSessionTickets from the server. This sounds like a bug somewhere. Once you have close_notify you shouldn't expect anything else. Is that an OpenSSL server? Matt -- openssl-users

[openssl-users] when should client stop calling SSL_read to get TLS1.3 session tickets after the close_notify?

2019-02-14 Thread Sam Roberts
In particular, I'm getting a close_notify alert, followed by two NewSessionTickets from the server. The does SSL_read()/SSL_get_error(), it is returning SSL_ERROR_ZERO_RETURN, so I stop calling SSL_read(). However, that means that the NewSessionTickets aren't seen, so I don't get the callbacks