eSeGeCe
software
Hi! Im a bit confused about status of this Indy progect https://github.com/IndySockets/Indy
In the patchnotes for sgcWebSockets there is written about OpenSSL 1.* but I didnt find about 3.*
What is the proper way to use newest OpenSSL libraries?
In the patchnotes for sgcWebSockets there is written about OpenSSL 1.* but I didnt find about 3.*
What is the proper way to use newest OpenSSL libraries?
Hello,
You can check the demo in the folder "Demos\01.WebSocket_Quick_Start\01.Server_and_Client_Chat" which shows a server and client components which can connect any of the openssl libraries: openSSL 1.0.2, 1.1.1 and 3.0.0
You only must select the openssl apiversion before start the server/client.
More info:
https://www.esegece.com/help/sgcWebSockets/#t=QuickStart%2FOpenSSL.htm
Kind Regards,
Sergio
You can check the demo in the folder "Demos\01.WebSocket_Quick_Start\01.Server_and_Client_Chat" which shows a server and client components which can connect any of the openssl libraries: openSSL 1.0.2, 1.1.1 and 3.0.0
You only must select the openssl apiversion before start the server/client.
More info:
https://www.esegece.com/help/sgcWebSockets/#t=QuickStart%2FOpenSSL.htm
Kind Regards,
Sergio
Sergio thanks for your answer! Indeed I found it in the sgcWebSockets but now I have another more general question, how do I switch to an Indy version from the project https://github.com/IndySockets/Indy to be able to use OpenSSL 3.* everywhere in my project, not only in sgcWebSockets ?
Hello,
The standard indy version doesn't currently support openssl 3, although there is an effort for provide support to it.
You can download the sgcIndy version which supports openssl 1.1.1 and 3.0.0
https://www.esegece.com/products/sgcindy
Kind Regards,
Sergio
The standard indy version doesn't currently support openssl 3, although there is an effort for provide support to it.
You can download the sgcIndy version which supports openssl 1.1.1 and 3.0.0
https://www.esegece.com/products/sgcindy
Kind Regards,
Sergio
- Page :
- 1
There are no replies made for this post yet.