mirror of
git://slackware.nl/current.git
synced 2025-01-27 07:59:56 +01:00
07f87f994f
a/aaa_elflibs-15.0-x86_64-17.txz: Rebuilt.
Upgraded: libcap.so.2.28, libelf-0.178.so, libglib-2.0.so.0.6200.4,
libgmodule-2.0.so.0.6200.4, libgobject-2.0.so.0.6200.4,
libgthread-2.0.so.0.6200.4, libidn2.so.0.3.7, libpcre2-8.so.0.9.0,
libtdb.so.1.4.3.
Added: libffi.so.6.0.4, libffi.so.7.1.0.
a/file-5.38-x86_64-2.txz: Rebuilt.
Patched to fix ELF shared libraries misidentified as "statically linked."
a/kernel-firmware-20191220_6871bff-noarch-1.txz: Upgraded.
a/openssl10-solibs-1.0.2u-x86_64-1.txz: Upgraded.
(* Security fix *)
d/guile-2.2.6-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
d/llvm-9.0.1-x86_64-1.txz: Upgraded.
Compiled against libffi-3.3.
d/python-2.7.17-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
d/python3-3.7.6-x86_64-1.txz: Upgraded.
Compiled against libffi-3.3.
d/ruby-2.6.5-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
l/glib2-2.62.4-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
l/libffi-3.3-x86_64-1.txz: Upgraded.
Shared library .so-version bump.
l/libvpx-1.8.2-x86_64-1.txz: Upgraded.
l/pygobject-2.28.7-x86_64-4.txz: Rebuilt.
Recompiled against libffi-3.3.
l/pygobject3-3.34.0-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
l/sip-4.19.20-x86_64-1.txz: Upgraded.
n/cifs-utils-6.10-x86_64-1.txz: Upgraded.
n/dhcpcd-8.1.3-x86_64-1.txz: Upgraded.
n/openssl10-1.0.2u-x86_64-1.txz: Upgraded.
This update fixes a low severity security issue:
Fixed an an overflow bug in the x86_64 Montgomery squaring procedure used in
exponentiation with 512-bit moduli.
For more information, see:
https://www.openssl.org/news/secadv/20191206.txt
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551
(* Security fix *)
n/p11-kit-0.23.18.1-x86_64-2.txz: Rebuilt.
Recompiled against libffi-3.3.
extra/tigervnc/tigervnc-1.10.1-x86_64-1.txz: Upgraded.
From tigervnc.org: "This is a security release to fix a number of issues
that were found by Kaspersky Lab. These issues affect both the client and
server and could theoretically allow a malicious peer to take control
over the software on the other side. No working exploit is known at this
time, and the issues require the peer to first be authenticated. We still
urge users to upgrade when possible."
(* Security fix *)
|
||
|---|---|---|
| .. | ||
| a | ||
| ap | ||
| d | ||
| e | ||
| f | ||
| installer | ||
| k | ||
| kde | ||
| kdei | ||
| l | ||
| n | ||
| t | ||
| tcl | ||
| x | ||
| xap | ||
| xfce | ||
| y | ||
| buildlist-from-changelog.sh | ||
| make_world.sh | ||
| README.TXT | ||
This is the source used for Slackware. To look for a particular bit of source (let's say for 'cp'), first you would look for the full path: fuzzy:~# which cp /bin/cp Then, you grep for the package it came from. Note that the leading '/' is removed: fuzzy:~# grep bin/cp /var/log/packages/* /var/log/packages/cpio-2.4.2.91-i386-1:bin/cpio /var/log/packages/fileutils-4.1-i386-2:bin/cp /var/log/packages/gcc-2.95.3-i386-2:usr/bin/cpp /var/log/packages/gnome-applets-1.4.0.5-i386-1:usr/bin/cpumemusage_applet From this, you can see that 'cp' came from the fileutils-4.1-i386-2 package. The source will be found in a corresponding subdirectory. In this case, that would be ./a/bin. Don't be fooled into thinking that the _bin.tar.gz in this directory is the package with the source code -- anything starting with '_' is just a framework package full of empty files with the correct permissions and ownerships for the completed package to use. Many of these packages now have scripts that untar, patch, and compile the source automatically. These are the 'SlackBuild' scripts. Moving back to the example above, you can figure out which package the bin/cp source came from by examining the SlackBuild script. Have fun! --- Patrick J. Volkerding volkerdi@slackware.com