Quick Update: 2014.04.11

Updated openssl-1.0.1e windows binary to openssl-1.0.1g. Extract it on the c: drive and you should be able to use it.
Extract all the 32 bit openssl binaries into the C drive and rename the folder to c:\openssl

Quick Update: 2014.04.10

I will update the following windows binary versions of openssl tomorrow night 9:00EST. At the moment, the 0.9.8 versions of openssl are safe. Avoid using the 1.0.x versions for now. ~Aschenbach

QUICK Update: 2014.04.07 READ THIS

OPENSSL BUG

Quick Update: 2013.05.07

This 64-bit version of openssl 0.9.8y will work.

If you are missing a random *.dll file after running either the openssl 64 or the 32 bit package. There is a microsoft c++ redistributable package you may need to install first. If the 32-bit version of openssl doesn't work for you then try installing the 32-bit VS C++ 2008 redistributable package to see if this will solve it for you. The 64 bit VS C++ 2010 redistributable version is for the 64 bit openssl pacakge. All else fails, install both versions of C++ 2008 and 2010 redistributable packages before downloading our compiled version of openssl.
32 bit Package
64 bit Package

~aschenbach

Quick Update: 2013.05.02

With much joy and happiness, We are pleased to announce we have finally found time to compile the latest openssl package for win32.
Same format, place the 7-zip package under "c:\" and enjoy :)
To test the latest binary openssl 7zip package, unzip it with 7zip then place the openssl folder at "c:", then open up a DOS prompt then finally run the following command:
"\openssl\bin\openssl.exe speed"
If you do see a test running with lots of numbers displaying on your DOS screen, this means you are GOLDEN!
we are in the process of entertaining the idea of compiling a 64-bit version of openssl in the near future.
~aschenbach

Quick Update: 2012.05.24

Everything in these three binary packages will work. Please extract the 7-zip file under "c:\"

We will compile each packages from now on to have the prefix point to --prefix=C:\openssl during configuration. We have tested the latest on two seperate windows machines and it works on both.

We would not rule out the idea of compiling your own unique version of openssl with a installation location for a small fee or donation, if this situation presents itself.

Installation: using 7zip to extract the compressed file to "c:\", then edit your autoexec.bat or somekind of batch script to point to c:\openssl\bin to gain ubiquitous access.

~aschenbach

Quick Update: 2012.04.07

We have uploaded two 7zip binary packages of openssl version 0.9.8u and 1.0.0h along with its sha1sum on the download location. We will build the installer version at a later date.

We've noticed on this compilation, the size on each of the 7z binary packages is smaller compared to our previous binary releases. We did do something different on this compilation. There are two additional dll files which associated in the bin directory. This could be the reason why these two packages are smaller in size compared to previous release. Don't be alarm that its a little different. ~aschenbach

We would like to contribute some of our computing resources to create win32 openssl binary for the masses. We plan to keep up with the latest stable release of openssl and make it widely available on various windows platform.

The following are sha1 sum of the 7zip package for two openssl win32 binary packages. The packages are compiled with 32 bit MS-visual studio 2008 version, currently We do not own a copy of 64 bit windows with a 64 bit MS-VS 2008 compiler.

We found that there is a minor issue with using openssl on windows. In order to use openssl on windows {XP,Vista,Windows 7}, one must extract this 7z package to your local "C:" drive then rename the folder name to "openssl". We've also noticed that on the older versions of openssl, a file called "openssl.cnf" must be place under "c:\openssl\ssl". This file is place at the proper location in version 1.0.0f. Installable and non-installable packages are available below.

If you need ubiquitous access on windows, you could edit the autoexec.bat file on windows XP and have the PATH global variable be set to PATH=%PATH%;c:\openssl\bin sadly, windows 7 and vista won't allow any user to edit their global autoexec.bat file without having administrator rights. In order to bypass this problem, We created a runme.bat file under our windows user directory c:\users\aschenbach\runme.bat and had this environment variable be set in this file. We then ran this file each time when We opened up a DOS or powershell prompt, so one could have ubiquitous access with openssl.

Download

Description Download Size Last change Sha1
 
• Win64 Binary 7z package, openssl v0.9.8y Package  874859  10 Feb 2013  da1da3a956c7bcf15d48b4ecc7ef914a8798c7d7
 
• Win32 Binary 7z package, openssl v1.0.1g Package  991477  10 April 2014  aaf350a654356b30c89f338992e75814951bf7a6
• Win32 Binary 7z package, openssl v1.0.0k Package  934751  10 Feb 2013  1fede9c8bdd657b0d51aff77e28fef4505796293
• Win32 Binary 7z package, openssl v0.9.8y Package  794359  10 Feb 2013  5fd3fab2cb85e524bcfc02edf108152845630ac3
 

If you wish to send mail to me, please figure out the order.
Feel free to send comments to gmail com aschenbach

Information on documentations, usage, support and knowledgebase of openssl, please contact openssl.org

DISCLAIMER:

This software package uses strong cryptography, so even if it is created, maintained and distributed from liberal countries in Europe (where it is legal to do this), it falls under certain export/import and/or use restrictions in some other parts of the world.

PLEASE REMEMBER THAT EXPORT/IMPORT AND/OR USE OF STRONG CRYPTOGRAPHY SOFTWARE, PROVIDING CRYPTOGRAPHY HOOKS OR EVEN JUST COMMUNICATING TECHNICAL DETAILS ABOUT CRYPTOGRAPHY SOFTWARE IS ILLEGAL IN SOME PARTS OF THE WORLD. SO, WHEN YOU IMPORT THIS PACKAGE TO YOUR COUNTRY, RE-DISTRIBUTE IT FROM THERE OR EVEN JUST EMAIL TECHNICAL SUGGESTIONS OR EVEN SOURCE PATCHES TO THE AUTHOR OR OTHER PEOPLE YOU ARE STRONGLY ADVISED TO PAY CLOSE ATTENTION TO ANY EXPORT/IMPORT AND/OR USE LAWS WHICH APPLY TO YOU. THE AUTHORS OF OPENSSL ARE NOT LIABLE FOR ANY VIOLATIONS YOU MAKE HERE. SO BE CAREFUL, IT IS YOUR RESPONSIBILITY.