- 02 Nov, 2016 3 commits
-
-
Matt Caswell authored
Includes addition of the various options to s_server/s_client. Also adds one of the new TLS1.3 ciphersuites. This isn't "real" TLS1.3!! It's identical to TLS1.2 apart from the protocol and the ciphersuite...and the ciphersuite is just a renamed TLS1.2 one (not a "real" TLS1.3 ciphersuite). Reviewed-by:Rich Salz <rsalz@openssl.org>
-
Emilia Kasper authored
Reviewed-by: -
Richard Levitte authored
Forks will have to define their own Reviewed-by:
-
- 01 Nov, 2016 4 commits
-
-
Todd Short authored
For convenience, combine getting a new ref for the new SSL_CTX with assigning the store and freeing the old one. Reviewed-by:
Matt Caswell <matt@openssl.org> Reviewed-by:
-
Mike Aizatsky authored
Reviewed-by:
Kurt Roeckx <kurt@roeckx.be> Reviewed-by:
-
Benjamin Kaduk authored
Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
-
Rich Salz authored
This reverts commit ca1574ce . Not suitabled for a minor release as it breaks the ABI. Reviewed-by:
-
- 31 Oct, 2016 5 commits
-
-
Richard Levitte authored
Reviewed-by:
Andy Polyakov <appro@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1802)
-
Richard Levitte authored
Fixes #1781 Reviewed-by:
-
Andy Polyakov authored
Reviewed-by: -
Rich Salz authored
Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
-
Richard Levitte authored
VC-noCE-common and VC-WIN64-common were missing this line: template => 1, Fixes GH#1809 Reviewed-by:
-
- 28 Oct, 2016 19 commits
-
-
Benjamin Kaduk authored
After the recent reworking, not everything matched up, and some comments didn't catch up to the outl-->dlen and inl-->dlen renames that happened during the development of the recent patches. Try to make parameter names consistent across header, implementation, and manual pages. Also remove some trailing whitespace that was inadvertently introduced. Reviewed-by:
-
Benjamin Kaduk authored
Make it clear that the OPENSSL_LOCAL_CONFIG_DIR settings take precedence over the in-tree configs. Reviewed-by:
-
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Rename some parameters; add some error codes; fix a comment; etc Reviewed-by: -
Matt Caswell authored
Make sure the return value isn't bigger than the buffer len Reviewed-by: -
Matt Caswell authored
Based on feedback received. Reviewed-by: -
Matt Caswell authored
Rename some parameters. Also change handling of buffer sizes >INT_MAX in length. Reviewed-by: -
Matt Caswell authored
They should return 0 for a failure (retryable or not), and 1 for a success. Reviewed-by: -
Matt Caswell authored
In converting a new style BIO_read() call into an old one, read as much data as we can (INT_MAX), if the size of the buffer is >INT_MAX. Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Reviewed-by: -
Matt Caswell authored
Also extend BIO_METHOD to be able to supply an implementation for the new BIO_write_ex function. Reviewed-by: -
Matt Caswell authored
Also extend BIO_METHOD to be able to supply an implementation for the new BIO_read function. Reviewed-by: -
Matt Caswell authored
Providing a spkac file with no default section causes a double free. Thanks to Brian Carpenter for reporting this issue. Reviewed-by:Kurt Roeckx <kurt@openssl.org>
-
Matt Caswell authored
A BIO_read() 0 return indicates that a failure occurred that may be retryable. An SSL_read() 0 return indicates a non-retryable failure. Check that if BIO_read() returns 0, SSL_read() returns <0. Same for SSL_write(). The asyncio test filter BIO already returns 0 on a retryable failure so we build on that. Reviewed-by: -
Matt Caswell authored
A zero return from BIO_read()/BIO_write() could mean that an IO operation is retryable. A zero return from SSL_read()/SSL_write() means that the connection has been closed down (either cleanly or not). Therefore we should not propagate a zero return value from BIO_read()/BIO_write() back up the stack to SSL_read()/SSL_write(). This could result in a retryable failure being treated as fatal. Reviewed-by:
-
- 26 Oct, 2016 4 commits
-
-
Matt Caswell authored
Reviewed-by: -
Rich Salz authored
Move manpages to manX directories Add Windows/VMS install fix from Richard Levitte Update README Fix typo's Remove some duplicates Reviewed-by: -
Richard Levitte authored
The current version of the VMS compiler provides C99 features, strictly language wise. Unfortunately, even the most recent standard library isn't fully updated for that standard, so we need to use an earlier standard that the compiler supports. Most importantly, this affects the __STDC_VERSION__ value, which the compiler unfortunately currently defaults to 199901L. With this change we won't have to give VMS special treatment when looking for features based on that macro. Reviewed-by:
-
Rich Salz authored
Reviewed-by:
-
- 25 Oct, 2016 2 commits
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
This is overdue since the addition of the unified build system Reviewed-by:
-
- 24 Oct, 2016 3 commits
-
-
Andy Polyakov authored
[And remove FPU mutiplication subroutine.] Reviewed-by: -
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by:
-
