-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS 1.3 #11
Comments
TLS 1.3 is available in PR IndySockets/Indy#299, which has not been merged yet. But you can use its code in your project. |
hello - any plans to add TLS 1.3 support? some SMTP providers are only accepting 1.3 which is becoming problematic to me. |
What I stated in my previous comment still stands. The PR is not finalized, but you are welcome to use it in your projects. |
As far as I understand it, the PR IndySockets/Indy#299 is dead and will not be updated by the author. However he stated plans to jump to OpenSSL 3.x instead (and therefore skipping OpenSSL 1.1.x, but incorporating backwards compatibility). |
PR IndySockets/Indy#299 haven’t been merged in more than 3 years, so this definitely this can been seen as “Abandoned” (Hope not), but I’m not optimistic if this will happen on near future.
Delphi 12 was released today, and still don’t have OpenSSL 3.x
Regards
MH
De: baka0815 ***@***.***>
Responder a: IndySockets/Indy ***@***.***>
Fecha: miércoles, 8 de noviembre de 2023, 7:59
Para: IndySockets/Indy ***@***.***>
CC: Mauricio Herrera ***@***.***>, Author ***@***.***>
Asunto: Re: [IndySockets/Indy] TLS 1.3 (Issue IndySockets/IndyTLS-OpenSSL#11)
As far as I understand it, the PR IndySockets/Indy#299 is dead and will not be updated by the author. However he stated plans to jump to OpenSSL 3.x instead (and therefore skipping OpenSSL 1.1.x, but incorporating backwards compatibility).
But I can't find any reference to code supporting OpenSSL 3.x, but maybe my search-fu is lacking.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
FYI, a new GitHub repo has now been created to separate the OpenSSL logic, most likely into a new package, so it can be updated independently of the main Indy library. |
Many services are now accepting only TLS 1.3, and Indy only have 1.2.
I have a webservice running on Linux, and my provider is asking to switch to TLS 1.3, so when can we have it enabled?
Thanks
The text was updated successfully, but these errors were encountered: