Re: kernels exploitable
"Ryan P.C. McQuen" <[email protected]> Tue, 23 Jun 2015 07:17:44 -0700
| Newsgroups | gmane.linux.slackware |
|---|---|
| Message-ID | <CAAcyf-p16=oH_p0cCSk+PrWqWXi92T461QYupSpnS0r+phDZzg@mail.gmail.com> |
>Does slackware not update kernels in its distros anymore, myriad of bugs fixed in 3.2 and we are still on 3.2.9 when its actually at 3.2.69 - Id hate to think of how rootable these 14.0 pc's are. Actually, 14.0 is on 3.2.45, with some backports from 3.2.46, check here: http://mirrors3.kernel.org/slackware/slackware-14.0/ChangeLog.txt And originally 3.2.29 was shipped, not 3.2.9. I have a script that will compile a new kernel and add it to LILO. It prompts you to choose the latest mainline/stable/longterm kernel, or you can feed it a version number like: cd /usr/src/ sh kernelMe.sh 3.14.45 It will also accept a kernel config, or just grab the running config. To pass it a kernel config (such as one downloaded from slackware-current), do: wget http://mirrors.slackware.com/slackware/slackware64-current/source/k/config-x86_64/config-huge-3.18.11.x64 -P /usr/src/ KERNELCONFIG=/usr/src/config-huge-3.18.11.x64 sh kernelMe.sh You can grab it here: https://github.com/ryanpcmcquen/linuxTweaks/blob/master/slackware/kernelMe.sh Good luck. On 6/23/15, Didier Spaier <[email protected]> wrote: > On 23/06/2015 13:35, eleksir wrote >> <offtopic mode on> >> Slackware have kernel-like team management but team itself is not that >> large. And due to very conservative approach to system design and idea >> that software should be as vanilla as possible, and whole distribution >> _must_ be as simple as it really can be - there not too much maintainers >> that support older releases of Slackware. >> >> Thinking of tendency that complexity of software increases with >> development process progressing, Slackware maintainers should think of >> increasing of amount of active team members. But this is separate topic >> to discuss :) >> <offtopic mode off> > > Increasing amount of active team members? Theoretically possible but > unlikely, says my crystal ball. What Eric wrote in this paper[1] nearly > 6 years ago still mostly stands, I think. And confirms what Alan said. > > Cheers, Didier > > [1]http://www.slackware.com/~alien/tdose2009/t-dose-slackware.pdf > > > > _______________________________________________ > slackware mailing list > [email protected] > https://mailman.lug.org.uk/mailman/listinfo/slackware > -- --- <ryanpcmcquen.com>