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.
Just a reminder that the '/usr/share/pci.ids' file is probably dated for your system. You can get '/usr/share/pci.ids' that should be current. No harm but to update this will aid you in understanding newer devices that are not identified but output as 'unknown device'. Not everyone memorizes their 'pci:id' so update that '/usr/share/pci.ids'.
I posted 'Slackware '-current' '/usr/share/pci.ids' file is dated' to prepare anyone for the new release and thinking the system was at fault. You will need to update '/usr/share/pci.ids' to rid the 'unknown device' errors. No harm, just a aid.
Last edited by onebuck; 03-09-2010 at 08:11 AM.
Reason: correct link
Click here to see the post LQ members have rated as the most helpful post in this thread.
I'd expect a fixed package to be included in Slackware very shortly, so this warning will not have a very long shelf life. By the time most people read this it will most likely be patched.
However, I would strongly encourage any Slackers who are interested in system security to subscribe to the following two threads over in the LQSEC forum:
Security is on everyone's mind now a days or at least it should be.
'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.
Mon Apr 5 03:06:19 UTC 2010
kde/k3b-1.91.0-x86_64-1.txz: Upgraded.
l/libjpeg-v8a-x86_64-1.txz: Upgraded.
l/seamonkey-solibs-2.0.4-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-3.6.3-x86_64-1.txz: Upgraded.
This fixes some security issues.
For more information, see: http://www.mozilla.org/security/know...firefox36.html
(* Security fix *)
xap/mozilla-thunderbird-3.0.4-x86_64-1.txz: Upgraded.
This upgrade fixes some more security bugs.
For more information, see: http://www.mozilla.org/security/know...derbird30.html
(* Security fix *)
xap/seamonkey-2.0.4-x86_64-1.txz: Upgraded.
This release fixes some more security vulnerabilities.
For more information, see: http://www.mozilla.org/security/know...amonkey20.html
(* Security fix *)
Some security fixes for mozilla apps. Please be sure to use a mirror, plus let things get updated as it does take some time to settle;
If you need some casual reading then look at the 'Linux Books & Online Magazines' section of 'Slackware-Links'. Loads of FREE online books and magazines to enhance your relationship with other LQ members.
Tue Apr 20 14:45:24 UTC 2010
a/kernel-firmware-2.6.33.2-noarch-1.txz: Upgraded.
a/kernel-generic-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-generic-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
a/kernel-huge-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-huge-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
a/kernel-modules-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-modules-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
ap/mpg123-1.12.1-i486-1.txz: Upgraded.
ap/mysql-5.1.45-i486-1.txz: Upgraded.
ap/nano-2.2.4-i486-1.txz: Upgraded.
ap/sudo-1.7.2p6-i486-1.txz: Upgraded.
This update fixes security issues that may give a user with permission
to run sudoedit the ability to run arbitrary commands.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-0426 http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-1163 http://www.gratisoft.us/sudo/alerts/..._escalate.html http://www.gratisoft.us/sudo/alerts/...escalate2.html
(* Security fix *)
d/cmake-2.8.1-i486-1.txz: Upgraded.
d/git-1.7.0.5-i486-1.txz: Upgraded.
d/kernel-headers-2.6.33.2_smp-x86-1.txz: Upgraded.
e/emacs-23.1-i486-3.txz: Rebuilt.
Fixed a broken icon and updated to the upstream .desktop file.
k/kernel-source-2.6.33.2_smp-noarch-1.txz: Upgraded.
kde/amarok-2.3.0-i486-1.txz: Upgraded.
kde/kdebase-workspace-4.3.5-i486-2.txz: Rebuilt.
Patched a security issue with KDM.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-0436
(* Security fix *)
kde/koffice-2.1.2-i486-1.txz: Upgraded.
kdei/koffice-l10n-*: Upgraded.
l/lesstif-0.95.2-i486-1.txz: Upgraded.
l/libmtp-1.0.1-i486-1.txz: Upgraded.
l/loudmouth-1.4.3-i486-1.txz: Added.
This is a Jabber library used by Amarok's mp3tunes service.
Thanks to Eric Hameleers.
l/taglib-1.6.2-i486-1.txz: Upgraded.
n/gnutls-2.8.6-i486-1.txz: Upgraded.
extra/linux-2.6.33.2-nosmp-sdk/*: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
excerpt 'CVE-2010-0426';
sudo 1.6.x before 1.6.9p21 and 1.7.x before 1.7.2p4, when a pseudo-command is enabled, permits a match between the name of the pseudo-command and the name of an executable file in an arbitrary directory, which allows local users to gain privileges via a crafted executable file, as demonstrated by a file named sudoedit in a user's home directory.
Details:
When sudo performs its command matching, there is a special case for pseudo-commands in the sudoers file (currently, the only pseudo-command is sudoedit). Unlike a regular command, pseudo-commands do not begin with a slash ('/'). The flaw is that sudo's the matching code would only check against the list of pseudo-commands if the user-specified command also contained no slashes. As a result, if the user ran "sudo ./sudoedit" the normal matching code path was followed, which uses stat(2) to verify that the user-specified command matches the one in sudoers. In this case, it would compare the "./sudoedit" specified by the user with "sudoedit" from the sudoers file, resulting in a positive match.
Impact:
Exploitation of the bug requires that the sudoers file be configured to allow the attacker to run sudoedit. If no users have been granted access to sudoedit there is no impact. Successful exploitation of the bug will allow a user to run arbitrary commands for whichever user they have permission to run sudoedit as, typically root.
Race condition in backend/ctrl.c in KDM in KDE Software Compilation (SC) 2.2.0 through 4.4.2 allows local users to change the permissions of arbitrary files, and consequently gain privileges, by blocking the removal of a certain directory that contains a control socket, related to improper interaction with ksm.
'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.
excerpt form 'changelog';
Thu May 6 21:02:02 UTC 2010
Hi folks! We have some pretty big changes today, with an update to the latest
KDE SC 4.4.3, and the addition of support for ConsoleKit and PolicyKit which
have been enhanced to use shadow authentication. Thanks to Andrew Psaltis for
doing some great work on polkit-1, and to Robby Workman for spending months
following the sometimes random developments coming from the CK/PK camp. :-)
Thanks to Eric Hameleers for leading the KDE 4.4.x Slackware development and
handling the out-of-tree testing through http://alien.slackbook.org/blog/.
And with that, we're calling this Slackware 13.1 BETA1. A stable release
should be just around the corner...
Please remember that when the stable becomes available to use a 'mirror'. Check out the Get Slackware section of 'Slackware-Links under 'Slackware® Mirrors:' or for you point & clickers;
For the new user to get '-current' or this 'Slackware 13.1 BETA1' I suggest that you use Alien_Bob's-script-mirror-slackware-current.sh. To download -current, create cdrom/dvd Or Alien_Bob's-script -mirror-slackware-current.sh : UK backup of script script to download the '-current' of choice ( 'x86' meaning 32bit or 'x86_64' meaning 64bit). You can either pass parameters or edit the script to create the 'ISO' medium of choice. Plus be sure to select a mirror of choice to use. The script is well documented to allow you choices. Alien_Bob is a Slackware® contributor and has graciously provided the scripts/tools.
So an ata-boy and a big Thank You to PV, Alien_Bob, Robby and Team. Plus I want to extend my personal thanks to the LQ Slackware forum members.
The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!
I've noticed a problem for some new users that are attempting to use 'Slackware 13.1 BETA1'.
'libata_switchover' has been around since 13.0 but some new users are not aware.
A new user should look at rworkman's 'libata_switchover HOWTO';
Quote:
excerpt 'libata_switchover HOWTO';
This is written to provide one of several ways to retain a working
system after upgrading from Slackware 13.0's kernel to the newer
kernel in -current (which removes support for the "old" ide subsytem,
thereby causing all /dev/hd* devices to have /dev/sd* names.
One thing that I believe everyone should read is the 'CURRENT.WARNING' as it pertains to '-current' & 'Slackware 13.1 BETA1' is '-current'.
Code:
'CURRENT.WARNING';
[Standard disclaimer follows... ]
Welcome to Slackware-current! (x86_64)
*** Please note that you must already be ***
*** running a 2.6.x kernel before ***
*** upgrading to Slackware-current! ***
*** ***
*** upgradepkg glibc-solibs before other ***
*** packages. Take care not to miss new ***
*** packages that were split from old ***
*** ones: upgradepkg --install-new is ***
*** (as always) the safest approach. ***
Slackware-current is a snapshot of the active Slackware development tree.
It is intended to give developers (and other Linux gurus) a chance to test
out the latest packages for Slackware. The feedback we get will allow us
to make the next stable release better than ever.
See the ChangeLog.txt for a list of changes in Slackware-current.
Please note that the code in this directory is unstable. It might be
inconsistent about which version of the Linux kernel is required, could be
incomplete because it's in the process of being uploaded, or might not work
for other reasons. In most cases, we know about these things and are working
to correct them, but still -- feel free to point out the bugs.
Production use is AT YOUR OWN RISK and is not recommended.
Security is NOT GUARANTEED. In -current, forward progress often takes
priority. Security fixes take time and resources, and would often have to
be done more than once. It's more efficient to build the system and secure
it as time permits and/or the development cycle nears completion.
We do not promise to issue security advisories for Slackware-current.
Slackware-current might DELETE FILES WITHOUT WARNING when packages are
upgraded. (If, for example, a directory location is replaced by a symbolic
link to a new location.) Upgrade packages carefully. Examine incoming
updates first if your machine's data is not expendable. Again, we do not
recommend using Slackware-current to store or process valuable data.
It is a system in testing, not one that is ready to go (though often it does
work just fine... BUT DON'T COUNT ON IT)
#include BSD license warranty disclaimer here...
Enjoy! :)
---
Patrick J. Volkerding
volkerdi@slackware.com
Plus other text files should be read as there are hidden treasures of information that may keep you from .
excerpt ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt
Wed May 19 08:58:23 UTC 2010
Slackware 13.1 x86 stable is released!
Lots of thanks are due -- see the RELEASE_NOTES and the rest of the
ChangeLog for credits. The ISOs are on their way to replication,
a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD.
We are taking pre-orders now at store.slackware.com, and offering
a discount if you sign up for a subscription. Consider picking up
a copy to help support the project. Thanks again to the Slackware
community for testing, contributing, and generally holding us to a
high level of quality. :-)
Enjoy!
Please note that you only need CD1,2 & 3 for a full install of Slackware x86.
The dust is settling for this wonderful release. Forum activity is minimal for this release other than praise.
BUT: Once You get the ISO downloaded then you should do a md5sum check on the downloaded ISO(s) image(s) to keep from having a stack of coasters. This can be done using a M$ Windows application such as 'md5sum.exe' to check the md5sum. Or for Linux from the cli you would do;
Code:
~#cd /downloadisolocation #cdromiso.iso cdromiso.md5
~#md5sum -c cdromiso.md5 #substitute the correct name to check
Once you are sure that everything is OK then you can burn the 'ISO IMAGE' to your selected media. Please note that some users must burn the ISO image at a slower speed to insure a good burn. By slowing the burn speed you may insure that a good copy will be created if the image is indeed valid.
Once the image has been burned to the media then a 'CdromMd5sumsAfterBurning' check would be advised. Your burn application can fail so a check of the final media would prevent you from some possible headaches.
After you have the new release ready to install then you should read for understanding and revelation to help in having no stumbling blocks or gotcha(s);
I also suggest that you look at 'How to Ask Questions the Smart Way' so that in the future your thread queries provide information which will aid us in diagnosis of the problem from a good formed question(s).
Alphageek’s “sligdo files” are a very fast way of creating byte-exact copies of the official ISOs in case you already have a local mirror-copy of the full Slackware 13.1 tree. The ISOs you create with sligdo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
