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 Code:
bash-4.2$ ./slack64-14.1_CVE-2014-0038_poc |
Quote:
Code:
# mkdir -p /lib/modules/$(uname -r)/misc Code:
# echo "/sbin/modprobe nox32recvmmsg" >> /etc/rc.d/rc.local Quote:
To be protected you must load the module on an untainted kernel. Reboot, insmod, and you should be OK. If that doesn't work let me know. --mancha |
Thanks, mancha. I'll do all you suggest.
|
It looks like it does work, because you are root at the bottom, by the # sign.
|
Quote:
|
I think I've done everything right, the module is loaded, but I'm still getting:
Code:
bash-4.2$ cd temp |
OK, I think I know what is going on. Is there an "unable to handle kernel paging request" after the module is loaded (check /var/log/syslog).
If this is the case, I have uploaded a new module that accounts for protected-mode CPUs. Please download and try it (note: it might take a minute or two to propagate to the SF servers). Check against hash below. SHA256(nox32recvmmsg.tar.bz2)= 8c822d55a0a45f0fa994c73921701e2bb035bdaeb169c2355ed8d767414c4f73 --mancha |
No, there's nothing in /var/log/syslog. I'll try the new module after I've eaten (never load modules on an empty stomach. :) ).
|
Yes!!! The new module works:
Code:
bash-4.2$ cd temp |
Quote:
--mancha |
Update 20140205
|
Quote:
|
Quote:
Seamonkey for 14.0+14.1+current (right?). --mancha |
Got FF 27.0 using ruario's latest-firefox script.
|
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?
|
All times are GMT -5. The time now is 12:04 AM. |