8713e488fb
Most notably this version includes fixes for: http://secunia.com/advisories/21259/ http://secunia.com/advisories/21506/ http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3469 * Packages changes: the script mysqldumpslow had been moved from the mysql4-client to the mysql4-server. * Changes since last packaged version (4.1.20) (see http://dev.mysql.com/doc/refman/4.1/en/news-4-1-21.html for more details): This is a bugfix release for the recent production release family. Functionality added or changed: - For spatial data types, the server formerly returned these as VARSTRING values with a binary collation. Now the server returns spatial values as BLOB values. (Bug#10166) - Added the --set-charset option to mysqlbinlog to allow the character set to be specified for processing binary log files. (Bug#18351) - For a table with an AUTO_INCREMENT column, SHOW CREATE TABLE now shows the next AUTO_INCREMENT value to be generated. (Bug#19025) - A warning now is issued if the client attempts to set the SQL_LOG_OFF variable without the SUPER privilege. (Bug#16180) - The mysqldumpslow script has been moved from client RPM packages to server RPM packages. This corrects a problem where mysqldumpslow could not be used with a client-only RPM install, because it depends on my_print_defaults which is in the server RPM. (Bug#20216) Bugs fixed: - Security fix: On Linux, and possibly other platforms using case-sensitive filesystems, it was possible for a user granted rights on a database to create or access a database whose name differed only from that of the first by the case of one or more letters. (Bug#17647) - Security fix: If a user has access to MyISAM table t, that user can create a MERGE table m that accesses t. However, if the user's privileges on t are subsequently revoked, the user can continue to access t by doing so through m. If this behavior is undesirable, you can start the server with the new --skip-merge option to disable the MERGE storage engine. (Bug#15195) - Security fix: Invalid arguments to DATE_FORMAT() caused a server crash. (CVE-2006-3469, Bug#20729) Thanks to Jean-David Maillefer for discovering and reporting this problem to the Debian project and to Christian Hammers from the Debian Team for notifying us of it. ... (see http://dev.mysql.com/doc/refman/4.1/en/news-4-1-21.html for the complete bug fix list)
17 lines
950 B
Text
17 lines
950 B
Text
$NetBSD: distinfo,v 1.27 2006/08/31 12:42:42 seb Exp $
|
|
|
|
SHA1 (mysql-4.1.21.tar.gz) = ec761b42d640e4dd051bff939fdcd2895b0e2591
|
|
RMD160 (mysql-4.1.21.tar.gz) = a8e92bb3b1371cde3fd938482b34cb597403debf
|
|
Size (mysql-4.1.21.tar.gz) = 17624947 bytes
|
|
SHA1 (patch-aa) = adc6956d4be304db61aa0323061143fffc1b9751
|
|
SHA1 (patch-ab) = 0959e0ba7316e4fe00b656d7af2d8c2c04ed296f
|
|
SHA1 (patch-af) = fd55cd066ac78601dc12002959d2bfafe243f65b
|
|
SHA1 (patch-av) = 5bb6b9e90b6537d4fad71fb575986b49e56161e0
|
|
SHA1 (patch-aw) = 8e7ad98457ab0b2b96d18cc414b6a773eb564dcc
|
|
SHA1 (patch-ax) = 9ad64516523d6052dca586c6a427a1c64921b891
|
|
SHA1 (patch-ay) = fa4a55fa0df5b92823f2390e42fe46e728aadb25
|
|
SHA1 (patch-ba) = bd34391e522ae12ee63ec6a734f7a31116b2918d
|
|
SHA1 (patch-bb) = 242c97ab4658838a6001d9c288e01209abfcee77
|
|
SHA1 (patch-bc) = 31c933a03e2b05aeaff1d89d3fa542aad663e96a
|
|
SHA1 (patch-bd) = 2070c5946ceea4c1b79ce290d359a811996ce454
|
|
SHA1 (patch-be) = 1ba51c75cec53cb4bd6d1b5e71f776869cc340ac
|