Commit graph

8 commits

Author SHA1 Message Date
taca
93a53fbf88 Fix some my_time_t (long) v.s. time_t problem introduced MySQL 5.1.49.
This problem results mysqld to exit on start up.

		5.1/i386	5.1/amd64	5.99.38/i386	5.99.38/amd64
my_time_t	int32_t		int64_t		int32_t		int64_t
time_t		int32_t		int32_t		int64_t		int64_t

I confirmed to mysqld running on these four case except 5.99.38/i386.

Bump PKG_REVISION.
2010-08-13 14:25:34 +00:00
taca
f1fdf4c660 Update mysql51-client and mysql51-server to 5.1.49.
Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html
for full changes.


* InnoDB Plugin has been upgraded to version 1.0.10. This version is
  considered of General Availability (GA) quality.

  In this release, the InnoDB Plugin is included in source and binary
  distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and
  generic Linux RPM packages. It also does not work for FreeBSD 6 and
  HP-UX or for Linux on generic ia64.

Bugs fixed:

* Security Fix: After changing the values of the innodb_file_format or
  innodb_file_per_table configuration parameters, DDL statements could
  cause a server crash. (Bug#55039)

* Security Fix: Joins involving a table with with a unique SET column
  could cause a server crash. (Bug#54575)

* Security Fix: Incorrect handling of NULL arguments could lead to a
  crash for IN() or CASE operations when NULL arguments were either
  passed explicitly as arguments (for IN()) or implicitly generated by
  the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477)

* Security Fix: A malformed argument to the BINLOG statement could
  result in Valgrind warnings or a server crash. (Bug#54393)

* Security Fix: Use of TEMPORARY InnoDB tables with nullable columns
  could cause a server crash. (Bug#54044)

* Security Fix: The server could crash if there were alternate reads
  from two indexes on a table using the HANDLER interface. (Bug#54007)

* Security Fix: Using EXPLAIN with queries of the form SELECT
  ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server
  crash. (Bug#52711)

* Security Fix: LOAD DATA INFILE did not check for SQL errors and sent
  an OK packet even when errors were already reported. Also, an assert
  related to client-server protocol checking in debug servers
  sometimes was raised when it should not have been. (Bug#52512)
2010-08-11 23:18:04 +00:00
taca
aa5d9c6e8d Update mysql51-{client,server} package to 5.1.47.
For full changes, see http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html.

Here is important changes:


InnoDB Plugin Notes:

    * InnoDB Plugin has been upgraded to version 1.0.8. This version
      is considered of General Availability (GA) quality. InnoDB
      Plugin Change History, may contain information in addition to
      those changes reported here.

      In this release, the InnoDB Plugin is included in source and
      binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64,
      ia64), and generic Linux RPM packages. It also does not work for
      FreeBSD 6 and HP-UX or for Linux on generic ia64.

Functionality added or changed:

    * InnoDB stores redo log records in a hash table during
      recovery. On 64-bit systems, this hash table was 1/8 of the
      buffer pool size. To reduce memory usage, the dimension of the
      hash table was reduced to 1/64 of the buffer pool size (or 1/128
      on 32-bit systems). (Bug#53122)

Security fixed:

    * Security Fix: The server failed to check the table name argument
      of a COM_FIELD_LIST command packet for validity and compliance
      to acceptable table name standards. This could be exploited to
      bypass almost all forms of checks for privileges and table-level
      grants by providing a specially crafted table name argument to
      COM_FIELD_LIST.

      In MySQL 5.0 and above, this allowed an authenticated user with
      SELECT privileges on one table to obtain the field definitions
      of any table in all other databases and potentially of other
      MySQL instances accessible from the server's file system.

      Additionally, for MySQL version 5.1 and above, an authenticated
    user with DELETE or SELECT privileges on one table could delete or
    read content from any other table in all databases on this server,
    and potentially of other MySQL instances accessible from the
    server's file system. (Bug#53371, CVE-2010-1848)

    * Security Fix: The server was susceptible to a buffer-overflow
      attack due to a failure to perform bounds checking on the table
      name argument of a COM_FIELD_LIST command packet. By sending
      long data for the table name, a buffer is overflown, which could
      be exploited by an authenticated user to inject malicious
      code. (Bug#53237, CVE-2010-1850)

    * Security Fix: The server could be tricked into reading packets
      indefinitely if it received a packet larger than the maximum
      size of one packet. (Bug#50974, CVE-2010-1849)
2010-05-26 01:52:21 +00:00
wiz
dfdea861b6 Fix build on DragonFly by removing DragonFly-specific patch.
From Alexander Polakov in PR 43280.
2010-05-08 20:48:37 +00:00
taca
617b94d60a Update mysql51-client/mysql51-server package to 5.1.46.
This is maintainous release and please refer for full changes:

	http://dev.mysql.com/doc/refman/5.1/en/news-5-1-46.html
2010-04-24 15:59:23 +00:00
taca
0238d6eb3b Update mysql51-client/mysql51-server package to 5.1.45.
This is maintainous release and please refer for full changes:

	http://dev.mysql.com/doc/refman/5.1/en/news-5-1-45.html

Added a patch for recent security problem to mysql51-server, too.

	http://secunia.com/advisories/39454
2010-04-20 22:58:10 +00:00
taca
6c0a9be54c Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS.
These are control some optional functions for mysql51-server (leaf package).

Bump PKGREVISION.
2010-03-21 14:41:41 +00:00
taca
e605d723d7 Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including
embedded server (by PKG_OPTION).

For release MySQL 5.1 specific information please refer:

	http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html


MySQL is a SQL (Structured Query Language) database server.  SQL is the
most popular database language in the world.  MySQL is a client-server
implementation that consists of a server daemon `mysqld' and many
different client programs/libraries.

The main goals of MySQL are speed and robustness.

The base upon which MySQL is built is a set of routines that have been
used in a highly demanding production environment for many years.  While
MySQL is still in development it already offers a rich and highly useful
function set.

The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL).

This package contains the MySQL server programs and libraries including
embedded server (by PKG_OPTION).
2010-03-04 16:28:57 +00:00