Re: NSS: Unable to verify close_notify in client code?

On Tuesday, 19 December 2017 20:44:33 CET Martin Thomson wrote: > See SSL_AlertReceivedCallback(). though do note that TCP does not reliably deliver data after one side has closed connection and behaviour of different implementations varies widely (both on TCP and TLS level):

Re: NSS: Unable to verify close_notify in client code?

See SSL_AlertReceivedCallback(). On 20 Dec. 2017 6:22 am, "Johann 'Myrkraverk' Oskarsson" wrote: > Hi, > > Is it really impossible to verify if the server sent close_notify in a > normal NSS client application? > > In both cases, PR_Read() returns zero with no error

NSS: Unable to verify close_notify in client code?

Hi, Is it really impossible to verify if the server sent close_notify in a normal NSS client application? In both cases, PR_Read() returns zero with no error messages or status difference of any kind. I have tentatively verified that ssl3_HandleAlert() is called with AlertDescription zero ==