notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)

Current status

The server has been repaired, with a new power supply, for $23. I am waiting for lower COVID rates before visiting the datacenter to return it.
non port: databases/mysql57-client/files/patch-cmake_ssl.cmake
SVNWeb

Number of commits found XX: 5

Wed, 3 Feb 2021
[ 02:02 fluffy ] Original commit   Revision:563858
563858 databases/mysql57-client/Makefile
563858 databases/mysql57-client/files/patch-cmake_ssl.cmake
563858 databases/mysql57-client/files/patch-vio_viosslfactories.c
563858 databases/mysql57-server/Makefile
563858 databases/mysql57-server/files/patch-cmake_ssl.cmake
563858 databases/mysql57-server/files/patch-rapid_plugin_group_replication_libmysqlgcs_src_bindings_xcom_xcom_xcom_ssl_transport.c
563858 databases/mysql57-server/files/patch-sql_locks_shared__spin__lock.cc
563858 databases/mysql57-server/files/patch-vio_viosslfactories.c
databases/mysql56*: update to 5.7.33 release

Disable detect of TLSv1.3 functions - it's broken with LibreSSL

Release Notes:	https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-33.html
Requested by:	joneum
Thu, 9 Jul 2020
[ 10:09 joneum ] Original commit   Revision:541739
541739 databases/mysql57-client/files/patch-cmake_ssl.cmake
databases/mysql57-client: fix SIGSEGV due to static OpenSSL linking

As opposed to MySQL 8.0.x branch that switched to dynamic linking for OpenSSL
libraries, MySQL 5.7.30 still statically links client applications with OpenSSL.

Meantime, OpenSSL supports dynamic loading of external engines like
security/gost-engine. If such engine is configured to load in the openssl.cnf,
mysql CLI application crashes at start with SIGSEGV early trying to initialize
OpenSSL.

This loads dynamic engine library libgost.so that calls OpenSSL function using
second (uninitialized) instance of OpenSSL leading to crash.

The problem is fixed with small backport from MySQL 8.0.x for cmake/ssl.cmake
distribution file we already patching anyway.

https://github.com/openssl/openssl/issues/12368

PR:		247803
Reported by:	eugen
Sponsored by:	Netzkommune GmbH
Thu, 30 Apr 2020
[ 08:15 joneum ] Original commit   Revision:533416
533416 databases/mysql57-client/files/patch-cmake_ssl.cmake
533416 databases/mysql57-client/files/patch-cmd-line-utils_libedit_chartype.h
533416 databases/mysql57-client/files/patch-cmd-line-utils_libedit_vi.c
533416 databases/mysql57-server/Makefile
533416 databases/mysql57-server/distinfo
533416 databases/mysql57-server/files/patch-cmake_ssl.cmake
533416 databases/mysql57-server/files/patch-cmd-line-utils_libedit_chartype.h
533416 databases/mysql57-server/files/patch-cmd-line-utils_libedit_vi.c
databases/mysq56-{client, server}: Update to latest release 5.7.30

Bugs Fixed:
- InnoDB: The row_upd_clust_rec_by_insert function, which marks a clustered
index record as deleted and inserts an updated version of the record into the
clustered index, passed an incorrect n_ext value (the total number of external
fields) to lower level functions, causing an assertion failure.
- InnoDB: An operation performed with the innodb_buffer_pool_evict debug
variable set to uncompressed caused an assertion failure.
- InnoDB: An add column operation caused an assertion failure. The failure was
due to a dangling pointer.
- nnoDB: Updating certain InnoDB system variables that take string values raised
invalid read errors during Valgrind testing.
- InnoDB: An insert statement on a table with a spatial index raised a record
type mismatch assertion due to a tuple corruption.
- InnoDB: A function that calculates undo log record size could calculate an
incorrect length value in the case of a corrupted undo log record, resulting in
a malloc failure. Assertion code was added to detect incorrect calculations.
- Replication: While an SQL statement was in the process of being rewritten for
the binary log so that sensitive information did not appear in plain text, if a
SHOW PROCESSLIST statement was used to inspect the query, the query could become
corrupted when it was written to the binary log, causing replication to stop.
The process of rewriting the query is now kept private, and the query thread is
updated only when rewriting is complete.
- Replication: When a GRANT or REVOKE statement is only partially executed, an
incident event is logged in the binary log, which makes the replication slave's
applier thread stop so that the slave can be reconciled manually with the
master. Previously, if a failed GRANT or REVOKE statement was the first
statement executed in the session, no GTID was applied to the incident event
(because the cache manager did not yet exist for the session), causing an error
on the replication slave. Also, no incident event was logged in the situation
where a GRANT statement created a user but then failed because the privileges
had been specified incorrectly, again causing an error on the replication slave.
Both these issues have now been fixed.
- Replication: When a replication slave has a generated column that the master
does not have in that table, with a secondary index on the generated column, the
generated expression should be evaluated and the value stored by the storage
engine in the secondary index. When row-based binary logging is in use, the
replication slave assigns default values to any fields that are not in the
master's definition of the table. In the case of a generated column, which does
not have a default value, the slave was previously assigning a null or a zero
value to the column. This value was then stored by the storage engine in the
secondary index, causing both the table and the index to become corrupted. To
fix this issue, generated columns in a table on a replication slave are now
re-evaluated before the values are sent to the storage engine.
- 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.

Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-30.html

MFH:		2020Q2
Security:	21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security:	622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by:	Netzkommune GmbH
Sat, 7 Dec 2019
[ 17:55 joneum ] Original commit   Revision:519226
519226 databases/mysql57-client/Makefile
519226 databases/mysql57-client/files/patch-cmake_ssl.cmake
/ram/usr/ports/databases/mysql57-client/work/mysql-5.7.28/vio/viosslfactories.c:505:27:
error: use of undeclared identifier 'SSL_OP_NO_TLSv1_3'
                        | SSL_OP_NO_TLSv1_3

This patch fix this error

PR:		242474
Approved by:	mmokhi (maintainer, implicit)
Sponsored by:	Netzkommune GmbH
Wed, 24 Aug 2016
[ 18:56 brnrd ] Original commit   Revision:420816
420816 databases/mysql57-client/files/patch-cmake_ssl.cmake
420816 databases/mysql57-server/Makefile
420816 databases/mysql57-server/files/patch-cmake_ssl.cmake
databases/mysql57-server: Fix build with LibreSSL

  - Fix building when OPENSSL_VERSION_NUMBER == 2
  - Switch USE_OPENSSL to USES= ssl

PR:		211770
Submitted by:	Markus Kohlmeyer <rootservice@gmail.com>
Reported by:	Markus Kohlmeyer <rootservice@gmail.com>
Approved by:	Mahdi Mokhtari <mokhi64@gmail.com>
MFH:		2016Q3

Number of commits found XX: 5

Login
User Login
Create account

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD

This site
What is FreshPorts?
About the authors
Issues
FAQ
How big is it?
The latest upgrade!
Privacy
Blog
Contact

Search
Enter Keywords:
 
more...

Latest Vulnerabilities
vaultFeb 27
redisFeb 23
redis-develFeb 23
redis5Feb 23
zeekFeb 22
jenkinsFeb 20
raptor2Feb 20
asterisk13Feb 18
asterisk13Feb 18
asterisk13Feb 18
asterisk16Feb 18
asterisk16Feb 18
asterisk16Feb 18
asterisk16Feb 18
asterisk16Feb 18

13 vulnerabilities affecting 98 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Last updated:
2021-02-27 01:52:12


Ports
Home
Categories
Deleted ports
Sanity Test Failures
Newsfeeds

Statistics
Graphs
NEW Graphs (Javascript)
Traffic

Calculated hourly:
Port count 42629
Broken 77
Deprecated 174
Ignore 316
Forbidden 4
Restricted 139
No CDROM 71
Vulnerable 21
Expired 37
Set to expire 150
Interactive 0
new 24 hours 15
new 48 hours23
new 7 days44
new fortnight84
new month149

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD
Valid HTML, CSS, and RSS.
Copyright © 2000-2021 Dan Langille. All rights reserved.