3 new security updates has been released for Slackware Linux:
- sudo (SSA:2010-257-02)
- samba (SSA:2010-257-01)
- sudo redo (SSA:2010-258-03)
- sudo (SSA:2010-257-02)
- samba (SSA:2010-257-01)
- sudo redo (SSA:2010-258-03)
The following 3 security updates are available for Slackware Linux:
- seamonkey (SSA:2010-253-03)
- mozilla-firefox (SSA:2010-253-01)
- mozilla-thunderbird (SSA:2010-253-02)
- seamonkey (SSA:2010-253-03)
- mozilla-firefox (SSA:2010-253-01)
- mozilla-thunderbird (SSA:2010-253-02)
The following 6 security updates are available for Slackware Linux:
- xorg-server (SSA:2010-240-06)
- pidgin (SSA:2010-240-05)
- kdegraphics (SSA:2010-240-03)
- httpd (SSA:2010-240-02)
- gnupg2 (SSA:2010-240-01)
- php (SSA:2010-240-04)
- xorg-server (SSA:2010-240-06)
- pidgin (SSA:2010-240-05)
- kdegraphics (SSA:2010-240-03)
- httpd (SSA:2010-240-02)
- gnupg2 (SSA:2010-240-01)
- php (SSA:2010-240-04)
New mozilla-firefox packages are available for Slackware Linux
3 new security updates are available for Slackware Linux
libtiff/libpng security updates are available for Slackware Linux
The following 5 security updates are available for Slackware Linux:
- seamonkey (SSA:2010-176-03)
- bind (SSA:2010-176-01)
- mozilla-firefox (SSA:2010-176-02)
- mozilla-thunderbird (SSA:2010-176-04)
- cups (SSA:2010-176-05)
- seamonkey (SSA:2010-176-03)
- bind (SSA:2010-176-01)
- mozilla-firefox (SSA:2010-176-02)
- mozilla-thunderbird (SSA:2010-176-04)
- cups (SSA:2010-176-05)
New samba packages are available for Slackware 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, 12.2, and 13.0 to fix a security issue
Linux Journal takes a look at Slackware Linux 13.1
Slackware Linux 13.1 has been released. Here the release announcement:
Slackware 13.1 RC1 has been released
Slackware 13.1 Beta 1 has been released
Slackware 13.0 has been released
New mozilla-firefox packages are available for Slackware 12.2, and -current to fix security issues.
The new packages may also be used with earlier versions of Slackware.
More details about the issues may be found on the Mozilla website:
http://www.mozilla.org/security/known-vulnerabilities/firefox30.html
The new packages may also be used with earlier versions of Slackware.
More details about the issues may be found on the Mozilla website:
http://www.mozilla.org/security/known-vulnerabilities/firefox30.html
New curl packages are available for Slackware 9.1, 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, 12.2, and -current to fix a security issue.
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0037
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0037
New xterm packages are available for Slackware 12.0, 12.1, 12.2, and -current to fix a security issue.
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2383
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2383
Updated bind packages are available for Slackware 10.2 and 11.0 to address a load problem. It was reported that the initial build of these updates complained that the Linux capability module was not present and would refuse to load. It was determined that the packages which were compiled on 10.2 and 11.0 systems running 2.6 kernels, and although the installed kernel headers are from 2.4.x, it picked up on this resulting in packages that would only run under 2.4 kernels. These new packages address the issue.
Slackware 12.2 has been released. Here the release announcement:
New php packages are available for Slackware 12.0, 12.1, and -current to fix security issues, as well as make improvements and fix bugs.
New samba packages are available for Slackware 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, and -current to fix a possible security vulnerability involving the reading of uninitialized memory.
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4314
More details about this issue may be found in the Common Vulnerabilities and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4314
