Hello,
updated OpenSSL Versions available in the flavor of your choice 
As of today you can download precompiled versions of the newest OpenSSL libaries from our official Indy Mirror (The Fulgan Mirror).
As the OpenSSL team has published an update for the old 0.9.8 branch, we supply them too:
Direct Links:
http://indy.fulgan.com/SSL/openssl-0.9.8o-i386-win32.zip
http://indy.fulgan.com/SSL/openssl-1.0.0a-i386-win32.zip
As always: You’ll find a ReadMe, License Information and File Hashes inside the zip archive. This version is including important bug and security fixes, using it is strongly recommended.
Note: This version needs the very latest Indy SVN (Revision #4168 and newer). This is due to changes in OpenSSL (i.e. removing deprecated MD2 by default).
As before the libraries have no noteworthy dependencies except for the Win64 versions which require the VC++ 2008 runtime libraries.
Cheers,
Arvid
Arvid Delphi, Indy Delphi, Indy, OpenSSL, Security, Update
Hi,
beside my post about OpenSSL updates, there has been no or little time to update this blog in the past month. There are some interesting OpenSource projects I had been involved.
Regarding my voluntary work with the Indy Project I am glad to announce that I was invited to join the Indy Mercury Team: Since Nov 2009 I am now part of Indy’s so called steering committee too (next to the Core Team where the development takes place).
In Addition my company became a Intel Software Partner and an Embarcadero Technology Partner.
Last but not least I had been working on other OpenSource projects too:
Now, in the next weeks I am going to blog especially about:
- Some backports of UI behaviour for older Delphi Versions (like native Cursors and Hints/Tooltips)
- Some tricky bugs I chased in Indy (topics will cover Winsock EADDRINUSE, IPv6 and Nagle)
- A patch I committed for dxgettext: changing embedded translations behaviour from absolute file offsets to relative positions which allows using i.e. EXE compressors like UPX while still being able to attach embedded translations
- A fork of David Polberger’s (and JEDI’s) JvLinkLabel I am currently creating
- Probably the upcoming Delphi Tage 2010 in Berlin, Germany (national Delphi Days)
So stay tuned, more to come!
Cheers,
Arvid
Edited 04/24/2010 (Typos)
Arvid Delphi, Indy Delphi, Indy, News, Project
Hello,
after one year of beta testing, the OpenSSL team published the final 1.0 version yesterday. As of today you can download a precompiled version of the OpenSSL libaries from our official Indy Mirror (The Fulgan Mirror).
Direct Link: openssl-1.0.0-i386-win32.zip
As always: You’ll find a ReadMe, License Information and File Hashes inside the zip archive. This version is including important bug and security fixes, using it is strongly recommended.
Note: This version needs the very latest Indy SVN (Revision #4168 and newer). This is due to changes in OpenSSL (i.e. removing deprecated MD2 by default).
I would like to thank my previous readers, especially Salvor for pointing out a different way in building the libraries without the need for the MS VC++ Runtime DLLs while being able to use the latest VC++ compilers.
This release is built using MS VC++ 2008 and the Network Wide Assembler (NASM) instead of Mingw/gcc which allows us to create smaller DLLs and faster code now (sadly the VC++ 2010 build chain is still broken for OpenSSL 1.0).
Regards,
Arvid
Arvid Delphi, Indy Delphi, Indy, OpenSSL, Security, Update
Hi,
I just prepared and published an updated precompiled version of the OpenSSL libraries. As always they are available on the official Indy Mirror, the Fulgan Mirror.
Direct Link: openssl-0.9.8m-i386-win32.zip
You’ll find a ReadMe, License Information and File Hashes inside the zip archive. This version is including important bug and security fixes, using it is strongly recommended.
Regards,
Arvid
Arvid Delphi, Indy Delphi, Fix, Indy, OpenSSL, Security, Update
Hi,
I recently had a talk with JP Mugaas about whether we should include FIPS support of OpenSSL in Indy and to what extend this will be useful for our users (especially those in the United States).
We agreed that many users would benefit from the possibility to write FIPS compliant applications. However as you know providing support for it can only be part of your certification process. On the other hand: Even if you or your company don’t decide to get a certification on your own it would be still an advantage to be able to write at least FIPS compliant applications.
What do you think about? Would that be of interest to you?
Feel free to add your comments about. Currently we are only planning…
Regards,
Arvid
Arvid Delphi, Indy
