Thanks Salz and Benjamin for your feedback. Indeed my Wireshark version was unable to decode TLS 1.3. I got an update from the shared link.
I had one doubt about the server side session caching. I read that server side server caching is disabled by default. Then, how is session resumption possible using session identifiers because that is is stateful resumption as I have understood with servers maintaining the session info. Whereas with session tickets, client maintains the session tickets. I am getting confused on the session caching concept. Could someone please clarify. Also, for TLS 1.3, should the server caching be enabled for session resumption ? Thanks BR, Neetish On Sat, Jun 10, 2017 at 7:09 AM, Salz, Rich <rs...@akamai.com> wrote: > > It is quite likely that your version of wireshark does not know how to > properly decode the TLS 1.3 ServerHello. > > Please see https://www.ietf.org/mail-archive/web/tls/current/ > msg22333.html for information about downloading an early release of > wireshark. >
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
