TLS/SSL and crypto library https://www.openssl.org

Nicola Tuveri a3b54f0f5d Fix no-ec2m in ec_curve.c (1.1.0) il y a 5 ans
Configurations e32bc855a8 Fix default installation paths on mingw il y a 5 ans
VMS 46117d31fe dasync is an internal testing engine, so don't install it il y a 8 ans
apps f4764841dc Update copyright year il y a 5 ans
crypto a3b54f0f5d Fix no-ec2m in ec_curve.c (1.1.0) il y a 5 ans
demos 38c23e647f Spelling doc #3580 il y a 7 ans
doc d742232027 Update copyright year il y a 5 ans
engines a8e613cc51 Update copyright year il y a 6 ans
external 6244f53177 Update copyright year il y a 6 ans
fuzz 6244f53177 Update copyright year il y a 6 ans
include 4eabf3d654 Prepare for 1.1.0m-dev il y a 5 ans
ms 6244f53177 Update copyright year il y a 6 ans
os-dep 6c4be50a5d Move Haiku configuration to separate config file to denote il y a 8 ans
ssl d742232027 Update copyright year il y a 5 ans
test f4764841dc Update copyright year il y a 5 ans
tools 1850451676 Add -h and -help for c_rehash script and app il y a 8 ans
util 403783ce05 Have util/mktar.sh display the absolute path to the tarball il y a 6 ans
.gitattributes 58381f26c2 Don't export the submodules 'boringssl', 'krb5' and 'pyca-cryptography' il y a 6 ans
.gitignore 55b1542ca5 Add a compile time test to verify that openssl/rsa.h and complex.h can il y a 6 ans
.travis-apt-pin.preferences f114b91461 Fix travis clang-3.9 builds il y a 7 ans
.travis-create-release.sh b97cbe05a3 Remove all 'make dist' artifacts il y a 6 ans
.travis.yml 10fe37dd1b Try to work around ubuntu gcc-5 ubsan build failure il y a 6 ans
ACKNOWLEDGEMENTS ab29c82a55 Refer to website for acknowledgements. il y a 9 ans
AUTHORS e0a651945c Copyright consolidation: perl files il y a 8 ans
CHANGES 4eabf3d654 Prepare for 1.1.0m-dev il y a 5 ans
CONTRIBUTING fca038db55 Add a note on CHANGES and NEWS in CONTRIBUTING il y a 6 ans
Configure f4764841dc Update copyright year il y a 5 ans
FAQ 4f46473a86 Move FAQ to the web. il y a 9 ans
INSTALL 853d245362 Improve wording il y a 6 ans
LICENSE 1d01aeeca4 Update the license end year il y a 6 ans
Makefile.shared b15a19c148 Makefile.shared: fix to allow strings and spaces in passed variables il y a 5 ans
NEWS 4eabf3d654 Prepare for 1.1.0m-dev il y a 5 ans
NOTES.DJGPP 07930a75a1 Slight cleanup of the collection of READMEs, INSTALLs and NOTES il y a 8 ans
NOTES.PERL 073b1b72f6 Tweaks to NOTES.PERL il y a 8 ans
NOTES.UNIX 41371618f7 Add NOTES.UNIX, with a description on how to deal with runpaths il y a 7 ans
NOTES.VMS e8fd2a4cb4 Add a note about a perl issue on VMS and how to work around it il y a 8 ans
NOTES.WIN e32bc855a8 Fix default installation paths on mingw il y a 5 ans
README 4eabf3d654 Prepare for 1.1.0m-dev il y a 5 ans
README.ECC c5ee394b58 Add NSA sublicense info. il y a 13 ans
README.ENGINE 766579ec89 Remove Ubsec engine il y a 8 ans
README.FIPS 700b4a4ae7 Remove more (rest?) of FIPS build stuff. il y a 9 ans
appveyor.yml f1e92861c3 CI config: no need to make both install and install_docs il y a 6 ans
build.info 8842005e75 Have the VMS shared library file names contain the shared version il y a 8 ans
config a8e613cc51 Update copyright year il y a 6 ans
config.com f520f134d1 Update copyright year il y a 6 ans
e_os.h 7c188d4af0 Remove NO_DIRENT; it isn't used anywhere il y a 7 ans

README


OpenSSL 1.1.0m-dev

Copyright (c) 1998-2019 The OpenSSL Project
Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
All rights reserved.

DESCRIPTION
-----------

The OpenSSL Project is a collaborative effort to develop a robust,
commercial-grade, fully featured, and Open Source toolkit implementing the
Transport Layer Security (TLS) protocols (including SSLv3) as well as a
full-strength general purpose cryptographic library.

OpenSSL is descended from the SSLeay library developed by Eric A. Young
and Tim J. Hudson. The OpenSSL toolkit is licensed under a dual-license (the
OpenSSL license plus the SSLeay license), which means that you are free to
get and use it for commercial and non-commercial purposes as long as you
fulfill the conditions of both licenses.

OVERVIEW
--------

The OpenSSL toolkit includes:

libssl (with platform specific naming):
Provides the client and server-side implementations for SSLv3 and TLS.

libcrypto (with platform specific naming):
Provides general cryptographic and X.509 support needed by SSL/TLS but
not logically part of it.

openssl:
A command line tool that can be used for:
Creation of key parameters
Creation of X.509 certificates, CSRs and CRLs
Calculation of message digests
Encryption and decryption
SSL/TLS client and server tests
Handling of S/MIME signed or encrypted mail
And more...

INSTALLATION
------------

See the appropriate file:
INSTALL Linux, Unix, Windows, OpenVMS, ...
NOTES.* INSTALL addendums for different platforms

SUPPORT
-------

See the OpenSSL website www.openssl.org for details on how to obtain
commercial technical support. Free community support is available through the
openssl-users email list (see
https://www.openssl.org/community/mailinglists.html for further details).

If you have any problems with OpenSSL then please take the following steps
first:

- Download the latest version from the repository
to see if the problem has already been addressed
- Configure with no-asm
- Remove compiler optimisation flags

If you wish to report a bug then please include the following information
and create an issue on GitHub:

- OpenSSL version: output of 'openssl version -a'
- Any "Configure" options that you selected during compilation of the
library if applicable (see INSTALL)
- OS Name, Version, Hardware platform
- Compiler Details (name, version)
- Application Details (name, version)
- Problem Description (steps that will reproduce the problem, if known)
- Stack Traceback (if the application dumps core)

Just because something doesn't work the way you expect does not mean it
is necessarily a bug in OpenSSL. Use the openssl-users email list for this type
of query.

HOW TO CONTRIBUTE TO OpenSSL
----------------------------

See CONTRIBUTING

LEGALITIES
----------

A number of nations restrict the use or export of cryptography. If you
are potentially subject to such restrictions you should seek competent
professional legal advice before attempting to develop or distribute
cryptographic code.