Go to file
Richard Levitte a87c159f19 Fix freeze in config's interrupt trap with some shells
With bash and zsh, the trap on the 5 second read does respond, but
doesn't break out of the read.  What's worse is that it takes away the
5 second timer, and therefore has the read hang indefinitely and
(almost) unbreakable.

Having the trap do 'exit 0' after reseting the tty params has it break
out of read and continue with the configuration.

Other shells do not appear to have the issue described here, but
neither does the extra 'exit 0' appear to harm them.

Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-03-14 11:24:55 +01:00
apps Make X509_SIG opaque. 2016-03-11 17:40:47 +00:00
Configurations Fix a few Configure errors 2016-03-14 11:21:35 +01:00
crypto Change an function macro for ERR match the function it's used in. 2016-03-13 14:54:51 +01:00
demos
doc Document X509_get_serialNumber and X509_set_serialNumber. 2016-03-14 00:23:13 +00:00
engines Add $(LIB_CFLAGS) for any build.info generator that uses $(CFLAGS) 2016-03-13 00:02:55 +01:00
external/perl
include Make X509_SIG opaque. 2016-03-11 17:40:47 +00:00
ms remove ms/.rnd and add it to .gitignore 2016-03-09 20:58:32 -05:00
Netware
os2
ssl Fix no-comp build 2016-03-12 16:21:33 +01:00
test Fix build break; add function declaration 2016-03-11 20:36:33 -05:00
tools
util removed extra define 2016-03-11 14:34:26 -05:00
VMS
.gitignore Update .gitignore to ignore all cscope files 2016-03-09 20:59:21 -05:00
.travis-create-release.sh
.travis.yml Workaround for false -Warray-bounds in Travis 2016-03-12 17:57:01 +01:00
ACKNOWLEDGEMENTS
appveyor.yml
build.info
CHANGES Review comments 2016-03-11 10:39:10 -05:00
config Fix freeze in config's interrupt trap with some shells 2016-03-14 11:24:55 +01:00
config.com Harmonize the option processing in 'config' and 'config.com' 2016-03-10 14:20:50 +01:00
Configure Enforce the demand for Perl 5.10.0 as a minimum. 2016-03-14 11:21:35 +01:00
CONTRIBUTING
e_os.h Allow OPENSSL_NO_SOCK in e_os.h even for non-Windows/DOS platforms 2016-03-10 10:56:23 +01:00
FAQ
INSTALL More tweaks to the installation instructions 2016-03-11 10:00:39 +00:00
INSTALL.DJGPP
INSTALL.NW
INSTALL.OS2
INSTALL.WCE
LICENSE
Makefile.in Add blake2 support. 2016-03-11 10:39:10 -05:00
Makefile.shared
NEWS Update CHANGES and NEWS 2016-03-09 15:31:22 +00:00
NOTES.VMS
NOTES.WIN Adapt INSTALL and related notes for Windows 2016-03-09 11:22:07 +01:00
openssl.spec
README
README.ECC
README.ENGINE
README.FIPS
README.PERL

 OpenSSL 1.1.0-pre4-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.a:
     Provides the client and server-side implementations for SSLv3 and TLS.

 libcrypto.a:
     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, etc.
        INSTALL.DJGPP   DOS platform with DJGPP
        INSTALL.NW      Netware
        INSTALL.OS2     OS/2
        INSTALL.VMS     VMS
        INSTALL.WIN     Windows
        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.