On 8/24/2018 4:08 PM, Simone Bordet wrote:
However, on the server-side the session ID is the same, so I am
confused by the fact that on the client the session has been resumed,
but it has a different ID.
When the client receives a NewSessionTicket message, it copies the
current SSLSession and
Hi,
On Fri, Aug 24, 2018 at 8:54 PM Adam Petcher wrote:
> On 8/23/2018 3:28 PM, Simone Bordet wrote:
> > Hi,
> >
> > The code below reproduces a bug where session resumption is tested.
> > Turns out that session resumption does happen on the client and on the
> > server, but on the client the ses
Thanks for testing this. I developed most of the NewSessionTicket/PSK
code. See below for my comments.
On 8/23/2018 3:28 PM, Simone Bordet wrote:
Hi,
The code below reproduces a bug where session resumption is tested.
Turns out that session resumption does happen on the client and on the
serv
Hi,
The code below reproduces a bug where session resumption is tested.
Turns out that session resumption does happen on the client and on the
server, but on the client the session id is not replaced with the
resumed session id (while it is on the server).
The code prints:
session1 = Session(153
