summaryrefslogtreecommitdiff
path: root/ChangeLog.txt
diff options
context:
space:
mode:
authorPatrick J Volkerding <volkerdi@slackware.com>2018-08-01 22:38:53 +0000
committerEric Hameleers <alien@slackware.com>2018-08-02 09:00:35 +0200
commit22d153f9e271d438e0d5094ac8603b97105665bd (patch)
tree045672fa5142b2b177ac6331aa58ba08d6fe8d7e /ChangeLog.txt
parentda51cf8739bc365374ee8a91bb2db905b5e38b82 (diff)
downloadcurrent-22d153f9e271d438e0d5094ac8603b97105665bd.tar.gz
Wed Aug 1 22:38:53 UTC 201820180801223853
ap/man-db-2.8.4-x86_64-1.txz: Upgraded. d/gdb-8.1.1-x86_64-1.txz: Upgraded. d/python-pip-18.0-x86_64-1.txz: Upgraded. d/python-setuptools-40.0.0-x86_64-1.txz: Upgraded. d/python3-3.6.6-x86_64-1.txz: Upgraded. l/libpcap-1.9.0-x86_64-1.txz: Upgraded. l/pango-1.42.3-x86_64-1.txz: Upgraded. x/libdrm-2.4.93-x86_64-1.txz: Upgraded. xap/blueman-2.0.6-x86_64-1.txz: Upgraded. This update fixes an issue where blueman-mechanism did not enforce the polkit action 'org.blueman.network.setup' for which a polkit policy is shipped. This meant that any user with access to the D-Bus system bus was able to access the related API without authentication. The result was an unspecified impact on the networking stack. Thanks to Matthias Gerstner for discovering this issue. (* Security fix *) testing/packages/glibc-2.28-x86_64-1.txz: Added. These packages are in /testing pending FTBFS analysis. They seem to work fine here, but with a few header file deprecations and some other possible API changes and incompatibilities (see the NEWS file), I expect there will be some changes required to various packages. Feel free to test them out though. Because of changes to the way glibc is built and installed that started with the glibc-2.27 packages, you can upgrade to these packages and also (if you wish) downgrade back to glibc-2.27 using upgradepkg. testing/packages/glibc-i18n-2.28-x86_64-1.txz: Added. testing/packages/glibc-profile-2.28-x86_64-1.txz: Added. testing/packages/glibc-solibs-2.28-x86_64-1.txz: Added.
Diffstat (limited to 'ChangeLog.txt')
-rw-r--r--ChangeLog.txt30
1 files changed, 30 insertions, 0 deletions
diff --git a/ChangeLog.txt b/ChangeLog.txt
index 6923dd87..7ef26ba9 100644
--- a/ChangeLog.txt
+++ b/ChangeLog.txt
@@ -1,3 +1,33 @@
+Wed Aug 1 22:38:53 UTC 2018
+ap/man-db-2.8.4-x86_64-1.txz: Upgraded.
+d/gdb-8.1.1-x86_64-1.txz: Upgraded.
+d/python-pip-18.0-x86_64-1.txz: Upgraded.
+d/python-setuptools-40.0.0-x86_64-1.txz: Upgraded.
+d/python3-3.6.6-x86_64-1.txz: Upgraded.
+l/libpcap-1.9.0-x86_64-1.txz: Upgraded.
+l/pango-1.42.3-x86_64-1.txz: Upgraded.
+x/libdrm-2.4.93-x86_64-1.txz: Upgraded.
+xap/blueman-2.0.6-x86_64-1.txz: Upgraded.
+ This update fixes an issue where blueman-mechanism did not enforce the
+ polkit action 'org.blueman.network.setup' for which a polkit policy is
+ shipped. This meant that any user with access to the D-Bus system bus was
+ able to access the related API without authentication. The result was an
+ unspecified impact on the networking stack.
+ Thanks to Matthias Gerstner for discovering this issue.
+ (* Security fix *)
+testing/packages/glibc-2.28-x86_64-1.txz: Added.
+ These packages are in /testing pending FTBFS analysis. They seem to work
+ fine here, but with a few header file deprecations and some other
+ possible API changes and incompatibilities (see the NEWS file), I expect
+ there will be some changes required to various packages. Feel free to
+ test them out though. Because of changes to the way glibc is built and
+ installed that started with the glibc-2.27 packages, you can upgrade to
+ these packages and also (if you wish) downgrade back to glibc-2.27 using
+ upgradepkg.
+testing/packages/glibc-i18n-2.28-x86_64-1.txz: Added.
+testing/packages/glibc-profile-2.28-x86_64-1.txz: Added.
+testing/packages/glibc-solibs-2.28-x86_64-1.txz: Added.
++--------------------------+
Tue Jul 31 05:53:40 UTC 2018
a/kernel-firmware-20180730_7b5835f-noarch-1.txz: Upgraded.
l/fuse-2.9.8-x86_64-1.txz: Upgraded.