Binary distributions of OpenSSL static libraries
The official source of OpenSSL software is the OpenSSL website. One can download OpenSSL source codes archives and compile them for a given platform. The compilation work can sometimes be quite tedious and may require a specific knowledge or tools, especially for exotic platforms.
We, at TeskaLabs, set up this page because we frequently compile OpenSSL for various platforms for our internal purposes and this may save some time to other developers. Binary distribution archives available on this page contains a statically linked OpenSSL libraries and header files. There are no other files (such as binaries like ./bin/openssl) included in this distribution. Developers can directly use them in their projects and save a bit of time.
Please let us know (via Twitter, LinkedIn, Facebook) if you like our work or if you want to comment.
This page is updated time to time with newer versions of OpenSSL libraries or new platforms.
Android
OpenSSL 1.0.2t for Android
CPU architectures: arm64-v8a, armeabi-v7a, x86, x86_64
SHA-256: 59d6eeabd7d558b85cf2d0f7a941f10ea92cd048273cab6279d7a82da3564c94
Compiled by Android NDK Revision 15c from July 2017 (the last one with GCC).
Binary distribution created at 27nd Nov 2019
OpenSSL 1.0.2o for Android
CPU architectures: arm64-v8a, armeabi, armeabi-v7a, x86, x86_64, mips, mips64
SHA-256: 9612a455858774c3fa9708eaa81fd436026f337c818d687a2d3cc20b7555a870
Compiled by Android NDK 16.1.4479499
Binary distribution created at 27nd Apr 2018
OpenSSL 1.0.2n for Android
CPU architectures: arm64-v8a, armeabi, armeabi-v7a, x86, x86_64, mips, mips64
SHA-256: 6e7acdb6620b54e4ef1cedfcfe11603ed3f48c0b0e5711362881b486eed07eb1
Compiled by Android NDK 15.2.4203891
Binary distribution created at 23rd Dec 2017
iOS
OpenSSL 1.0.2o for iOS
CPU architectures: armv7, armv7s, arm64, i386 (Simulator), x86_64 (Simulator)
SHA-256: d487ccdff18262eca87dd152bdc3a00562187877f1acb2f2d002032be31303e5
Compiled by iOS SDK 11.2 (15C107) & Xcode 9.2 (9C40b)
Binary distribution created at 27nd Apr 2018
OpenSSL 1.0.2n for iOS
CPU architectures: armv7, armv7s, arm64, i386 (Simulator), x86_64 (Simulator)
SHA-256: 47555c61a9ca827d9e0bced39b274f6bffdb0de300e3283b207c02d9e01f2948
Compiled by iOS SDK 11.2 (15C107)
Binary distribution created at 23rd Dec 2017
Windows
OpenSSL 1.0.2s for Windows (64 bit, Mingw-w64)
SHA-256: 90122e978aa87f335726f1f4a7e79cb0b2492b7e54032d33a7747e349533fd0a
Compiled by Mingw-w64 gcc 9.1.0
Binary distribution created at 6th July 2019
Build process:
./Configure mingw64 -fPIC --prefix=/opt/openssl
PATH=/mingw64/bin:${PATH} make depend
PATH=/mingw64/bin:${PATH} make
PATH=/mingw64/bin:${PATH} make installOpenSSL 1.0.2l for Windows i686 (32 bit)
SHA-256: 1db5347e3ba09edf299b3a674ecc717a5dbee9efa2a9ff172aa52984aedb66f6
Compiled by MSVC 2013
Binary distribution created at 6th Aug 2017
Windows Phone 8.1
OpenSSL 1.0.2l for Windows Phone 8.1 ARM
SHA-256: 31d8349e1b37f776eadd070bd09ecb3943ee980a67caf967b6f1cb8ef1b9b257
Compiled by MSVC 2015
Binary distribution created at 6th Aug 2017
OpenSSL 1.0.2l for Windows Phone 8.1 x86 (32bit)
SHA-256: 432c026342abaf56ed2286c2264444a3c8b4cc123fd8ebba37b866b44505cf44
Compiled by MSVC 2015
Binary distribution created at 6th Aug 2017
LEGAL NOTICE: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
THIS SOFTWARE IS PROVIDED``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL TeskaLabs Ltd BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Most Recent Articles
- A beginner-friendly intro to the Correlator for effective cybersecurity detection
- Inotify in ASAB Library
- From State Machine to Stateless Microservice
- Entangled ways of product development in the area of cybersecurity #3 - LogMan.io
- Entangled ways of product development in the area of cybersecurity #2 - BitSwan
You Might Be Interested in Reading These Articles
How to Teach Your Kids to Safely Play Pokemon GO
This summer something strange has occurred in my household. Suddenly, all of my children ranging in age from 9 to 18 are willingly piling into our van the minute I mention driving anywhere- even to the grocery store. And it’s not my company or the possibility of picking out this week’s cereal they are seeking. No, they are merely wanting a ride to aid them on their hunt for elusive Pokémon.
Published on August 30, 2016
Building a private cloud on AMD Ryzen and Linux Containers
At our company, we develop our own software products that we offer to our clients and often also run ourselves. So far our company has operated its IT infrastructure — about 30 virtual servers—on a public cloud, specifically on MS Azure.
Published on July 01, 2018
Google has introduced new rules about how mobile app developers and companies deal with customer impact on apps across the board. What is it?
The new regulations call for increased transparency with regards to how apps make use of customer data. Developers need to ensure that the way they handle user data - from how they collect it to what it might be used for - is perfectly clear to all users. In Google’s words, developers must “limit the use of the data to the description in the disclosure”. In layman’s terms, this means that data use and privacy policies need to be clearly visible on app descriptions in the Google Play store, and not simply within the app itself.
Published on October 10, 2017