 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Dan Guest
|
Posted: Thu Aug 17, 2006 10:01 pm Post subject: Specifying the directory of the Indy Open SSL dll's |
|
|
Hi all,
I am want to use TLS with SMTP client. I set the
idSMPT1.IOHandler:=IdSSLIOHandlerSocketOpenSSL1;
idSMTP1.UseTLS:=utUseExplicitTLS;
and put the Indy Open SSL libraries ( libeay32.dll and ssleay32.dll from
http://www.intelicom.si/www.nsf/docs/6GERPJGIBC?opendocument&cat=9&doc=6GERPJGIBC&lang=en )
in the same directory as my application. It works. My question is, is
there any way tospecify what directory to look in for the dll's ? is that
what TIdSSLIOHandlerSocketOpenSSL.SSLOptions.VerifyDirs is for? I'd like to
be able to specify, b/c whatt if I want to use openSSL for other things in
the application? I'd like to use the newer dll's. |
|
| Back to top |
|
 |
Remy Lebeau (TeamB) Guest
|
Posted: Thu Aug 17, 2006 10:28 pm Post subject: Re: Specifying the directory of the Indy Open SSL dll's |
|
|
"Dan" <onsite (AT) hpassist (DOT) com> wrote in message
news:44e4a0df (AT) newsgroups (DOT) borland.com...
| Quote: | is there any way tospecify what directory to look in for the dll's ?
|
No. Indy does not specify any folder name when loading the DLLs, so they
must exist in the OS's search path. Refer to the documentation for the
Win32 API LoadLibrary() function for a list of rules that the OS follows
when looking for DLLs with no folder names specified.
| Quote: | is that what TIdSSLIOHandlerSocketOpenSSL.SSLOptions.VerifyDirs is for?
|
No.
| Quote: | I'd like to be able to specify
|
You cannot, unless you alter Indy's source code to pass your own folder
names, and then recompile Indy.
| Quote: | b/c whatt if I want to use openSSL for other things in the application?
I'd like to use the newer dll's.
|
You must upgrade to the latest Indy 10 snapshot in order to use newer DLLs.
The DLLs you are using right now are 4 years old, and are not official DLLs
from http://www.openssl.org anyway. Until recently, Indy had had to always
use custom-built DLLs because it could not use the official DLLs. So
updates were released whenever someone could get around to re-building the
custom DLLs with the latest OpenSSL version at the time. So Indy was
usually far behind in OpenSSL updates/fixes. Recently, Indy 10 was updated
to fully support the official DLLs. The custom DLLs are no longer used at
all. This way, people can stay up-to-date with the official DLLs whenever
new versions are released on http://www.openssl.org.
Gambit |
|
| Back to top |
|
 |
Dan Guest
|
Posted: Fri Aug 18, 2006 2:23 am Post subject: Re: Specifying the directory of the Indy Open SSL dll's |
|
|
Thanks for the information. That will work. I thought I had the latest
Indy version (10.0.52) -I will try to figure out how to get the beta
version.
"Remy Lebeau (TeamB)" <no.spam (AT) no (DOT) spam.com> wrote in message
news:44e4a772$1 (AT) newsgroups (DOT) borland.com...
| Quote: |
"Dan" <onsite (AT) hpassist (DOT) com> wrote in message
news:44e4a0df (AT) newsgroups (DOT) borland.com...
is there any way tospecify what directory to look in for the dll's ?
No. Indy does not specify any folder name when loading the DLLs, so they
must exist in the OS's search path. Refer to the documentation for the
Win32 API LoadLibrary() function for a list of rules that the OS follows
when looking for DLLs with no folder names specified.
is that what TIdSSLIOHandlerSocketOpenSSL.SSLOptions.VerifyDirs is for?
No.
I'd like to be able to specify
You cannot, unless you alter Indy's source code to pass your own folder
names, and then recompile Indy.
b/c whatt if I want to use openSSL for other things in the application?
I'd like to use the newer dll's.
You must upgrade to the latest Indy 10 snapshot in order to use newer
DLLs.
The DLLs you are using right now are 4 years old, and are not official
DLLs
from http://www.openssl.org anyway. Until recently, Indy had had to
always
use custom-built DLLs because it could not use the official DLLs. So
updates were released whenever someone could get around to re-building the
custom DLLs with the latest OpenSSL version at the time. So Indy was
usually far behind in OpenSSL updates/fixes. Recently, Indy 10 was
updated
to fully support the official DLLs. The custom DLLs are no longer used at
all. This way, people can stay up-to-date with the official DLLs whenever
new versions are released on http://www.openssl.org.
Gambit
|
|
|
| Back to top |
|
 |
Dan Guest
|
Posted: Fri Aug 18, 2006 6:27 pm Post subject: The link to get the development snapshot |
|
|
Here's the link to get the Development snapshot for Indy 10, to save anyone
in the same boat some time:
http://www.indyproject.org/Sockets/Docs/Indy10Install.en.aspx
"Dan" <onsite (AT) hpassist (DOT) com> wrote in message
news:44e4de50$1 (AT) newsgroups (DOT) borland.com...
| Quote: | Thanks for the information. That will work. I thought I had the latest
Indy version (10.0.52) -I will try to figure out how to get the beta
version.
"Remy Lebeau (TeamB)" <no.spam (AT) no (DOT) spam.com> wrote in message
news:44e4a772$1 (AT) newsgroups (DOT) borland.com...
"Dan" <onsite (AT) hpassist (DOT) com> wrote in message
news:44e4a0df (AT) newsgroups (DOT) borland.com...
is there any way tospecify what directory to look in for the dll's ?
No. Indy does not specify any folder name when loading the DLLs, so they
must exist in the OS's search path. Refer to the documentation for the
Win32 API LoadLibrary() function for a list of rules that the OS follows
when looking for DLLs with no folder names specified.
is that what TIdSSLIOHandlerSocketOpenSSL.SSLOptions.VerifyDirs is for?
No.
I'd like to be able to specify
You cannot, unless you alter Indy's source code to pass your own folder
names, and then recompile Indy.
b/c whatt if I want to use openSSL for other things in the application?
I'd like to use the newer dll's.
You must upgrade to the latest Indy 10 snapshot in order to use newer
DLLs.
The DLLs you are using right now are 4 years old, and are not official
DLLs
from http://www.openssl.org anyway. Until recently, Indy had had to
always
use custom-built DLLs because it could not use the official DLLs. So
updates were released whenever someone could get around to re-building
the
custom DLLs with the latest OpenSSL version at the time. So Indy was
usually far behind in OpenSSL updates/fixes. Recently, Indy 10 was
updated
to fully support the official DLLs. The custom DLLs are no longer used
at
all. This way, people can stay up-to-date with the official DLLs
whenever
new versions are released on http://www.openssl.org.
Gambit
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|