SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thu Jan 30 04:59:13 UTC 2020
a/kernel-generic-5.4.16-x86_64-1.txz: Upgraded.
a/kernel-huge-5.4.16-x86_64-1.txz: Upgraded.
a/kernel-modules-5.4.16-x86_64-1.txz: Upgraded.
ap/linuxdoc-tools-0.9.73-x86_64-5.txz: Rebuilt.
gnome-doc-tools: Make '/usr/bin/xml2po' and its accompanying Python module
build against Python3.
Thanks to bassmadrigal and ponce on LQ for the report and the patch.
docbook2x: Removed '--disable-maintainer-mode' configuration flag because
it's no longer valid.
Thanks to Stuart Winter.
d/kernel-headers-5.4.16-x86-1.txz: Upgraded.
k/kernel-source-5.4.16-noarch-1.txz: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Fri Jan 24 22:59:00 UTC 2020
patches/packages/mozilla-thunderbird-68.4.2-x86_64-1_slack14.2.txz: Upgraded.
This release contains security fixes and improvements.
For more information, see:
https://www.mozilla.org/en-US/thunderbird/68.4.2/releasenotes/
https://www.mozilla.org/security/known-vulnerabilities/thunderbird.html
(* Security fix *)
+--------------------------+
...
+--------------------------+
Thu Jun 30 20:26:57 UTC 2016
Slackware 14.2 x86_64 stable is released!
Wed Jan 22 22:53:32 UTC 2020
patches/packages/bind-9.11.15-x86_64-1_slack14.1.txz: Upgraded.
This is a bugfix release:
With some libmaxminddb versions, named could erroneously match an IP address
not belonging to any subnet defined in a given GeoIP2 database to one of the
existing entries in that database. [GL #1552]
Fix line spacing in `rndc secroots`. Thanks to Tony Finch. [GL #2478]
+--------------------------+
...
+--------------------------+
Mon Nov 4 17:08:47 UTC 2013
Slackware 14.1 x86_64 stable is released!
Wed Jan 22 22:53:32 UTC 2020
patches/packages/bind-9.11.15-x86_64-1_slack14.0.txz: Upgraded.
This is a bugfix release:
With some libmaxminddb versions, named could erroneously match an IP address
not belonging to any subnet defined in a given GeoIP2 database to one of the
existing entries in that database. [GL #1552]
Fix line spacing in `rndc secroots`. Thanks to Tony Finch. [GL #2478]
+--------------------------+
...
+--------------------------+
Wed Sep 26 01:10:42 UTC 2012
Slackware 14.0 x86_64 stable is released!
Tue Jun 19 22:35:25 UTC 2018
patches/packages/gnupg-1.4.23-x86_64-1_slack13.37.txz: Upgraded.
Sanitize the diagnostic output of the original file name in verbose mode.
By using a made up file name in the message it was possible to fake status
messages. Using this technique it was for example possible to fake the
verification status of a signed mail.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
(* Security fix *)
+--------------------------+
...
+--------------------------+
Fri Apr 6 20:47:43 UTC 2018
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
# #
# Effective July 5, 2018, security patches will no longer be #
# provided for the following versions of Slackware (which will all #
# be more than 7 years old at that time): #
# Slackware 13.0, Slackware 13.1, Slackware 13.37. #
# If you are still running these versions you should consider #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own #
# security patches. #
####################################################################
patches/packages/patch-2.7.4-x86_64-2_slack13.37.txz: Rebuilt.
Fix arbitrary shell execution possible with obsolete ed format patches.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000156
(* Security fix *)
+--------------------------+
...
+--------------------------+
Mon Apr 25 13:37:00 UTC 2011
Slackware 13.37 x86_64 stable is released!
Tue Jun 19 22:35:25 UTC 2018
patches/packages/gnupg-1.4.23-x86_64-1_slack13.1.txz: Upgraded.
Sanitize the diagnostic output of the original file name in verbose mode.
By using a made up file name in the message it was possible to fake status
messages. Using this technique it was for example possible to fake the
verification status of a signed mail.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
(* Security fix *)
+--------------------------+
...
+--------------------------+
Fri Apr 6 20:47:43 UTC 2018
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
# #
# Effective July 5, 2018, security patches will no longer be #
# provided for the following versions of Slackware (which will all #
# be more than 7 years old at that time): #
# Slackware 13.0, Slackware 13.1, Slackware 13.37. #
# If you are still running these versions you should consider #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own #
# security patches. #
####################################################################
patches/packages/patch-2.7.4-x86_64-2_slack13.1.txz: Rebuilt.
Fix arbitrary shell execution possible with obsolete ed format patches.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000156
(* Security fix *)
+--------------------------+
...
+--------------------------+
Wed May 19 08:58:23 UTC 2010
Slackware 13.1 x86_64 stable is released!
Tue Jun 19 22:35:25 UTC 2018
patches/packages/gnupg-1.4.23-x86_64-1_slack13.0.txz: Upgraded.
Sanitize the diagnostic output of the original file name in verbose mode.
By using a made up file name in the message it was possible to fake status
messages. Using this technique it was for example possible to fake the
verification status of a signed mail.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
(* Security fix *)
+--------------------------+
...
+--------------------------+
Fri Apr 6 20:47:43 UTC 2018
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
# #
# Effective July 5, 2018, security patches will no longer be #
# provided for the following versions of Slackware (which will all #
# be more than 7 years old at that time): #
# Slackware 13.0, Slackware 13.1, Slackware 13.37. #
# If you are still running these versions you should consider #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own #
# security patches. #
####################################################################
patches/packages/patch-2.7.4-x86_64-2_slack13.0.txz: Rebuilt.
Fix arbitrary shell execution possible with obsolete ed format patches.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000156
(* Security fix *)
+--------------------------+
...
+--------------------------+
Wed Aug 26 10:00:38 CDT 2009
Slackware 13.0 x86_64 is released as stable!
Slackware 13.0, released way back in 2009, received security updates up until a year and a half ago (less than your claimed 2016). Slackware 14.0, released in 2012, is still actively receiving security updates.
Again, from where did you hear Slackware was last updated in 2016? Perhaps you misunderstood from the fact that the last stable release (14.2) was released in 2016 - but it is still actively receiving security updates.
Ever same excuse , updates today ..yes , for current , NOW THE QUESTION IS
current is for general purpose use? ..or is "testing" porpouse ?
current is solid as a rock , and ever same bla bla bla , current is not for final users.
The OP , probably referer since 14.2-stable.... 2016 ... and 2020 ...no more "stable" , release.
Its slackware dead =? ,obviously NOT , but this development cycle is more longer than others.
Say , the sky is BLUE , is not a lie , only cause some people only see clouds.
Yes, we haven't had a release for almost 4 years, but there have been patches for stable releases over this whole period of time. Many may not be aware of the changelogs and only see the "last stable release" date in Wikipedia, distrowatch, etc and question whether Slackware is alive or dead. Also, many aren't aware of -current and the constant movement that has been seen in there.
If you only pay attention to stable releases, it is reasonable to question whether Slackware is alive or dead, but if you see the changelogs, you'd realize Slackware is alive. I would say it is alive and well, but some may question the "well" portion due to the lack of a stable release for quite some time.
Gloom, despair, and agony on me.
Deep dark depression, excessive misery.
If it weren't for bad luck, I'd have no luck at all.
Gloom, despair, and agony on me.
Slackware is like the Schrödinger's cat, both alive and dead until one observes it. Then for some careful observers it is dead and for other not so careful ones it is alive.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ivandi
Slackware is like the Schrödinger's cat, both alive and dead until one observes it. Then for some careful observers it is dead and for other not so careful ones it is alive.
Cheers
Ensuite, il ya ceux qui savent que le chat Schrodingers n'existe pas et ne ses conclusions. Ivandi est le chat ?
Slackware is like the Schrödinger's cat, both alive and dead until one observes it. Then for some careful observers it is dead and for other not so careful ones it is alive.
Slackware is like the Schrödinger's cat, both alive and dead until one observes it. Then for some careful observers it is dead and for other not so careful ones it is alive.
Do you believe that PAM will finally become part of Slackware?
Slackware is like the Schrödinger's cat, both alive and dead until one observes it. Then for some careful observers it is dead and for other not so careful ones it is alive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
