Jason Wharton

On 8/2/2021 at 11:25 AM, Remy Lebeau said:

Then you should be fine using the latest Indy with OpenSSL 1.0.2, as it supports TLS 1.2

Yes, correct.  I was mistaken.

I finally discovered that my path to the Open SSL binaries was not configured correctly and so Indy was resorting to TLS 1.0.

On 7/27/2021 at 1:50 AM, Angus Robertson said:

Flagged by whom?  TLS 1.2 is perfectly good provided you disable a lot of weak ciphers and hashes. 

 

Most IIS sites are still only TLS 1.2, Microsoft does not support TLS 1.3 until Windows Server 2022. 

 

Angus

 

Sorry, I mistyped.  I need to get to TLS 1.2.

On 6/4/2020 at 9:15 PM, Remy Lebeau said:

Still a work in progress.  Mezen's pull request for a new SSLIOHandler for OpenSSL 1.1.x is still pending review, I just have not had time lately to review it yet, but you can download and try it for yourself.

 

How can I help?  I need to get higher than TLS 1.2.  My websites are being flagged as having too weak of encryption.

6 hours ago, y2nd66 said:

Yesterday, I wrote an email trying to contact you to "support at ibobjects dot com", with the detail of the modification and asked the same, if was valid or not.

Thanks.

Unfortunately I didn't receive it.  Please try sending it directly to jason at jwharton dot com.

On 12/22/2020 at 7:20 AM, y2nd66 said:

More or less, I had to modify the source code of IB_Components.pas

 

I have to test if the change is effective for my entire environment, I still need more time to know.

I am the author of IB Objects and would be interested to have a look at the changes you made to IB Objects source.  I will be able to tell you if what you have done is a good idea or not.

Thanks,

Jason Wharton