Go to file
Richard Levitte b83ace3162 Rearrange test/recipes/95-test_*.t to use skip_all
The conditions to skip these recipes entirely don't show in a
non-verbose test harness output.  We prefer to know, so use skip_all,
as it is a little bit more verbose.

[extended tests]

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/3398)
2017-05-05 23:10:41 +02:00
.github Remind people to have 'Fixes #XXXX' in the commit message 2017-04-02 21:51:47 +02:00
apps Add the -groups option to s_server/s_client 2017-05-03 16:39:32 +01:00
boringssl@2070f8ad91 Update ossl_config.json for later BoringSSL commit 2017-03-14 12:12:13 +00:00
Configurations VMS: Make sure to include MAIN from static libraries if needed 2017-04-24 18:09:01 +02:00
crypto sha/sha512.c: fix formatting. 2017-05-05 17:04:09 +02:00
demos Remove outdated and unsupported CHIL engine 2017-05-04 15:45:57 -04:00
doc Remove some out of date text inadvertently left behind 2017-05-05 08:28:56 +01:00
engines check length sanity before correcting in EVP_CTRL_AEAD_TLS1_AAD 2017-04-24 11:19:56 -04:00
external/perl
fuzz fuzz/{client,server}.c: omit _time64 "overload method". 2017-04-27 13:01:08 +02:00
include Update the TLSv1.3 version indicator for draft-20 2017-05-03 17:23:02 +01:00
krb5@b9ad6c4950 [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
ms
os-dep
pyca-cryptography@6c5a519f9b Update the pyca-cryptography submodule to version 1.8.1 2017-04-28 18:04:52 +02:00
ssl Updates to serverinfo fix based on review feedback 2017-05-04 16:02:08 +01:00
test Rearrange test/recipes/95-test_*.t to use skip_all 2017-05-05 23:10:41 +02:00
tools
util Fix curly braces on util/mkrc.pl 2017-05-03 14:16:58 -04:00
VMS
.gitattributes
.gitignore Ignore all .a files, not just the top ones 2017-04-25 18:29:31 +02:00
.gitmodules [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
.travis-create-release.sh
.travis.yml [extended tests] Enable krb5 tests in Travis 2017-04-18 19:10:25 +02:00
ACKNOWLEDGEMENTS
appveyor.yml appveyor.yml: split {build,test}_scripts to avoid exit code masking. 2017-04-08 10:55:32 +02:00
AUTHORS
build.info
CHANGES Ensure s_client sends an SNI extension by default 2017-04-27 11:43:55 +01:00
config Better way to recognise mingw64 in config script 2017-03-13 21:41:20 +01:00
config.com
Configure Remove duplicates from clang_devteam_warnings 2017-05-01 14:23:28 -04:00
CONTRIBUTING
e_os.h e_os.h: drop now-redundant PRIu64 [and fix OSSLzu]. 2017-03-30 19:34:24 +02:00
FAQ
INSTALL Make the TLSv1.3 downgrade mechanism a configurable option 2017-03-24 14:07:11 +00:00
LICENSE Update year, wording tweak 2017-02-28 10:13:32 -05:00
Makefile.shared Code health: Remove base address setting for mingw 2017-02-28 21:31:32 +01:00
NEWS Update CHANGES and NEWS for new release 2017-02-16 10:10:05 +00:00
NOTES.DJGPP
NOTES.PERL
NOTES.UNIX Add NOTES.UNIX, with a description on how to deal with runpaths 2017-03-02 07:33:27 +01:00
NOTES.VMS More typo fixes 2017-03-29 07:14:29 +02:00
NOTES.WIN NOTES.WIN: mention Strawberry Perl as option. 2017-03-15 12:17:52 +01:00
README
README.ECC
README.ENGINE
README.FIPS

 OpenSSL 1.1.1-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
 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.