This content has been marked as final. Show 6 replies
Every SSLException except SSLPeerUnverifiedException, every IOException, and every SocketException except SocketTimeoutException is fatal when arising from socket I/O.
What is your actual problem?
According to the RFC for SSL there can be two levels of alerts ie Warning and Fatal. I just need to find out whether the alert thrown by the library is of Warning level or Fatal error.
What part of 'all SSLExceptions are fatal' didn't you understand?
The fact that some SSL alerts are just warnings has no bearing on this, unless you have some counter-evidence that shows that warning alerts throw SSLExceptions too. Do you? The only two alerts I can find that can be warnings are 'close_notify', which is manifested as read() returning -1, not as an exception, and 'no_renegotiation', which as a quick search of this forum will show you is definitely treated as fatal by JSSE, as it is permitted to do by the RFC, and causes an SSLException.
NB cross posted.
no_renegotiation is to be treated as WARNING as I am using TLS 1.0 and RFC 2246 specifies that it should always be treated as Warning and not fatal.
Edited by: 980263 on Jan 7, 2013 4:10 AM
I do not wish to discuss this in two places at once.
Edited by: EJP on 7/01/2013 23:23
+... thread locked. Stay with your original post at the other web site.+