These are chat archives for IndySockets/Indy

30th
Mar 2017
Justin
@klsyzzz
Mar 30 2017 00:35
@rlebeau Thank you very much
also can you tell me what's the difference between openssl-1.0.2k-i386-win32 and openssl-1.0.2j-i386-win32 ? they all listed in the server, are they just different build built on different time?
Kudzu
@czhower
Mar 30 2017 00:37
they are based on the openssl releases, so check their release notes.
Justin
@klsyzzz
Mar 30 2017 00:37
oh. didn't know that
does that means I need to update openssl as well ?
I didn't recall I installed openssl, just using Indy lib from Delphi install
Remy Lebeau
@rlebeau
Mar 30 2017 00:40
@klsyzzz openssl-1.0.2k-i386-win32 = OpenSSL 1.0.2k for Windows 32bit, openssl-1.0.2j-i386-win32 = OpenSSL 1.0.2j for Windows 32bit, openssl-1.0.2k-x64_86-win64 = OpenSSL 1.0.2k for Windows 64bit. They are just different builds of different releases of OpenSSL
Justin
@klsyzzz
Mar 30 2017 00:41
how do I find out which openssl on my pc, the Indy package come with Delphi 10.2 berlin install
Remy Lebeau
@rlebeau
Mar 30 2017 00:42
OpenSSL is a standalone library. There can be multiple versions installed on a PC. Look at the DLL's version info properties in Windows Explorer. In your code, you can find out which version of OpenSSL is being used by your app by calling Indy's OpenSSLVersion() wrapper function in the IdSSLOpenSSL unit.
Justin
@klsyzzz
Mar 30 2017 00:49
i see, thank you very much
sorry one more question, do we need to include OpenSSL dlls for deployment to client's pc which runs our delphi application?
as we don't need to deploy any Indy lib to client PC
Remy Lebeau
@rlebeau
Mar 30 2017 01:00
@klsyzzz OpenSSL is a separate library, so yes, you need to deploy it (or, if encryption export laws get in your way, have the user download it from OpenSSL's website), unless it is already installed on the PC (if so, you can use Indy's IdOpenSSLSetLibPath() function to point to it), or if you are compiling for iOS devices (Indy compiles OpenSSL statically on that platform). Indy itself is compiled directly into your app (unless you enable runtime packages, in which case you would then have to deploy those)
Justin
@klsyzzz
Mar 30 2017 01:12
thank you very much Remy
mezen
@mezen
Mar 30 2017 06:52

But pls consider https://www.openssl.org/source/license.html, for example

    1. Redistributions in binary form must reproduce the above copyright
  • notice, this list of conditions and the following disclaimer in
  • the documentation and/or other materials provided with the
  • distribution.

    1. Redistributions of any form whatsoever must retain the following
  • acknowledgment:
  • "This product includes software developed by the OpenSSL Project
  • for use in the OpenSSL Toolkit (http://www.openssl.org/)"

    1. All advertising materials mentioning features or use of this software
  • must display the following acknowledgement:
  • "This product includes cryptographic software written by
  • Eric Young (eay@cryptsoft.com)"
  • The word 'cryptographic' can be left out if the rouines from the library
  • being used are not cryptographic related :-).
Hmpf, gitter broken my format :-\
Remy Lebeau
@rlebeau
Mar 30 2017 17:48
looks fine to me
Justin
@klsyzzz
Mar 30 2017 21:53
@mezen thank you, will add that to consideration.
Justin
@klsyzzz
Mar 30 2017 22:15
so if we planning to distribute the dlls, we just distribute the openssl license.txt to the same folder on client side, is it enough?