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-cmd-line-utils_libedit_vi.c
SVNWeb

Number of commits found XX: 4

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
Fri, 6 May 2016
[ 14:40 riggs ] Original commit   Revision:414707
414707 databases/mysql57-client/Makefile
414707 databases/mysql57-client/files/patch-CMakeLists.txt
414707 databases/mysql57-client/files/patch-client_CMakeLists.txt
414707 databases/mysql57-client/files/patch-cmake_build__configurations_compiler__options.cmake
414707 databases/mysql57-client/files/patch-cmake_os_DragonFly.cmake
414707 databases/mysql57-client/files/patch-cmd-line-utils_libedit_chartype.h
414707 databases/mysql57-client/files/patch-cmd-line-utils_libedit_vi.c
414707 databases/mysql57-client/files/patch-extra_CMakeLists.txt
414707 databases/mysql57-client/files/patch-include_CMakeLists.txt
414707 databases/mysql57-client/files/patch-include_my__compare.h

(Only the first 10 of 52 ports in this commit are shown above. View all ports for this commit)
Update to 5.7.12, fixing 31 partially critical vulnerabilities

List of vulnerabilities is documented on:
http://vuxml.freebsd.org/freebsd/8c2b2f11-0ebe-11e6-b55e-b499baebfeaf.html
CVE IDs see below.

PR:		206998
Submitted by:	mokhi64@gmail.com (maintainer)
Reviewed by:	rootservice@gmail.com
Approved by:	mokhi64@gmail.com (maintainer)
MFH:		2016Q2
Security:	CVE-2016-0705
		CVE-2016-0639
		CVE-2015-3194
		CVE-2016-0640
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Sun, 10 Jan 2016
[ 20:02 pi ] Original commit   Revision:405741
405741 databases/mysql57-client
405741 databases/mysql57-client/files/patch-cmake_build__configurations_compiler__options.cmake
405741 databases/mysql57-client/files/patch-cmake_build_configurations_compiler_options.cmake
405741 databases/mysql57-client/files/patch-cmake_os_DragonFly.cmake
405741 databases/mysql57-client/files/patch-cmd-line-utils_libedit_chartype.h
405741 databases/mysql57-client/files/patch-cmd-line-utils_libedit_vi.c
405741 databases/mysql57-client/files/patch-include-CMakeLists.txt
405741 databases/mysql57-client/files/patch-include_CMakeLists.txt
405741 databases/mysql57-client/files/patch-include_my__compare.h
405741 databases/mysql57-client/files/patch-include_my_compare.h

(Only the first 10 of 34 ports in this commit are shown above. View all ports for this commit)
databases/mysql57-client, databases/mysql57-server:
	re-add for proper repo-copy

PR:		204607
Thu, 17 Dec 2015
[ 12:08 marino ] Original commit   Revision:403905
403905 databases/mysql57-client/files/patch-cmake_os_DragonFly.cmake
403905 databases/mysql57-client/files/patch-cmd-line-utils_libedit_chartype.h
403905 databases/mysql57-client/files/patch-cmd-line-utils_libedit_vi.c
403905 databases/mysql57-client/files/patch-libmysql_CMakeLists.txt
403905 databases/mysql57-server/Makefile
403905 databases/mysql57-server/files/patch-cmd-line-utils_libedit_chartype.h
403905 databases/mysql57-server/files/patch-cmd-line-utils_libedit_vi.c
403905 databases/mysql57-server/files/patch-include_my__thread__os__id.h
403905 databases/mysql57-server/files/patch-storage_innobase_include_srv0mon.h
databases/mysql57-*: Support DragonFly

PR:	204607

Number of commits found XX: 4

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 42646
Broken 75
Deprecated 170
Ignore 314
Forbidden 4
Restricted 139
No CDROM 71
Vulnerable 21
Expired 37
Set to expire 146
Interactive 0
new 24 hours 12
new 48 hours25
new 7 days64
new fortnight103
new month161

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