- 13 Aug, 2015 7 commits
-
-
Richard Levitte authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Rich Salz authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
Process the Certificate Status message using the PACKET API Reviewed-by:
Emilia Käsper <emilia@openssl.org>
-
Matt Caswell authored
Enhance the PACKET code readability, and fix a stale comment. Thanks to Ben Kaduk (bkaduk@akamai.com) for pointing this out. Reviewed-by:
Emilia Käsper <emilia@openssl.org>
-
Matt Caswell authored
The new ClientHello PACKET code is missing a return value check. Reviewed-by:
Emilia Käsper <emilia@openssl.org>
-
Ismo Puustinen authored
Part of RT 3997 Per Ben, just jump to common exit code. Signed-off-by:
Rich Salz <rsalz@akamai.com> Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
Use the PACKET API to process an incoming server Certificate message. Reviewed-by:
Emilia Käsper <emilia@openssl.org>
-
- 12 Aug, 2015 3 commits
-
-
Dr. Stephen Henson authored
PR#3974 PR#3975 Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Dr. Stephen Henson authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
- 11 Aug, 2015 13 commits
-
-
Rich Salz authored
This was obsolete in 2001. This is not the same as Gost94 digest. Thanks to Dmitry Belyavsky <beldmit@gmail.com> for review and advice. Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
When config'd with "sctp" running "make test" causes a seg fault. This is actually due to the way ssltest works - it dives under the covers and frees up BIOs manually and so some BIOs are NULL when the SCTP code does not expect it. The simplest fix is just to add some sanity checks to make sure the BIOs aren't NULL before we use them. This problem occurs in master and 1.0.2. The fix has also been applied to 1.0.1 to keep the code in sync. Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
Matt Caswell authored
There are some missing return value checks in the SCTP code. In master this was causing a compilation failure when config'd with "--strict-warnings sctp". Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
Matt Caswell authored
Run a "make update" for the OSSLTest Engine changes Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Richard Levitte authored
Use a dynamic engine for ossltest engine so that we can build it without subsequently deploying it during install. We do not want people accidentally using this engine. Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
When using an anon DH ciphersuite a client should reject a 0 value for p. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
Add ServerHello parsing to TLSProxy. Also add some (very) limited ServerKeyExchange parsing. Add the capability to set client and server cipher lists Fix a bug with fragment lengths Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
Two tests are added: one is a simple version tolerance test; the second is a test to ensure that OpenSSL operates correctly in the case of a zero length extensions block. The latter was broken inadvertently (now fixed) and it would have been helpful to have a test case for it. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
This commit provides a set of perl modules that support the testing of libssl. The test harness operates as a man-in-the-middle proxy between s_server and s_client. Both s_server and s_client must be started using the "-testmode" option which loads the new OSSLTEST engine. The test harness enables scripts to be written that can examine the packets sent during a handshake, as well as (potentially) modifying them so that otherwise illegal handshake messages can be sent. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
This engine is for testing purposes only. It provides crippled crypto implementations and therefore must not be used in any instance where security is required. This will be used by the forthcoming libssl test harness which will operate as a man-in-the-middle proxy. The test harness will be able to modify TLS packets and read their contents. By using this test engine packets are not encrypted and MAC codes always verify. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Matt Caswell authored
The function BN_MONT_CTX_set was assuming that the modulus was non-zero and therefore that |mod->top| > 0. In an error situation that may not be the case and could cause a seg fault. This is a follow on from CVE-2015-1794. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Guy Leaver (guleaver) authored
If a client receives a ServerKeyExchange for an anon DH ciphersuite with the value of p set to 0 then a seg fault can occur. This commits adds a test to reject p, g and pub key parameters that have a 0 value (in accordance with RFC 5246) The security vulnerability only affects master and 1.0.2, but the fix is additionally applied to 1.0.1 for additional confidence. CVE-2015-1794 Reviewed-by:
Richard Levitte <levitte@openssl.org> Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
make errors wants things in a different order to the way things are currently defined in the header files. The easiest fix is to just let it reorder it. Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
- 10 Aug, 2015 4 commits
-
-
Rich Salz authored
Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Rich Salz authored
Especially since after the #ifdef cleanups this is not useful. Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Rich Salz authored
Reviewed-by:
Viktor Dukhovni <viktor@openssl.org>
-
Ben Laurie authored
Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
- 08 Aug, 2015 2 commits
-
-
bluelineXY authored
Add Host Header in OCSP query if no host header is set via -header Signed-off-by:
Rich Salz <rsalz@akamai.com> Reviewed-by:
Ben Laurie <ben@openssl.org>
-
David Woodhouse authored
Signed-off-by:
Rich Salz <rsalz@akamai.com> Reviewed-by:
Ben Laurie <ben@openssl.org>
-
- 06 Aug, 2015 4 commits
-
-
Adam Eijdenberg authored
We could just initialize it, but to be consistent with the rest of the file it seemed to make more sense to just drop. Reviewed-by:
Ben Laurie <ben@openssl.org> Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
This reverts commit 704563f0 . Reverting in favour of the next commit which removes the underlying cause of the warning. Reviewed-by:
Ben Laurie <ben@openssl.org>
-
Ben Laurie authored
Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Anton Blanchard authored
Signed-off-by:
Rich Salz <rsalz@openssl.org> Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
- 04 Aug, 2015 7 commits
-
-
Adam Eijdenberg authored
Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Adam Eijdenberg authored
--strict-warnings started showing warnings for this today... Surely an error should be raised if these reads fail? Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
Matt Caswell <matt@openssl.org>
-
Matt Caswell authored
The -use_srtp s_client/s_server option is supposed to take a colon separated string as an argument. In master this was incorrectly set to expect a filename. Reviewed-by:
Rich Salz <rsalz@openssl.org>
-
Matt Caswell authored
Change NextProto message processing to use the PACKET API. Reviewed-by:
Stephen Henson <steve@openssl.org>
-
Matt Caswell authored
Modify CertificateVerify processing to use the new PACKET API. Reviewed-by:
Stephen Henson <steve@openssl.org>
-
Matt Caswell authored
Use the PACKET API for processing ClientCertificate messages Reviewed-by:
Tim Hudson <tjh@openssl.org>
-
Matt Caswell authored
Some of the PACKET functions were returning incorrect data. An unfortunate choice of test data in the unit test was masking the failure. Reviewed-by:
Tim Hudson <tjh@openssl.org>
-