summaryrefslogtreecommitdiff
path: root/extra/yassl/include/openssl
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.1 into 10.2bb-10.2-mergeMarko Mäkelä2020-07-011-1/+1
|\
| * mtr: use env for perlDaniel Black2020-06-231-1/+1
| | | | | | | | | | | | | | | | On FreeBSD, perl isn't in /usr/bin, its in /usr/local/bin or elsewhere in the path. Like storage/{maria/unittest/,}ma_test_* , we use /usr/bin/env to find perl and run it.
| * imporve clang buildEugene Kosov2019-06-251-1/+1
| | | | | | | | | | | | | | | | | | cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_BUILD_TYPE=Debug Maintainer mode makes all warnings errors. This patch fix warnings. Mostly about deprecated `register` keyword. Too much warnings came from Mroonga and I gave up on it.
* | Merge 10.1 into 10.2Marko Mäkelä2019-05-1324-24/+24
|\ \ | |/
| * Merge branch '5.5' into 10.1Vicențiu Ciorbaru2019-05-1124-24/+24
| |\
| | * Update FSF AddressVicențiu Ciorbaru2019-05-1123-23/+23
| | | | | | | | | | | | * Update wrong zip-code
* | | Merge branch '10.1' into 10.2Sergei Golubchik2017-10-241-2/+3
|\ \ \ | |/ /
| * | Merge branch '5.5' into 10.0Sergei Golubchik2017-10-181-2/+3
| |\ \ | | |/
| | * Bug#26482173: TLS CIPHER NEGOTIATION INCORRECTLY MATCHES ONArun Kuruvila2017-08-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LAST BYTE ONLY (YASSL) Description:- TLS cipher negociation happens incorrectly leading to the use of a different Analysis:- YaSSL based MySQL server will compare only the last byte of each cipher sent in the Client Hello message. This can cause TLS connections to fail, due to the server picking a cipher which the client doesn't actually support. Fix:- A fix for detecting cipher suites with non leading zeros is included as YaSSL only supports cipher suites with leading zeros.
| | * Bug #24740291: YASSL UPDATE TO 2.4.2Robert Golebiowski2016-09-271-1/+1
| | |
* | | MDEV-12763 10.2 uses deprecated openssl 1.0 apis even with 1.1Sergei Golubchik2017-09-181-1/+1
| | | | | | | | | | | | | | | Use OpenSSL 1.1 when applicable. Create compatibility macros for OpenSSL 1.0- and YaSSL.
* | | Merge branch '10.1' into 10.2Sergei Golubchik2016-12-291-1/+1
|\ \ \ | |/ /
| * | Merge branch '5.5' into 10.0Sergei Golubchik2016-10-251-1/+1
| |\ \
| | * | Bug #24740291: YASSL UPDATE TO 2.4.2mysql-5.5.53Robert Golebiowski2016-09-281-1/+1
| | |/
* | | fix build and some warningskevg2016-11-241-1/+1
|/ /
* | Merge branch '5.5' into 10.0Sergei Golubchik2016-04-261-1/+1
|\ \ | |/
| * Bug #22738607: YASSL FUNCTION X509_NAME_GET_INDEX_BY_NID IS NOT WORKING AS ↵mysql-5.5.49Yashwant Sahu2016-02-261-1/+1
| | | | | | | | EXPECTED.
* | Merge branch '5.5' into 10.0Sergei Golubchik2016-02-151-1/+1
|\ \ | |/
| * Description: yaSSL was only handling the cases of zero orV S Murthy Sidagam2016-01-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | one leading zeros for the key agreement instead of potentially any number. There is about 1 in 50,000 connections to fail when using DHE cipher suites. The second problem was the case where a server would send a public value shorter than the prime value, causing about 1 in 128 client connections to fail, and also caused the yaSSL client to read off the end of memory. All client side DHE cipher suite users should update. Note: The patch is received from YaSSL people
| * Updated yassl to yassl-2.3.8Robert Golebiowski2015-09-181-1/+1
| |
| * Bug #21025377 CAN'T CONNECT TO SSL ENABLED SERVER FIRST 30 SEC AFTERRobert Golebiowski2015-09-181-1/+1
| | | | | | | | | | | | INITIAL STARTUP Updated yassl to yassl-2.3.7e
* | Merge branch '5.5' into 10.0Sergei Golubchik2015-10-091-1/+1
|\ \
| * | Updated yassl to yassl-2.3.8mysql-5.5.46Robert Golebiowski2015-09-181-1/+1
| | | | | | | | | | | | (cherry picked from commit 7f9941eab55ed672bfcccd382dafbdbcfdc75aaa)
| * | Bug #21025377 CAN'T CONNECT TO SSL ENABLED SERVER FIRST 30 SEC AFTERRobert Golebiowski2015-09-181-1/+1
| |/ | | | | | | | | | | | | | | INITIAL STARTUP Updated yassl to yassl-2.3.7e (cherry picked from commit 6e21c8c04b922bdb60b6a7c174709d2e1bdd3618)
| * Bug #20774956: THREAD_POOL.THREAD_POOL_CONNECT HANGS WHEN RUN ON ARobert Golebiowski2015-07-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | YASSL-COMPILED SERVER/CLIENT Description: thread_pool.thread_pool_connect hangs when the server and client are compiled with yaSSL. Bug-fix: Test thread_pool.thread_pool_connect was temporary disabled for yaSSL. However, now that yaSSL is fixed it runs OK. The bug was introduced by one of the yaSSL updates. set_current was not working for i == 0. Now this is fixed. YASSL is updated to 2.3.7d
| * Bug #21025377 CAN'T CONNECT TO SSL ENABLED SERVER FIRST 30 SEC AFTERRobert Golebiowski2015-07-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | INITIAL STARTUP Description: By using mysql_ssl_rsa_setup to get SSL enabled server (after running mysqld --initialize) server don't answer properly to "mysqladmin ping" first 30 secs after startup. Bug-fix: YASSL validated certificate date to the minute but should have to the second. This is why the ssl on the server side was not up right away after new certs were created with mysql_ssl_rsa_setup. The fix for that was submitted by Todd. YASSL was updated to 2.3.7c.
| * Bug #20168526 YASSL: CORRUPT SSL-KEY CRASHES CLIENTRobert Golebiowski2015-07-081-1/+1
| | | | | | | | | | | | | | | | | | | | Affects at least 5.6 and 5.7. In customer case, the "client" happened to be a replication slave, therefore his server crashed. Bug-fix: The bug was in yassl. Todd Ouska has provided us with the patch. (cherry picked from commit 42ffa91aad898b02f0793b669ffd04f5c178ce39)
* | Merge branch '5.5' into 10.0Sergei Golubchik2015-02-181-1/+1
|\ \ | |/
| * Bug#20201864 : UPGRADE TO YASSL 2.3.7Harin Vadodaria2014-12-301-1/+1
| | | | | | | | | | | | | | Upgrading YaSSL from 2.3.5 to 2.3.7 Reviewed-by : Kristofer Pettersson <kristofer.pettersson@oracle.com> Reviewed-by : Vamsikrishna Bhagi <vamsikrishna.bhagi@oracle.com>
| * Bug#19695101 UPGRADE YASSL TO 2.3.5Kristofer Pettersson2014-09-291-1/+1
| |
| * Bug#19370676 : YASSL PRE-AUTH BUFFER OVERFLOW WHEN CLIENTHarin Vadodaria2014-08-231-1/+1
| | | | | | | | | | | | | | | | LIES ABOUT SUITE_LEN_ and Bug#19355577 : YASSL PRE-AUTH BUFFER OVERFLOW WHEN CLIENT LIES ABOUT COMP_LEN_ Description : Updating yaSSL to version 2.3.4.
| * Updated/added copyright header. Added line "use is subject to license terms" Murthy Narkedimilli2014-02-1721-0/+21
| | | | | | | | to copyright header.
| * Bug#14211271 ISSUES WITH SSL ON DEBIAN WHEEZY I386 AND KFREEBSD-I386Anirudh Mangipudi2014-02-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: It was reported that on Debian and KFreeBSD platforms, i386 architecture machines certain SSL tests are failing. main.ssl_connect rpl.rpl_heartbeat_ssl rpl.rpl_ssl1 rpl.rpl_ssl main.ssl_cipher, main.func_encrypt were the tests that were reportedly failing (crashing). The reason for the crashes are said to be due to the assembly code of yaSSL. Solution: There was initially a workaround suggested i.e., to enable -DTAOCRYPT_DISABLE_X86ASM flag which would prevent the crash, but at an expense of 4X reduction of speed. Since this was unacceptable, the fix was the functions using assembly, now input variables from the function call using extended inline assembly on GCC instead of relying on direct assembly code.
| * Bug#16715064 MYSQL COMMUNITY UTILITIES CANNOT CONNECT TO MYSQL ENTERPRISEAnirudh Mangipudi2014-01-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WITH SSL ENABLED Problem: It was reported that MySQL community utilities cannot connect to a MySQL Enterprise 5.6.x server with SSL configured. We can reproduce the issue when we try to connect an MySQL Enterprise Server with a MySQL Client with --ssl-ca parameter enabled. We get an ERROR 2026 (HY000): SSL connection error: unknown error number. Solution: The root cause of the problem was determined to be the difference in handling of the certificates by OpenSSL(Enterprise) and yaSSL(Community). OpenSSL expects a blank certificate to be sent when a parameter (ssl-ca, or ssl-cert or ssl-key) has not been specified.On the other hand yaSSL doesn't send any certificate and since OpenSSL does not expect this behaviour it returns an Unknown SSL error. The issue was resolved by yaSSL adding capability to send blank certificate when any of the parameter is missing.
| * Correcting the permissions of the executable files.Murthy Narkedimilli2013-03-201-0/+0
| |
| * Fix for Bug 16395495 - OLD FSF ADDRESS IN GPL HEADERMurthy Narkedimilli2013-03-191-1/+1
| |
| * Updated/added copyright headers.Murthy Narkedimilli2013-02-251-2/+1
| |
| * Bug#15883127: PORT FIX FOR BUG #13904906 TO MYSQL 5.1Harin Vadodaria2012-11-211-1/+1
| | | | | | Description: Updated yassl to version 2.2.2
| * Further upgrade the yaSSL library to version 2.2.0Joerg Bruehe2012-03-021-2/+2
| | | | | | | | | | | | to pick up some new security fixes that are in it. Patch provided by Georgi Kodinov.
| * Bug #13706828: UPGRADE YASSL FROM 1.7.2 TO 2.1.4Georgi Kodinov2012-02-101-25/+24
| | | | | | | | | | | | | | $SUBJ$ 1. Took a diff between the previous base version and the mysql sources. 2. Added the new 2.1.4 base version. 3. Reviewed and re-applied the diff from step #1.
| * Bug#13706621 : UNIFY THE YASSL VERSIONS THAT WE USE BY BACKPORTING 5.1 Georgi Kodinov2012-02-102-5/+11
| | | | | | | | | | | | | | AND 5.5 YASSL FIXES. Took the 5.5 yassl code and applied it to the 5.0 codebase, keeping the compilation files.
| * - Added/updated copyright headersKent Boortz2010-12-2822-0/+394
| | | | | | | | | | | | | | | | | | | | | | - Removed files specific to compiling on OS/2 - Removed files specific to SCO Unix packaging - Removed "libmysqld/copyright", text is included in documentation - Removed LaTeX headers for NDB Doxygen documentation - Removed obsolete NDB files - Removed "mkisofs" binaries - Removed the "cvs2cl.pl" script - Changed a few GPL texts to use "program" instead of "library"
| * Import yaSSL version 1.7.2msvensson@pilot.(none)2007-08-288-1/+20
| | | | | | | | | | - Fix bug#27265 - Support for fixing bug#18441
| * Bug #29579 Clients using SSL can hang the serverdkatz@damien-katzs-computer.local2007-07-121-0/+2
| | | | | | | | Added an option to yassl to allow "quiet shutdown" like openssl does. This option causes the SSL libs to NOT perform the close_notify handshake during shutdown. This fixes a hang we experience because we hold a lock during socket shutdown.
| * Set yaSSL to use same type as MySQL do for socket handlesmsvensson@pilot.blaudden2007-03-281-2/+8
| |
| * Import yassl 1.6.0msvensson@pilot.blaudden2007-03-231-7/+3
| |
| * Fixed compiler warnings (for linux and win32 and win64)monty@mysql.com/narttu.mysql.fi2007-02-221-2/+6
| | | | | | | | Fixed a couple of usage of not initialized warnings (unlikely cases)
| * Import latest version of yaSSLmsvensson@neptunus.(none)2007-01-291-24/+17
| | | | | | | | | | | | | | - Replace SawTooth copyright header with MySQL's - Bug#19209 Test 'rpl_openssl' hangs on Windows - Spurious "2013 Connection to server lost" errors fixed yaSSL doesn't close socket anymore, that is left to the application
| * Import yaSSL version 1.5.8msvensson@neptunus.(none)2007-01-221-1/+1
| | | | | | | | - Includes patch for Bug#25189
| * Import version 1.50 of yaSSLmsvensson@shellback.(none)2006-11-292-1/+12
| |
View Lorry Controller Status