Nice solution, despite I think we will get troubles with our internal test regarding the FIPS versions of OpenSSL when we adjust the build process.

I would suggest you open a ticket at the RT of the OpenSSL team for a feature request about. I will of course support this approach!

Regarding C++ Builder I am still looking forward for David Dean’s tests: http://blogs.embarcadero.com/ddean/2009/11/11/34858

He says he has this on his list.

Cheers,
Arvid

Yes, I checked using Dependency Walker.
Here’s what I did using Microsoft Visual C++ 2008 SP1:

1. perl Configure VC-WIN32 –prefix=c:/temp
2. notepad.exe ms\ntdll.mak // replace “/MD” with “/MT”
3. ms\do_masm
4. nmake -f ms\ntdll.mak
5. nmake -f ms\ntdll.mak test
6. editbin.exe /rebase:base=0×11000000 libeay32.dll
7. editbin.exe /rebase:base=0×12000000 ssleay32.dll

IMHO, building with Embarcadero C++ 2010 and being able to static link into a Delphi or Embarcadero C++ EXE would be super. I hate using DLLs for crypto since calls are so easy to intercept (no programming skills needed.)

yes the lack of C++ Builder support is one of the reasons to use gcc. The DLLs you created are usable with any newer Indy version too, there are no more adjustments needed. We are “just” publishing them in order to provide something like an out-of-the-box experience when using Indy and SSL/TLS (without the need for MS VC Runtime DLLs as you already mentioned and most precompiled OpenSSL libraries available need).

The drawback of using gcc is a slightly larger size of the resulting files.

One thing regarding your experience: Are you sure there are no dependencies? I mean did you check it with Dependency Walker or something like that? If so, I will need to check that again, regarding Win32 we might move to that build environment after doing some tests.

Cheers,
Arvid

My findings were surprising.

I was unable to build OpenSSL 0.98m using Embarcadero C++ 2010.

I tried building OpenSSL 0.98m with Microsoft Visual C++ 2008 using the instructions in INSTALL.W32. But the default settings require deploying MSVC runtime DLL.

I changed “/MD” to “/MT” in ms/ntdll.mak and resulting DLL’s don’t require any more runtime DLL’s than MinGW.

No MSVC++ runtime DLL’s needed and OpenSSL binaries are smaller compared to ones compiled by MinGW! If I had time, I’d do benchmarks.

So far, it is working great with Delphi 2010 apps using Synapse. I haven’t done multithreaded stress tests, yet.

Embarcadero needs to work with the OpenSSL team, because Borland C++ 5.0 is the latest version mentioned by OpenSSL. That is embarrassing as not being able to compile.

thank you for your comment. I will have a look at it as soon as I have some spare time.

Regards,
Arvid

You’re welcome, thank you for your feedback! I just uploaded the updated libraries to the Fulgan Mirror, and I am going to blog about it right now!

Cheers,
Arvid

I’m wondering if you’ll be providing 0.98m soon.

Thanks!

Hi Carey,

sorry for the late reply, I am getting a bit busy at the end of each year

I need to check back to see if generating the certificates is possible using Indy. Externally you would use the OpenSSL executables (we are not shipping them). You could find them here: http://www.slproweb.com/products/Win32OpenSSL.html

A good explanation of using OpenSSL to build certificates can be found here: http://www.madboa.com/geek/openssl/#cert-self

One thing to mention is that those self-signed certificates should solely be used for testing purposes. Typically you would buy SSL certificates i.e. from your web hoster.

Cheers and Merry Christmas,

Arvid

Thank you very much for the feedback and pointing towards a solution!

Cheers,
Arvid