I am seeing that during the imap account setup testing performed by the software that in 10.3.3.3057 it is able to make a SSL connection to the server and the server is reporting:
SSL negotiation successful (TLS 1.0, 1024 bit key exchange, 256 bit encryption)
The two sides have agreed on the connection characteristics.
The phone prompts to accept an untrusted self signed cert. Which it is told to accept by me.
But then the phone drops the socket and reports back on the screen that it could not verify the connection.
The same account/setup on a different Classic running 10.3.2.2639 works fine and has been fine for quite some time.
The same account on the newer OS only works if SSL is disabled. If StartTLS is used, it gets as far as prompting for cert acceptance at the beginning of the StartTLS sequence, then drops again.
This has been tried with SSL levels set at compatible and low.
The one thing that I have forgotten from months ago is whether I needed to import the cert.
But it seems that if it fails even at SSL=low that the newer version of the OS will not downshift successfully to accomodate that setting.
TLS 1.2 is all well and fine, but there are systems that can do no higher than TLS 1.0. The particular server uses RC4 AES256.
Does anyone know of a workaround, or a particular TLS 1.0 cipher suite that passes muster on this version?
If not, I hope the post is at least informative.
SSL negotiation successful (TLS 1.0, 1024 bit key exchange, 256 bit encryption)
The two sides have agreed on the connection characteristics.
The phone prompts to accept an untrusted self signed cert. Which it is told to accept by me.
But then the phone drops the socket and reports back on the screen that it could not verify the connection.
The same account/setup on a different Classic running 10.3.2.2639 works fine and has been fine for quite some time.
The same account on the newer OS only works if SSL is disabled. If StartTLS is used, it gets as far as prompting for cert acceptance at the beginning of the StartTLS sequence, then drops again.
This has been tried with SSL levels set at compatible and low.
The one thing that I have forgotten from months ago is whether I needed to import the cert.
But it seems that if it fails even at SSL=low that the newer version of the OS will not downshift successfully to accomodate that setting.
TLS 1.2 is all well and fine, but there are systems that can do no higher than TLS 1.0. The particular server uses RC4 AES256.
Does anyone know of a workaround, or a particular TLS 1.0 cipher suite that passes muster on this version?
If not, I hope the post is at least informative.