Go to file
Kazuki Yamaguchi 9d5ac9532c Add SSL_CTX_get_ciphers()
Add an accessor for SSL_CTX.

Since libssl was made opaque, there is no way for users to access the
cipher_list, while users can set the cipher_list by
SSL_CTX_set_cipher_list().

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-04-11 09:59:04 -04:00
apps Fix the no-nextprotoneg option 2016-04-11 14:22:43 +01:00
Configurations Clean-up *_DEBUG options. 2016-04-07 21:18:00 +02:00
crypto Fix the no-posix-io option 2016-04-11 14:33:44 +01:00
demos Remove really old demo's 2016-03-07 14:56:12 -05:00
doc Add SSL_CTX_get_ciphers() 2016-04-11 09:59:04 -04:00
engines Fix forgotten adaptation to opaque RSA and RSA_METHOD 2016-04-07 02:17:35 +02:00
external/perl Adjust transfer::Text::Template.pm for alternate directory name 2016-02-12 18:04:49 +01:00
include Add SSL_CTX_get_ciphers() 2016-04-11 09:59:04 -04:00
ms set exec attribute for .pl files 2016-04-04 18:44:47 -04:00
ssl Add SSL_CTX_get_ciphers() 2016-04-11 09:59:04 -04:00
test Fix the no-tls option 2016-04-11 14:29:02 +01:00
tools Remove the remainder of util/mk1mf.pl and companion scripts 2016-03-21 11:02:00 +01:00
util Add SSL_CTX_get_ciphers() 2016-04-11 09:59:04 -04:00
VMS VMS: Harmonize the paths in openssl_startup.com with what's really installed 2016-03-29 20:26:43 +02:00
.gitignore Add apps/tsget and test/ssltest_old to .gitignore 2016-04-06 16:33:10 +02:00
.travis-create-release.sh Remove the -n tar flag from osx dist creation 2016-03-08 20:21:26 +01:00
.travis.yml Disable some sanitizer checks without PEDANTIC 2016-04-10 01:50:45 +02:00
ACKNOWLEDGEMENTS
appveyor.yml Appveyor - make sure to actually build "shared" in the shared configuration 2016-03-16 18:08:31 +01:00
build.info Build system: VC-WIN64I fixups. 2016-03-29 09:48:25 +02:00
CHANGES Adjust --strict-warnings builds in Travis 2016-04-10 01:50:16 +02:00
config config: fix off-by-centimeter-to-the-right typo. 2016-03-21 11:17:19 +01:00
config.com Harmonize the option processing in 'config' and 'config.com' 2016-03-10 14:20:50 +01:00
Configure Clean-up *_DEBUG options. 2016-04-07 21:18:00 +02:00
CONTRIBUTING Ask for tests in CONTRIBUTING 2016-01-25 17:12:57 -05:00
e_os.h Clean-up *_DEBUG options. 2016-04-07 21:18:00 +02:00
FAQ
INSTALL Adjust some default installation directories 2016-03-24 00:36:03 +01:00
INSTALL.DJGPP Refactor file writing - information on our use of Perl and Perl modules 2016-01-22 23:12:22 +01:00
INSTALL.WCE Refactor file writing - information on our use of Perl and Perl modules 2016-01-22 23:12:22 +01:00
LICENSE Update license year range to 2016 2016-01-19 10:24:05 -05:00
Makefile.in Remove the remainder of util/mk1mf.pl and companion scripts 2016-03-21 11:02:00 +01:00
Makefile.shared FreeBSD, at least, can restrict symbols in a shared library - so use the 2016-02-27 16:23:25 +00:00
NEWS Fix up CHANGES 2016-03-16 15:06:46 +01:00
NOTES.VMS Force argv to be an array of long pointers on VMS 2016-04-01 16:23:35 +02:00
NOTES.WIN Remove mk1mf documentation 2016-03-21 11:02:00 +01:00
openssl.spec GH781: openssl.spec: use secure urls 2016-03-03 19:45:13 -05:00
README README: small fixups 2016-03-17 22:48:13 +01:00
README.ECC
README.ENGINE Remove Ubsec engine 2016-02-26 23:34:25 +00:00
README.FIPS
README.PERL State the minimum Perl version that our scripts will work with 2016-02-11 22:11:48 +01:00

 OpenSSL 1.1.0-pre5-dev

 Copyright (c) 1998-2016 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
 Secure Sockets Layer (SSLv3) and Transport Layer Security (TLS) protocols as
 well as a full-strength general purpose cryptographic library. The project is
 managed by a worldwide community of volunteers that use the Internet to
 communicate, plan, and develop the OpenSSL toolkit and its related
 documentation.

 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
        INSTALL.DJGPP   DOS platform with DJGPP
        INSTALL.WCE     Windows CE

 SUPPORT
 -------

 See the OpenSSL website www.openssl.org for details on how to obtain
 commercial technical support.

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

    - Download the current snapshot from ftp://ftp.openssl.org/snapshot/
      to see if the problem has already been addressed
    - Remove ASM versions of libraries
    - Remove compiler optimisation flags

 If you wish to report a bug then please include the following information in
 any bug report:

    - On Unix systems:
        Self-test report generated by 'make report'
    - On other systems:
        OpenSSL version: output of 'openssl version -a'
        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)

 Email the report to:

    rt@openssl.org

 In order to avoid spam, this is a moderated mailing list, and it might
 take a day for the ticket to show up.  (We also scan posts to make sure
 that security disclosures aren't publically posted by mistake.) Mail
 to this address is recorded in the public RT (request tracker) database
 (see https://www.openssl.org/community/index.html#bugs for details) and
 also forwarded the public openssl-dev mailing list.  Confidential mail
 may be sent to openssl-security@openssl.org (PGP key available from the
 key servers).

 Please do NOT use this for general assistance or support queries.
 Just because something doesn't work the way you expect does not mean it
 is necessarily a bug in OpenSSL.

 You can also make GitHub pull requests. If you do this, please also send
 mail to rt@openssl.org with a link to the PR so that we can more easily
 keep track of it.

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

 See CONTRIBUTING

 LEGALITIES
 ----------

 A number of nations, in particular the U.S., 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.