Please be aware the database client is vulnerable
to CVE-2015-3152 - SSL Downgrade aka "BACKRONYM".
You may find more information at the following URL:
http://www.vuxml.org/freebsd/36bd352d-299b-11e5-86ff-14dae9d210b8.html
Although this database client is not listed as
"affected", it is vulnerable and will not be
receiving a patch. Please take note of this when
deploying this software.
databases/mysql56-client: be ready for OpenSSL 3.0 in base
Use same approach as in f89fd0980a5cbcc54597578015f660643cdccf0f
for mysql57-client. PORTREVISION not bumped intentionally.
PR: 271656
databases/mysql56-{client, server}: Mark DEPRECATED
MySQL 5.5 has reached it's Extended Support on Febuary 2021. Under
sustaining support there is no New updates, fixes, security alerts,
data fixes, and critical patch updates. Hence we are setting it to EXPIRE
before 2023Q3.
Sponsored by: Netzkommune GmbH
*/*: Remove redundant '-*' from CONFLICTS definitions
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
databases/mysql56-{client, server}: Update to latest release 5.6.48
Bugfix:
- InnoDB: A tablespace import operation that failed due to the source and
destination tables being defined with different DATA DIRECTORY clauses reported
an insufficiently descriptive schema mismatch error. Moreover, if a .cfg file
was not present, the same operation would raise an assertion failure. A more
informative error message is now reported in both cases before the import
operation is terminated due to the data directory mismatch.
- InnoDB: Updating certain InnoDB system variables that take string values
raised invalid read errors during Valgrind testing.
- Replication: In the event of an unplanned disconnection of a replication slave
from the master, the reference to the master's dump thread might not be removed
from the list of registered slaves, in which case statements that accessed the
list of slaves would fail. The issue has now been fixed
- Replication: With the settings binlog_format=MIXED,
tx_isolation=READ-COMMITTED, and binlog_row_image=FULL, an INSERT ... SELECT
query involving a transactional storage engine omitted any columns with a null
value from the row image written to the binary log. This happened because when
processing INSERT ... SELECT statements, the columns were marked for inserts
before the binary logging format was selected. The issue has now been fixed.
More Infos: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-48.html
MFH: 2020Q2
Security: 21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security: 622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by: Netzkommune GmbH
This fix a Problem, when MySQL build with libressl
/var/ports/usr/ports/databases/mysql56-client/work/mysql-5.6.47/vio/viosslfactories.c:230:25:
error: use of undeclared identifier 'SSL_OP_NO_TLSv1_3'
SSL_OP_NO_TLSv1_3 |
^
/var/ports/usr/ports/databases/mysql56-client/work/mysql-5.6.47/vio/viosslfactories.c:275:12:
warning: implicit declaration of function 'SSL_CTX_set_ciphersuites' is invalid
in C99 [-Wimplicit-function-declaration]
if (0 == SSL_CTX_set_ciphersuites(ssl_fd->ssl_context, ""))
Special thanks for his help to: fluffy
PR: 244320
MFH: 2020Q1
Sponsored by: Netzkommune GmbH
databases/mysql56-{client, server}: Update to latest release 5.6.46
Bugfix:
- Improper locking during storage engine initialization could cause a server
exit.
- A query with a WHERE clause whose predicate contained a numeric value in
scientific notation was not handled correctly.
- VS2019 produced compilation errors with debug compilation selected due to use
of the /ZI flag. Now /Z7 is used instead.
- For MySQL Community Edition, the cipher order specified by the client was
used in preference to the order on the server side, unless the server was confi
- Password masking was incomplete for SHOW PROCESSLIST and some
INFORMATION_SCHEMA and Performance Schema tables.
- The -DWITH_EXAMPLE_STORAGE_ENGINE=1 CMake option was ignored but should not
have been. If -DWITH_EXAMPLE_STORAGE_ENGINE=0 is given, the EXAMPLE storage e
More Info: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-46.html
Approved by: mmokhi (maintainer, implicit)
MFH: 2020Q1
Security: fc91f2ef-fd7b-11e9-a1c7-b499baebfeaf
Sponsored by: Netzkommune GmbH
databases/mysql56-{client, server}: Update to latest release 5.6.43
This update (released on Jan 21st) includes:
Bugfix:
-Correct the handling of quotes for identifiers in
ROLLBACK TO SAVEPOINT statements.
-Don't permit creation of dbs with same name as redo log file
(Bug #28867993).
-Use strncmp() instead of memcmp() for comparing logfile names
(prevent the uninitialized memory as result).
More info from upstream:
https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-43.html
Sponsored by: The FreeBSD Foundation
databases/mysql56-{client, server}: Fix inconsistencies on texinfo and man files
After `usr/info` moved to `usr/share/info` and now that texinfo is not
in base on any of the supported version of FreeBSD, This makes the port
consistent.
Reported by: ohauer
Sponsored by: The FreeBSD Foundation
databases/mysql56-{client, server}: Upgrade to new release 5.6.42
Upstream Bug #27788907, Bug #90264 fixed
Bug Fixes:
Raised assertion during an OPTIMIZE TABLE operation for InnoDB: Bug
#27753193
For MEMORY tables, memory overflow errors could occur: Bug #27799513
Incorrectly handled very long table keys on replication slaves: Bug
#27930505
More info on update:
https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-42.html
Sponsored by: The FreeBSD Foundation
databases/mysql56-{client, server}: Fix build with OpenSSL1.1.x
This is the backport of fix on mysql57
PR: 225888
Reported by: brnrd
Reviewed by: antoine
Sponsored by: The FreeBSD Foundation
databases/mysql56-{client, server}: Update to 5.6.39
This update fixes bugs like CVE-2018-2696, CVE-2018-2562,
and CVE-2018-2583 in MySQL protocol by upstream
PR: 225240
Sponsored by: Netzkommune GmbH
databases/mysql56-server: unbreak build with Clang 6 (C++14 by default)
sql-common/client_authentication.cc:87:56: error: comparison between pointer and
integer ('char *' and 'int')
mysql->options.extension->server_public_key_path != '\0')
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~
sql/sql_trigger.cc:195:5: error:
non-constant-expression cannot be narrowed from type 'int' to 'size_t'
(aka 'unsigned long') in
initializer list [-Wc++11-narrowing]
static_cast<int>(my_offsetof(class Table_triggers_list, definitions_list)),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Reported by: antoine (via bug 224669)
databases/mysql56-{server client}: Update to latest 5.6.36
Also Delete patches that merged/fixed by upstream.
And fix some no-longer-valid (but needed) patches.
Reviewed by: feld, mat (mentors)
Approved by: feld (mentor)
Differential Revision: https://reviews.freebsd.org/D10392
databases/mysql56: Update to 5.6.35
- Port improvements from MySQL 5.7 port
- Use system libs instead of bundled
- Fix many open PRs
- Change MAINTAINER
PR: 216244192657198812199751205093
PR: 209618211248205983209338
Bump PORTREVISION of the client and add pkg-message to warn about
CVE-2015-3152 which will not get patched
Security: CVE-2015-3152
Security: 36bd352d-299b-11e5-86ff-14dae9d210b8
Unbreak on head: instead of using headers from base libedit and
linking against readline, use libedit from ports
Note: this may need a bit more patching during next libedit port update
Reported by: pkg-fallout
Fix mysql51/55/56 build with clang on i386.
The included yassl library contains inline asm (only for i386) using
intel syntax which clang does not support. For now, just disable the
inline asm when clang is used and use the standard C implementation like
on every other architecture.
Approved by: ale (maintainer)
