summaryrefslogtreecommitdiff
path: root/lib/libssl
AgeCommit message (Collapse)Author
2016-05-03patch from openssl for multiple issues:Ted Unangst
missing padding check in aesni functions overflow in evp encode functions use of invalid negative asn.1 types ok beck
2016-04-28Crank majors for lib{crypto,ssl,tls} due to symbol removals, symbolJoel Sing
additions and functionality changes.
2016-04-28don't go into an unbreakable infinite loop during operations suchTed Unangst
as reading passwords. allow ^C to break. the pain was mine, the fix is miod's.
2016-04-28Implement the IETF ChaCha20-Poly1305 cipher suites.Joel Sing
Rename the existing ChaCha20-Poly1305 cipher suites with an "-OLD" suffix, effectively replaces the original Google implementation. We continue to support both the IETF and Google versions, however the existing names now refer to the ciphers from draft-ietf-tls-chacha20-poly1305-04. Feedback from doug@
2016-04-28Rename EVP_aead_chacha20_poly1305() to EVP_aead_chacha20_poly1305_old()Joel Sing
and replace with EVP_aead_chacha20_poly1305_ietf(). The IETF version will become the standard version. Discussed with many.
2016-04-13Use the correct iv and counter when decrypting the ciphertext forJoel Sing
EVP_aead_chacha20_poly1305_ietf().
2016-03-30for some time now mandoc has not required MLINKS to functionJason McIntyre
correctly - logically complete that now by removing MLINKS from base; authors need only to ensure there is an entry in NAME for any function/ util being added. MLINKS will still work, and remain for perl to ease upgrades; ok nicm (curses) bcook (ssl) ok schwarze, who provided a lot of feedback and assistance ok tb natano jung
2016-03-27Merge a memleak fix from BoringSSL 6b6e0b2:Michael McConville
https://boringssl.googlesource.com/boringssl/+/6b6e0b20893e2be0e68af605a60ffa2cbb0ffa64%5E!/#F0 ok millert@, beck@
2016-03-21Return zero from two functions on allocation failure instead of alwaysmmcc
returning one (indicating success). Each function has only a single usage, and both usages check the return value. Merged from BoringSSL 0ce78a757d815c0dde9ed5884229f3a5b2cb3e9c: https://boringssl.googlesource.com/boringssl/+/0ce78a757d815c0dde9ed5884229f3a5b2cb3e9c%5E!/#F0 ok beck@
2016-03-20" the the " -> " the ", or in a couple of cases replace the superfluousKenneth R Westerback
"the" with the obviously intended word. Started with a "the the" spotted by Mihal Mazurek.
2016-03-17explicit_bzero for asn1 objects on free. Too often these contain sensitive ↵Bob Beck
information and they should not be a performance bottleneck ok miod@ krw@
2016-03-15'accomodate' -> 'accommodate' in comments.Kenneth R Westerback
Started by diff from Mical Mazurek.
2016-03-13Fix examples for EVP_PKEY_CTX_set_rsa_padding.Brent Cook
Noted here, https://github.com/libressl-portable/portable/issues/161, we document a non-existent constant in the examples for EVP_PKEY_CTX_set_rsa_padding. ok deraadt@
2016-03-12Add error handling to the remaining calls to bn_wexpand().Brent Cook
Noticed by pascal-cuoq from Github: https://github.com/libressl-portable/openbsd/issues/56 ok beck@
2016-03-12Remove sentences in RETURN VALUES sections saying that functions withmmcc
void return types 'return no value'. This is obvious and therefore unneccessary to mention. We spare rewind(3)'s sentence because espie@ pointed out that it's a warning - the function masks a potential error. This commit also adds a sentence to X509_free clarifying that it's NULL-safe. This bit was discussed with doug@. ok martijn@, sentiment supported by schwarze@
2016-03-12Bump for LibreSSL 2.4.0Brent Cook
2003-05-11import 0.9.7b (without idea and rc5)Markus Friedl
2016-03-11X509_free(3) is NULL-safe, so remove NULL checks before its calls.mmcc
ok doug@
2016-03-10http -> https for a few more IETF URLs in comments or man pagesmmcc
2016-03-07http -> https for IETF/IANA URLs in commentsmmcc
2016-03-06explict_bzero for some asn1 free's - ok miod@Bob Beck
2016-03-06Make sure stdio functions don't end up in the library, from miod@Bob Beck
ok doug@ bcook@
2016-03-04graduate bn_expand() to a real function. the openssl version of thisTheo de Raadt
uses a macro with multiple-evaluations of arguments (different amount than the previous version..), but doug/bcook's inline version makes BIGNUM not opaque [problem spotted by naddy] ok doug
2016-03-04Revert bn_expand until there's consensus on a fix.Doug Hogan
2016-03-02fix the rest of the read_ledword() calls used as lengths to be bounded.Bob Beck
inspired by guido vranken https://guidovranken.wordpress.com/2016/03/01/public-disclosure-malformed-private-keys-lead-to-heap-corruption-in-b2i_pvk_bio/ ok doug@
2016-03-02Add bounds checking for BN_hex2bn/BN_dec2bn.Doug Hogan
Need to make sure i * 4 won't overflow. Based on OpenSSL: commit 99ba9fd02fd481eb971023a3a0a251a37eb87e4c input + ok bcook@ ok beck@
2016-03-02bound lengths coming out of a pem file to something like realityBob Beck
ok deraadt@
2016-03-01Remove support for ancient, broken DSA implementations.Doug Hogan
Based on a few OpenSSL commits: Remove ancient DSA workarounds commit ab4a81f69ec88d06c9d8de15326b9296d7f498ed Remove workaround for broken DSA implementations using negative integers commit dfb10af92e9663ce4eefaa1d6b678817fa85344d Typo in error name (EVP_R_DECODE_ERROR -> DSA_R_DECODE_ERROR) commit f6fb7f1856d443185c23f1a5968c08b4269dd37d ok beck@
2016-02-29remove NULL checks for pqueue_free()mmcc
ok doug@
2016-01-29Therefor -> Therefore (where appropriate)tb
from ray@, ok jmc@
2016-01-27deprecate SSL_OP_SINGLE_DH_USEBob Beck
ok jsing@
2015-12-30Document that the ssl free() functions are NULL safe. OK mmcc@Todd C. Miller
2015-12-24More adress -> addressmmcc
2008-09-06import of OpenSSL 0.9.8hDamien Miller
2015-12-23remove NULL-checks before free()mmcc
2015-12-23assign pointer NULL rather than 0mmcc
2015-12-23assign pointer to NULL rather than 0mmcc
2015-12-22initialize a pointer to NULL rather than 0mmcc
2015-12-14initialize ext_len to 0.Bob Beck
ok guenther@
2015-12-14initialize ok to 0Bob Beck
ok guenther@
2015-12-14initialize md_len to 0 for readability to quell warnings.Bob Beck
ok guenther@
2015-12-12decipher comment. ok bcook@mmcc
2015-12-12move initialization of buf up to quell warnings and make it obvious the err ↵Bob Beck
case is ok. ok bcook@
2015-12-12prevent possibly use of uninitialized variableBob Beck
ok bcook@
2015-12-12make the counter a size_t as well, which quells a warning on visual studio 2015Bob Beck
ok bcook@
2015-12-09bump the major for libcrypto/ssl/tls for a CRYPTO_chacha_20 ABI changeBrent Cook
ok jsing@, deraadt@, beck@
2015-12-09Change the counter argument for CRYPTO_chacha_20 to be 64-bits on all platforms.Brent Cook
The recently-added EVP_aead_chacha20_poly1305_ietf() function, which implements informational RFC 7539, "ChaCha20 and Poly1305 for IETF Protocols", needs a 64-bit counter to avoid truncation on 32-bit platforms. The existing TLS ChaCha20-Poly1305 ciphersuite is not impacted by this, but making this change requires an ABI bump. ok jsing@, "Looks sane" beck@
2015-12-07Remove SHA0 check, as we did in v1.21 of sha.h.Brent Cook
This enables ENGINE_get_digest to work again with SHA1. noted by NARUSE, Yui, @nurse from github
2015-12-04Fix for OpenSSL CVE-2015-3195Bob Beck
ok djm@ jsing@
2015-12-03Fix for OpenSSL CVE-2015-3194Bob Beck
ok krw@
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 11:34:11 +0000