TLS/SSL and crypto library
Find a file
Matt Caswell 75dd6c1a39 Fix s_client/s_server waiting for stdin on Windows
On Windows we were using the function _kbhit() to determine whether there
was input waiting in stdin for us to read. Actually all this does is work
out whether there is a keyboard press event waiting to be processed in the
input buffer. This only seems to work in a standard Windows console (not
Msys console) and also doesn't work if you redirect the input from some
other source (as we do in TLSProxy tests). This commit changes things to
work differently depending on whether we are on the Windows console or not.

RT#4255

Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-05-27 15:18:46 +01:00
apps Fix s_client/s_server waiting for stdin on Windows 2016-05-27 15:18:46 +01:00
Configurations Complete the list of files to clean up on Windows 2016-05-25 00:46:00 +02:00
crypto Prevent an overflow when trying to print excessively big floats 2016-05-27 10:23:18 +01:00
demos Consolidate copyright for demos 2016-05-18 09:23:31 -04:00
doc Update the documentation of BN_hex2bn() 2016-05-27 10:05:44 +01:00
engines build.info files: add quotes around any spec that may contain spaces 2016-05-25 11:50:44 +02:00
external/perl Copyright consolidation; .pm and Configure 2016-04-20 10:40:05 -04:00
fuzz Add fuzzing! 2016-05-07 18:13:54 +01:00
include Add error return for OPENSSL_INIT_set_config_filename() 2016-05-23 23:30:24 +01:00
ms Copyright consolidation: perl files 2016-04-20 09:45:40 -04:00
os-dep Move Haiku configuration to separate config file to denote 2016-05-19 22:39:52 +02:00
ssl Fix some suspect warnings on Windows 2016-05-26 17:18:39 +01:00
test Silence some "may be uninitialized when used" warning 2016-05-27 14:59:47 +01:00
tools Make sure tsget and c_rehash are named with .pl suffix on Windows and VMS 2016-05-23 21:48:42 +02:00
util Remove unused error/function codes. 2016-05-23 15:04:23 -04:00
VMS Make sure tsget.pl and c_rehash.pl get installed on VMS and Windows. 2016-05-23 21:48:42 +02:00
.gitattributes *.der files are binary. 2016-04-26 13:45:20 +01:00
.gitignore Add text/x509aux to gitignore 2016-05-23 13:55:16 +01:00
.travis-create-release.sh Remove the -n tar flag from osx dist creation 2016-03-08 20:21:26 +01:00
.travis.yml Try 'make install' with one of the Travis configurations 2016-05-03 12:28:49 +02:00
ACKNOWLEDGEMENTS Refer to website for acknowledgements. 2015-12-08 16:07:09 -05:00
appveyor.yml Update Travis and Appveyor for change to shared by default 2016-04-14 22:23:12 +01:00
AUTHORS Copyright consolidation: perl files 2016-04-20 09:45:40 -04:00
build.info build.info files: add quotes around any spec that may contain spaces 2016-05-25 11:50:44 +02:00
CHANGES Rename lh_xxx,sk_xxx tp OPENSSL_{LH,SK}_xxx 2016-05-20 10:48:29 -04:00
config Add a case for 64-bit OS X in config 2016-05-12 10:54:25 +02:00
config.com Harmonize the option processing in 'config' and 'config.com' 2016-03-10 14:20:50 +01:00
Configure Configure: pull 'which' back. 2016-05-25 23:50:40 +02:00
CONTRIBUTING Recommend GH over RT, per team vote. 2016-05-11 16:43:27 -04:00
e_os.h Handle Visual C warning about non-standard function names. 2016-05-26 00:48:23 +02:00
FAQ Move FAQ to the web. 2015-08-16 19:02:29 -04:00
INSTALL Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
LICENSE Copyright consolidation 07/10 2016-05-17 14:51:26 -04:00
Makefile.shared Makefile.shared: revert Haiku support commit. 2016-05-25 23:47:55 +02:00
NEWS Manual fixes after copyright consolidation 2016-05-17 17:38:18 -04:00
NOTES.DJGPP Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
NOTES.PERL Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
NOTES.VMS Force argv to be an array of long pointers on VMS 2016-04-01 16:23:35 +02:00
NOTES.WIN Windows notes: add a few lines on gaining admin privs for installing 2016-05-23 22:24:13 +02:00
README Slight cleanup of the collection of READMEs, INSTALLs and NOTES 2016-05-23 16:02:53 +02:00
README.ECC Add NSA sublicense info. 2011-05-11 12:50:57 +00:00
README.ENGINE Remove Ubsec engine 2016-02-26 23:34:25 +00:00
README.FIPS Remove more (rest?) of FIPS build stuff. 2016-01-06 12:07:26 -05:00

 OpenSSL 1.1.0-pre6-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, ...
        NOTES.*         INSTALL addendums for different platforms

 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.