[gnutls-devel] GnuTLS | TLS1.3 new session ticket GNUTLS_E_PUSH_ERROR (#1444)

[Read-only notification of GnuTLS library development activities]

Neelabh Mam commented:


I re-checked the logs of fz client against FZ server (both using gnutls) and realized that even fz client is getting these -53 errors (infact much more quickly than my libssl client). It's just that FZ maintains state and immediately initiates a reconnect and then proceeds with the listing from the remote folder where it errored out the last time.. So, at this point this does not look like an issue specific to my libssl client's handling of new session tickets. I took a process explorer trace of nw operations. This gives you a callstack of the server initiated disconnect. But unfortunately without the public symbols it doesn't highlight the correct situation. Short of me building a debug fz server, how best could we diagnose the problem ? This looks like something in the server tls layer is maxing out.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1444#note_1224969215
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20230102/a6dc2471/attachment.html>