summaryrefslogtreecommitdiff
path: root/src/lib/libssl/ssl_ciph.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* The ssl_ciper_get_evp() function is currently overloaded to also return thejsing2014-05-251-22/+32
| | | | | | | | | | | compression associated with the SSL session. Based on one of Adam Langley's chromium diffs, factor out the compression handling code into a separate ssl_cipher_get_comp() function. Rewrite the compression handling code to avoid pointless duplication and so that failures are actually returned to and detectable by the caller. ok miod@
* In ssl_cipher_get_evp(), fix off-by-one in index validation before accessingmiod2014-05-241-2/+2
| | | | | | arrays. "kind of scary" deraadt@, ok guenther@
* KSSL is dead... nuke KSSL_DEBUG from orbit.jsing2014-05-201-14/+0
| | | | ok beck@ miod@
* Remove SRP and Kerberos support from libssl. These are complex protocolstedu2014-05-051-4/+0
| | | | | all on their own and we can't effectively maintain them without using them, which we don't. If the need arises, the code can be resurrected.
* switch to reallocarraytedu2014-04-221-2/+2
|
* use mallocarray(a,b) instead of malloc(a*b)deraadt2014-04-211-2/+2
|
* more malloc/realloc/calloc cleanups; ok beck kettenisderaadt2014-04-211-2/+2
|
* Use calloc(a,b) instead of malloc(a*b) + memset(a*b). I don't know ifderaadt2014-04-201-2/+1
| | | | | | | | | | | | | | | | | | | | | | this instance is integer-overflowable, but we cannot keep hand-auditing every instance (or apathetically ignoring these issues) when the simple calloc idiom is better in the presence of a good calloc(). It is simply unfeasible to always enter correct range checks before the aggregate size calculation, just go find some 4000 lines of code, REPAIR THEM ALL, then come back and tell me I am wrong. This only works on systems where calloc() does the integer overflow check, but if your system doesn't do this, you need to ask your vendor WHY THEY ARE 10 YEARS BEHIND IN BEST PRACTICE? This is the kind of problem that needs to be solved at the right layer. malloc integer-overflow was implicated in the 2002 OpenSSH hole. OpenSSH and much other code is now written to use calloc(), for instance OpenSSH has 103 calls to it. We feel safer with our use of calloc(). It is a natural approach for us to use calloc(). How safe do you feel on systems which lack that range check in their calloc()? Good writeup from 2006: http://undeadly.org/cgi?action=article&sid=20060330071917
* More KNF and style consistency tweaksguenther2014-04-191-18/+18
|
* always build in RSA and DSA. ok deraadt miodtedu2014-04-171-7/+0
|
* Change library to use intrinsic memory allocation functions instead ofbeck2014-04-171-17/+17
| | | | | | | | OPENSSL_foo wrappers. This changes: OPENSSL_malloc->malloc OPENSSL_free->free OPENSSL_relloc->realloc OPENSSL_freeFunc->free
* add back SRP. i was being too greedy.tedu2014-04-161-0/+2
|
* disentangle SRP code from TLStedu2014-04-161-2/+0
|
* repair some whitespacetedu2014-04-151-50/+44
|
* remove FIPS mode support. people who require FIPS can buy something thattedu2014-04-151-14/+1
| | | | | meets their needs, but dumping it in here only penalizes the rest of us. ok miod
* Send the rotIBM stream cipher (ebcdic) to Valhalla to party for eternitybeck2014-04-151-4/+0
| | | | | with the bearded ones... some API's that nobody should be using will dissapear with this commit.
* Flense all use of BIO_snprintf from ssl source - use the real one instead,beck2014-04-141-4/+7
| | | | | | and allow for the normal posix mandated return values instead of the nonstandard one from BIO_snprintf. ok miod@
* First pass at applying KNF to the OpenSSL code, which almost makes itjsing2014-04-141-713/+680
| | | | | readable. This pass is whitespace only and can readily be verified using tr and md5.
* Merge conflicts; remove MacOS, Netware, OS/2, VMS and Windows build machinery.miod2014-04-131-2/+3
|
* resolve conflictsdjm2012-10-131-14/+119
|
* OpenSSL 1.0.0f: mergedjm2012-01-051-0/+1
|
* openssl-1.0.0e: resolve conflictsdjm2011-11-031-4/+2
|
* resolve conflicts, fix local changesdjm2010-10-011-331/+692
|
* resolve conflictsdjm2009-04-061-1/+1
|
* resolve conflictsdjm2009-01-091-0/+3
|
* update to openssl-0.9.8i; tested by several, especially krw@djm2009-01-051-0/+10
|
* resolve conflictsdjm2008-09-061-72/+307
|
* resolve conflictsdjm2006-06-271-41/+23
|
* resolve conflictsdjm2005-04-291-5/+16
|
* merge 0.9.7dmarkus2004-04-081-39/+40
|
* Correct some off-by-ones. They currently don't matter, but thiscloder2003-10-011-3/+3
| | | | | is for future safety and consistency. OK krw@, markus@
* merge 0.9.7b with local changes; crank majors for libssl/libcryptomarkus2003-05-121-4/+10
|
* merge openssl-0.9.7-beta3, tested on vax by miod@markus2002-09-101-7/+8
|
* do not propose IDEA cipher on SSL connection. tested by beckitojun2002-06-071-0/+6
| | | | noticed by Sverre Froyen <sverre@viewmark.com>
* OpenSSL 0.9.7 stable 2002 05 08 mergebeck2002-05-151-8/+69
|
* openssl-engine-0.9.6 mergebeck2000-12-151-15/+17
|
* OpenSSL 0.9.5a mergebeck2000-04-151-38/+39
|
* OpenSSL 0.9.5 mergebeck2000-03-191-296/+529
| | | | | | *warning* this bumps shared lib minors for libssl and libcrypto from 2.1 to 2.2 if you are using the ssl26 packages for ssh and other things to work you will need to get new ones (see ~beck/libsslsnap/<arch>) on cvs or ~beck/src-patent.tar.gz on cvs
* OpenSSL 0.9.4 mergebeck1999-09-291-58/+135
|
* Import of SSLeay-0.9.0b with RSA and IDEA stubbed + OpenBSD buildryker1998-10-051-0/+758
functionality for shared libs. Note that routines such as sslv2_init and friends that use RSA will not work due to lack of RSA in this library. Needs documentation and help from ports for easy upgrade to full functionality where legally possible.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-30 14:15:54 +0000