- Mar 02, 2017
-
-
Matt Caswell authored
Check whether we negotiate compression in various scenarios. Reviewed-by:
Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2814)
-
Matt Caswell authored
do_ssl3_write() was crashing when compression was enabled. We calculate the maximum length that a record will be after compression and reserve those bytes in the WPACKET. Unfortunately we were adding the maximum compression overhead onto the wrong variable resulting in a corrupted record. Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Robert Scheck authored
Based on initial patch by Alex Bergmann <alex@linlab.net> and new function ldap_ExtendedResponse_parse() by Andy Polyakov <appro@openssl.org>. Thanks very much to both. Reviewed-by:
Andy Polyakov <appro@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2293)
-
Andy Polyakov authored
GH#2816 Reviewed-by:
Richard Levitte <levitte@openssl.org>
-
Andy Polyakov authored
Private hstrerror was introduced to address linking problem on HP-UX, but truth be told conemporary systems, HP-UX included, wouldn't come to that call, they would use getaddrinfo and gai_strerror, while gethostbyname and h_errno are there to serve legacy systems. Since legacy systems are naturally disappearing breed, we can as well just let user interpret number. GH#2816 Reviewed-by:
-
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
[skip ci] Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
-
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by: -
Jon Spillett authored
Reviewed-by:
Matt Caswell <matt@openssl.org> Reviewed-by:
-
Andy Polyakov authored
For pull requests not tagged with [extended tests]: - short-curcuit most expensive fuzz and install tests; - skip over non-shared builds; Reviewed-by:
-
Andy Polyakov authored
Reviewed-by:
-
Richard Levitte authored
[skip ci] Reviewed-by:
-
- Mar 01, 2017
-
-
Bernd Edlinger authored
Reviewed-by:
-
Andy authored
CLA: trivial Reviewed-by:
-
Richard Levitte authored
With VMS C, the second parameter takes a 32-bit pointer. When building with 64-bit pointer size default, we must compensate. Reviewed-by:
-
Richard Levitte authored
Use EVP_CIPHER_CTX_reset() instead Reviewed-by:
-
Emilia Kasper authored
- FLAT_INC - PKCS1_CHECK (the SSL_OP_PKCS1_CHECK options have been no-oped) - PKCS_TESTVECT (debugging leftovers) - SSL_AD_MISSING_SRP_USERNAME (unfinished feature) - DTLS_AD_MISSING_HANDSHAKE_MESSAGE (unfinished feature) - USE_OBJ_MAC (note this removes a define from the public header but very unlikely someone would be depending on it) - SSL_FORBID_ENULL Reviewed-by:
Stephen Henson <steve@openssl.org> Reviewed-by:
-
Benjamin Kaduk authored
It's undocumented and unused in the tree. The idea seems to have never gained much traction, and can be removed without breaking ABI compatibility. Reviewed-by:
-
Benjamin Kaduk authored
Cleanse instead, and free in the free routine. Seems to have been introduced in commit 846ec07d when EVP_CIPHER_CTX was made opaque. Reviewed-by:
-
- Feb 28, 2017
-
-
Andy Polyakov authored
Reviewed-by:
-
Richard Levitte authored
Base address setting was done for the sake of FIPS. Since FIPS references have been removed, we clean away this one as well. Reviewed-by:
-
Bernd Edlinger authored
Reviewed-by:
-
Benjamin Kaduk authored
AGL has a history of pointing out the idiosynchronies/laxness of the openssl PEM parser in amusing ways. If we want this functionality to stay present, we should test that it works. Reviewed-by:
-
Benjamin Kaduk authored
Generate a fresh certificate and DSA private key in their respective PEM files. Modify the resulting ASCII in various ways so as to produce input files that might be generated by non-openssl programs (openssl always generates "standard" PEM files, with base64 data in 64-character lines except for a possible shorter last line). Exercise various combinations of line lengths, leading/trailing whitespace, non-base64 characters, comments, and padding, for both unencrypted and encrypted files. (We do not have any other test coverage that uses encrypted files, as far as I can see, and the parser enforces different rules for the body of encrypted files.) Add a recipe to parse these test files and verify that they contain the expected string or are rejected, according to the expected status. Some of the current behavior is perhaps suboptimal and could be revisited. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Rich Salz authored
Reviewed-by:
-
Emilia Kasper authored
Reviewed-by:
-
Emilia Kasper authored
This is a bogus, undocumented format that was intended for testing; I don't think anyone is using it. Reviewed-by: -
Rich Salz authored
Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Matt Caswell authored
Reviewed-by:
-
Dr. Stephen Henson authored
Reviewed-by:
-
