Results 13 comments of tangowhisky

> I'm creating my server with the following options: > > ``` > LIOHandleSSL.SSLOptions.SSLVersions := [sslvTLSv1, sslvTLSv1_1, sslvTLSv1_2]; > LIOHandleSSL.SSLOptions.Method := sslvTLSv1_2; > LIOHandleSSL.SSLOptions.Mode := sslmServer; > ``` > >...

> In the README.OpenSSL.txt I have noted a typo when I said that "SSLOptions.Mode" is ignored. I meant "SLLOptions.Method" is ignored. "SSLOptions.Versions" is now the only means of control over...

> Thanks for the change @MWASoftware and the work you're putting into this! I will take a look at the changes later on. > > > Loading the legacy OpenSSL...

> @MWASoftware (and anyone else who is interested in contributing to this effort) - there is a new joint initiative with Embarcadero and some other 3rd party devs to get...

I noticed the problem with IdAuthenticationNTLM when I was preparing my proposed update (https://github.com/MWASoftware/Indy.proposedUpdate). To solve these dependency issues, I would propose: 1. Moving IdSSL into the "core" package 2....

> > ``` > > 1. Moving IdSSL into the "core" package > > ``` > > Why? Nothing in the Core package uses SSL/TLS, encryption, or hashing APIs. All...

I have brought the Indy-10.7 branch in my repo up-to-date and tested. Note: I found an error in the merge changes from your upstream repo - a missing parameter in...

![lazoptions.png](https://github.com/user-attachments/assets/821964ae-8bc7-40fc-a9a7-398cd0f9a456) Just add -Ur to the indylaz package options (see image above). The unit references for Indy are almost circular and this options seems necessary to avoid compiler issues

On my system, the XML looks like: ```xml ``` but the actual value can include other settings, such as defining a DEBUG symbol. The problem seems to be a bug/feature...

> Your ProposedUpdate fork includes OpenSSL work, but OpenSSL has already been split out of the main Indy library for 10.7 in favor of the new IndyTLSOpenSSL package, so you...