summaryrefslogtreecommitdiff
path: root/extra/yassl/src
Commit message (Collapse)AuthorAgeFilesLines
* Fixed compiler warningsMichael Widenius2014-12-191-3/+3
| | | | | scripts/mysql_system_tables.sql: Removed DEFAULT from a blob definition as this can cause problems.
* 5.5 mergeSergei Golubchik2014-11-201-1/+1
|\
| * Fix YaSSL on windowsSergei Golubchik2014-11-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This came with the upgrade from yassl 2.3.0 to 2.3.4 - ssl tests started to hang on Windows. Comparing and removing changes I've got to this: void input_buffer::set_current(uint i) { - if (i) - check(i - 1, size_); - current_ = i; + if (error_ == 0 && i && check(i - 1, size_) == 0) + current_ = i; + else + error_ = -1; } in 2.3.0 i==0 was only used to avoid the check, in 2.3.4 it's an error. but there are places in the code that do set_current(0) and others that do, like, { before=get_current(); ...; set_current(before); } - and the initial value of current_ is 0. So, I suspect that set_current(0) should not be an error, but it should only skip the check().
* | 5.5.40+ mergeSergei Golubchik2014-10-094-55/+269
|\ \ | |/
| * mysql-5.5.40Sergei Golubchik2014-10-064-55/+269
| |\
| | * Bug#19370676 : YASSL PRE-AUTH BUFFER OVERFLOW WHEN CLIENTHarin Vadodaria2014-08-234-55/+269
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | 5.5.39 mergeSergei Golubchik2014-08-071-2/+5
|\ \ \ | |/ /
| * | mysql-5.5.39 mergeSergei Golubchik2014-08-021-2/+5
| |\ \ | | |/ | | | | | | | | | | | | | | | ~40% bugfixed(*) applied ~40$ bugfixed reverted (incorrect or we're not buggy) ~20% bugfixed applied, despite us being not buggy (*) only changes in the server code, e.g. not cmakefiles
| | * Bug#17201924 and Bug#18178997 : YASSL:MISSING CLOSEDIR()Harin Vadodaria2014-05-221-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IN SSL_CTX_LOAD_VERIFY_ LOCATIONS() and OFF-BY-ONE PROBLEM IN VOID CERTDECODER:: GETDATE(DATETYPE DT) IN ASN.CPP Description : Fixes corner cases in yassl code. Refer to bug page for details.
* | | 5.5 mergeSergei Golubchik2014-05-096-18/+47
|\ \ \ | |/ /
| * | mysql-5.5.37 selective mergeSergei Golubchik2014-03-276-18/+47
| |\ \ | | |/
| | * Updated/added copyright header. Added line "use is subject to license terms" Murthy Narkedimilli2014-02-172-0/+2
| | | | | | | | | | | | | | | to copyright header.
| | * Bug#14211271 ISSUES WITH SSL ON DEBIAN WHEEZY I386 AND KFREEBSD-I386Anirudh Mangipudi2014-02-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-083-13/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | 10.0-base mergeSergei Golubchik2014-02-263-3/+3
|\ \ \
| * \ \ 5.5 mergeSergei Golubchik2014-02-253-3/+3
| |\ \ \ | | |/ /
| | * | MySQL-5.5.36 mergeSergei Golubchik2014-02-173-3/+3
| | |\ \ | | | |/ | | | | | | | | (without few incorrect bugfixes and with 1250 files where only a copyright year was changed)
| | | * Updated/added copyright headersMurthy Narkedimilli2014-01-063-3/+3
| | | |
* | | | 10.0-base mergeSergei Golubchik2013-07-181-1/+1
|\ \ \ \ | |/ / /
| * | | 5.5 mergeSergei Golubchik2013-07-171-1/+1
| |\ \ \ | | |/ /
| | * | mysql-5.5.32 mergeSergei Golubchik2013-07-161-1/+1
| | |\ \ | | | |/
| | | * 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
| | | |
* | | | 10.0-base mergeSergei Golubchik2013-06-0611-35/+218
|\ \ \ \ | |/ / / | | | | | | | | (without InnoDB - all InnoDB changes were ignored)
| * | | 5.5 mergeSergei Golubchik2013-06-0611-37/+218
| |\ \ \ | | |/ /
| | * | mysql-5.5.31 mergeSergei Golubchik2013-05-0712-38/+220
| | |\ \ | | | |/
| | | * Updated/added copyright headersMurthy Narkedimilli2013-02-2611-15/+12
| | | |\
| | | | * Updated/added copyright headers.Murthy Narkedimilli2013-02-2511-15/+11
| | | | |
| | | * | Bug#16218104: MYSQL YASSL - LUCKY THIRTEEN: BREAKING THEHarin Vadodaria2013-02-153-23/+208
| | | |\ \ | | | | |/ | | | | | | | | | | | | | | | | | | | | TLS AND DTLS RECORD PROTOCOLS Description: Merge from 5.1.
| | | | * Bug#16218104: MYSQL YASSL - LUCKY THIRTEEN: BREAKING THEHarin Vadodaria2013-02-153-23/+208
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TLS AND DTLS RECORD PROTOCOLS Description: In yassl, decryption phase in TLS protocol depends on type of padding. This patch removes this dependancy and makes error generation/decryption process independent of padding type.
* | | | | 10.0-base mergeSergei Golubchik2013-04-151-1/+7
|\ \ \ \ \ | |/ / / /
| * | | | 5.5 mergeSergei Golubchik2013-03-271-1/+7
| |\ \ \ \ | | |/ / /
| | * | | merge with mysql-5.5.30 minus few incorrect or not applicable changesetsSergei Golubchik2013-02-281-1/+7
| | |\ \ \ | | | |/ /
| | | * | Bug#15965288: BUFFER OVERFLOW IN YASSL FUNCTIONHarin Vadodaria2012-12-131-1/+7
| | | |\ \ | | | | |/ | | | | | | | | | | | | | | | | | | | | DOPROCESSREPLY() Description: Merge from 5.1 to 5.5
| | | | * Bug#15965288: BUFFER OVERFLOW IN YASSL FUNCTIONHarin Vadodaria2012-12-131-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DOPROCESSREPLY() Description: Function DoProcessReply() calls function decrypt_message() in a while loop without performing a check on available buffer space. This can cause buffer overflow and crash the server. This patch is fix provided by Sawtooth to resolve the issue.
| | | | * Bug#15883127: PORT FIX FOR BUG #13904906 TO MYSQL 5.1Harin Vadodaria2012-11-214-12/+5
| | | | | | | | | | | | | | | | | | | | Description: Updated yassl to version 2.2.2
* | | | | Merge MariaDB 10.0-base to MariaDB 10.0unknown2012-12-183-141/+0
|\ \ \ \ \ | |/ / / /
| * | | | remove HAVE_EXPLICIT_TEMPLATE_INSTANTIATIONSergei Golubchik2012-12-173-141/+0
| |/ / /
* | | | merge with 5.5Sergei Golubchik2012-11-034-13/+6
|\ \ \ \ | |/ / /
| * | | mysql-5.5.28Sergei Golubchik2012-10-164-13/+6
| |\ \ \ | | |/ /
| | * | Bug #13115401: -SSL-KEY VALUE IS NOT VALIDATED AND IT ALLOWS INSECURE Venkata Sidagam2012-08-111-1/+1
| | |\ \ | | | |/ | | | | | | | | | | | | | | | | CONNECTIONS IF SPE Merged from mysql-5.1 to mysql-5.5
| | | * Bug #13115401: -SSL-KEY VALUE IS NOT VALIDATED AND IT ALLOWS INSECURE Venkata Sidagam2012-08-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | CONNECTIONS IF SPE Problem description: -ssl-key value is not validated, you can assign any bogus text to --ssl-key and it is not verified that it exists, and more importantly, it allows the client to connect to mysqld. Fix: Added proper validations checks for --ssl-key. Note: 1) Documentation changes require for 5.1, 5.5, 5.6 and trunk in the sections listed below and the details are : http://dev.mysql.com/doc/refman/5.6/en/ssl-options.html#option_general_ssl and REQUIRE SSL section of http://dev.mysql.com/doc/refman/5.6/en/grant.html 2) Client having with option '--ssl', should able to get ssl connection. This will be implemented as part of separate fix in 5.6 and trunk.
| | * | Bug#13904906: YASSL PRE-AUTH CRASH WITH 5.1.62, 5.5.22Harin Vadodaria2012-07-244-12/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Valgrind reports errors when an invalid certificate is used on the client. Solution: Updated yaSSL to version 2.2.2.
* | | | Fixing test casesMichael Widenius2012-08-232-3/+17
| | | | | | | | | | | | | | | | Added missing system tables used in 5.6
* | | | Next part of merge. See TODO for detailsMichael Widenius2012-08-145-44/+136
|/ / /
* | | mergeSergei Golubchik2012-04-071-1/+4
|\ \ \
| * \ \ mysql-5.1.62 mergeSergei Golubchik2012-04-0511-141/+248
| |\ \ \ | | | |/ | | |/|
* | | | mysql-5.5.22 mergeSergei Golubchik2012-03-2811-126/+222
|\ \ \ \ | | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mysql-test/suite/innodb/t/group_commit_crash.test: remove autoincrement to avoid rbr being used for insert ... select mysql-test/suite/innodb/t/group_commit_crash_no_optimize_thread.test: remove autoincrement to avoid rbr being used for insert ... select mysys/my_addr_resolve.c: a pointer to a buffer is returned to the caller -> the buffer cannot be on the stack mysys/stacktrace.c: my_vsnprintf() is ok here, in 5.5
| * | | Further upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.1 to 5.5.Joerg Bruehe2012-03-022-3/+22
| |\ \ \ | | | |/ | | |/| | | | | | | | | Also, take a syntax fix (C++ style comment in C file) in client/mysqldump.c.
| | * | Further upgrade the yaSSL library to version 2.2.0Joerg Bruehe2012-03-022-3/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | to pick up some new security fixes that are in it. Patch provided by Georgi Kodinov.
View Lorry Controller Status