Can I just double check that you are certain the Alert Level and Description bytes (1 byte each) are encrypted and so cannot be read in a Wireshark trace? This makes debugging very difficult if all you have to go on is a line trace?
Dave Thompson-5 wrote: > >> From: owner-openssl-us...@openssl.org On Behalf Of Mr.Rout >> Sent: Sunday, 18 March, 2012 03:55 > >> We have fixed the Segment lost issue which was causing Packet >> drop. But we >> are still seeing the "Encryption Alert" again. I am attaching one more >> packet capture which has all the information. >> > You are seeing "Encrypted Alert", not "Encryption Alert". > >> Due to my limited knowledge i request would you please >> explain me the exact >> reason for this Error message. >> > The alert is encrypted, which prevents us from knowing for sure > which alert it is. But the only alert that usually follows > application data in this way is alert #0 Close, which is > quite normal and not an error as far as SSL/TLS is concerned. > > It may be an error at the application level if the application > (endpoint) shouldn't have closed this connection at this time. > If so you need application level information to debug this. > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > > -- View this message in context: http://old.nabble.com/Difference-b-w-TLS--Connection-and-TLS-Session-tp32780649p34063664.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
