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.
Where do I put the nox32recvmmsg module, so that it's loaded permanently (survives reboot, etc) in /lib/modules/3.10.17? Which subdirectory?
EDIT
Doesn't seem to work.
Module loaded:
Code:
bash-4.2$ lsmod
Module Size Used by
nox32recvmmsg 1201 1
Ran .poc:
Code:
bash-4.2$ ./slack64-14.1_CVE-2014-0038_poc
13 minutes to root
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ praise bob!
The Golden Rule is of no use to you whatever unless you realize it
is your move.
-- Frank Crane
root@slackdesk:~/temp#
I think I've done everything right, the module is loaded, but I'm still getting:
Code:
bash-4.2$ cd temp
bash-4.2$ ./slack64-14.1_CVE-2014-0038_poc
13 minutes to root
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ praise bob!
If you can't say anything good about someone, sit right here by me.
-- Alice Roosevelt Longworth
root@slackdesk:~/temp#
Mozilla various
Firefox 27 (for current)
Firefox ESR 24.3
Thunderbird 24.3
Seamonkey 2.24
I was thinking that when one or more vulns hit the mozilla suite, to build the three on 12 different Slackware versions (13.0, 13.1, 13.37, 14.0, 14.1 and current, for i486 and x86_64) it's surely time-consuming...
I was thinking that when one or more vulns hit the mozilla suite, to build the three on 12 different Slackware versions (13.0, 13.1, 13.37, 14.0, 14.1 and current, for i486 and x86_64) it's surely time-consuming...
Surely serves as a good RAM/CPU stress tester. The good news for Pat is I think he's only updating FF and Tbird for 14.1+current and
Seamonkey for 14.0+14.1+current (right?).
I apologize if this is slightly off topic and/or has been asked before, but is there a risk with running the 3.10.17 kernel when the latest upstream longterm release is 3.10.28? Are most of the fixes simply bug fixes or do the kernel security patches not really affect Slackware?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.