diff options
Diffstat (limited to 'ChangeLog.rss')
| -rw-r--r-- | ChangeLog.rss | 99 |
1 files changed, 96 insertions, 3 deletions
diff --git a/ChangeLog.rss b/ChangeLog.rss index b52ce43a7..cba63e613 100644 --- a/ChangeLog.rss +++ b/ChangeLog.rss @@ -11,10 +11,103 @@ <description>Tracking Slackware development in git.</description> <language>en-us</language> <id xmlns="http://www.w3.org/2005/Atom">urn:uuid:c964f45e-6732-11e8-bbe5-107b4450212f</id> - <pubDate>Tue, 23 Aug 2022 19:27:56 GMT</pubDate> - <lastBuildDate>Wed, 24 Aug 2022 11:30:15 GMT</lastBuildDate> + <pubDate>Fri, 26 Aug 2022 04:02:20 GMT</pubDate> + <lastBuildDate>Sat, 27 Aug 2022 11:30:15 GMT</lastBuildDate> <generator>maintain_current_git.sh v 1.17</generator> <item> + <title>Fri, 26 Aug 2022 04:02:20 GMT</title> + <pubDate>Fri, 26 Aug 2022 04:02:20 GMT</pubDate> + <link>https://git.slackware.nl/current/tag/?h=20220826040220</link> + <guid isPermaLink="false">20220826040220</guid> + <description> + <![CDATA[<pre> +patches/packages/linux-5.15.63/*: Upgraded. + These updates fix various bugs and security issues. + Be sure to upgrade your initrd after upgrading the kernel packages. + If you use lilo to boot your machine, be sure lilo.conf points to the correct + kernel and initrd and run lilo as root to update the bootloader. + If you use elilo to boot your machine, you should run eliloconfig to copy the + kernel and initrd to the EFI System Partition. + For more information, see: + Fixed in 5.15.39: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1974 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1975 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1734 + Fixed in 5.15.40: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1943 + Fixed in 5.15.41: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28893 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32296 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1012 + Fixed in 5.15.42: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1652 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1729 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21499 + Fixed in 5.15.44: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1789 + Fixed in 5.15.45: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2873 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1966 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32250 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2078 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1852 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1972 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2503 + Fixed in 5.15.46: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1184 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1973 + Fixed in 5.15.47: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34494 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34495 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32981 + Fixed in 5.15.48: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21125 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21166 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21123 + Fixed in 5.15.53: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2318 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33743 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33742 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33741 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33740 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26365 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33744 + Fixed in 5.15.54: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33655 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34918 + Fixed in 5.15.56: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36123 + Fixed in 5.15.57: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29900 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29901 + Fixed in 5.15.58: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21505 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1462 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36879 + Fixed in 5.15.59: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36946 + Fixed in 5.15.60: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26373 + Fixed in 5.15.61: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2586 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2585 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1679 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2588 + (* Security fix *) +patches/packages/vim-9.0.0270-x86_64-1_slack15.0.txz: Upgraded. + We're just going to move to vim-9 instead of continuing to backport patches + to the vim-8 branch. Most users will be better served by this. + Fixed use after free and null pointer dereference. + Thanks to marav for the heads-up. + For more information, see: + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2946 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2923 + (* Security fix *) +patches/packages/vim-gvim-9.0.0270-x86_64-1_slack15.0.txz: Upgraded. + </pre>]]> + </description> + </item> + <item> <title>Tue, 23 Aug 2022 19:27:56 GMT</title> <pubDate>Tue, 23 Aug 2022 19:27:56 GMT</pubDate> <link>https://git.slackware.nl/current/tag/?h=20220823192756</link> @@ -23,7 +116,7 @@ <![CDATA[<pre> extra/sendmail/sendmail-8.17.1-x86_64-3_slack15.0.txz: Rebuilt. In recent versions of glibc, USE_INET6 has been removed which caused sendmail - to reject mail from IPv6 addresses. Adding -DHAS_GETHOSTBYNNAME2=1 to the + to reject mail from IPv6 addresses. Adding -DHAS_GETHOSTBYNAME2=1 to the site.config.m4 allows the reverse lookups to work again fixing this issue. Thanks to talo. extra/sendmail/sendmail-cf-8.17.1-noarch-3_slack15.0.txz: Rebuilt. |