Tobias Rapp wrote:
> Arno Garrels wrote:
>> The DLL names are globally writable typed constants, set their values
>> before the OpenSSL libraries are loaded.
>
> Is there any advantage to use writable typed constants like
>
> const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
>
> instead of
>
>
Arno Garrels wrote:
> The DLL names are globally writable typed constants, set their values
> before the OpenSSL libraries are loaded.
Is there any advantage to use writable typed constants like
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
instead of
var GSSLEAY_DLL_Name : String = 'SS
> I prefer this anyway since the load errors don't raise somewhere
> but where I can handle them easily:
I also log the SSL version and directory at the point, since multiple SSL
DLLs may be available on the PC and like to know the expected versions
are being used:
MySslContext.InitContext;
Zvone wrote:
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
>
>> This is not required since writable typed constants is enabled.
>
> That's all fine but I don't see it published as property anywhere. How
> do I modify its value during runtime to set full path for SSLEAY32.DLL
> and LIBEA
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
This is not required since writable typed constants is enabled.
That's all fine but I don't see it published as property anywhere. How
do I modify its value during runtime to set full path for SSLEAY32.DLL
and LIBEAY32.DLL?
So simple: Just
>>> const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
> This is not required since writable typed constants is enabled.
That's all fine but I don't see it published as property anywhere. How
do I modify its value during runtime to set full path for SSLEAY32.DLL
and LIBEAY32.DLL?
--
To unsubscrib
Francois PIETTE wrote:
>> const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
>
> I think the solution is much simpler than what you think: Change
> "const" by "var" so that the DLL name is provided thru a global
This is not required since writable typed constants is enabled.
--
Arno Garrels
--
e author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
- Original Message -
From: "Zvone"
To: "ICS support mailing"
Sent: Saturday, September 04, 2010 3:44 PM
Subject: Re: [twsocket] New
Forget about my remark about "\" or "/". The DllPath could be used as
is just DllPath + LibraryName. This avoids the need to process
needlessly slashes or backslashes. If this is used I would suggest a
bold remark in the docs on Wiki to encourage use of this property if
this is to be used.
Anyway,
Well, like I wrote, it effects all programs that use ICS. And it is a
bit harder to find a solution that fits all in this case due to nature
of the problem.
This is how ICS loads for example SSLLEAY32.DLL:
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
...
GSSLEAY_DLL_Handle := LoadLibrary(PC
I think here is what we should do:
- the OpsnSSL DLLs must be loaded only from process folder of the
ICS-based-our-code-exe
- before loading the DLLs, we must check for their presence in RAM and fire
an exception in that case.
Regards,
SZ
On Sat, Sep 4, 2010 at 10:29 AM, Francois PIETTE
wrote:
Maybe you could carefully read those documentation and review ICS code to
see if it needs some improvement. If improvment is needed, then propose some
changes. Don't forget the gold rule: change in ICS must not break any
existing code.
--
francois.pie...@overbyte.be
The author of the freeware
12 matches
Mail list logo
