Re: Debian Server restored after Compromise. Which kernels???
> > Why not try compiling your own kernel?
> > make-kpkg makes it quite simple for us non developer types.
> > All you need to do is install kernel-package, and perhaps gcc, make, g++
> > they don't already come down with kernel-package.
> > /usr/share/doc/kernel-package has the readme that shows you how to
> > your own .deb.
> Yes, it can be done. Two points:
> 1) I've lost mail from Leopold ... If I remember correctly, the
> vulnerable kernels were up to 126.96.36.199. Should 188.8.131.52 be needed?
> I've not heard about this.
I believe from debian.org's newsletter, it is kernel's less than
184.108.40.206, therefore 220.127.116.11 and lower.
Also, kernel.org changelog for 18.104.22.168 talks about fixing the local exploit.
> 2) It has often been told on this list that kernel packages provided
> by Debian cover most needs, implying that going to compile kernels
> is a waste of resources in most cases.
Perhaps, but since we're living in the world of debian non-stable kernels,
(because our hardware is too new), then we must find fixes or patches for
security exploits. If we can't find such a debian .deb immediately,
I'm happy to make my own. Of course, 90% of the time I wait for a .deb to