[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: is kernel 2.0.38 broken?



there is a locally exploitable command that will cause 2.0.36 and .38
(probably others too) to crash, usign ping -R i believe ..see bugtraq for
details

nate

On Sun, 26 Dec 1999, Pollywog wrote:

pollyw >I thought I read on this list that there was a problem with the last 2.0.x
pollyw >kernel.  Is that true?  I still have Slink on my laptop, so I am not ready for
pollyw >a 2.2.x kernel and I am using 2.0.36.
pollyw >
pollyw >thanks
pollyw >
pollyw >--
pollyw >Andrew
pollyw >
pollyw >-----------------------------
pollyw >GnuPG Public KeyID: 0x48109681
pollyw >*we all live downstream*
pollyw >
pollyw >
pollyw >-- 
pollyw >Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
pollyw >

----------------------------------------[mailto:aphro@aphroland.org ]--
   Vice President Network Operations       http://www.firetrail.com/
  Firetrail Internet Services Limited      http://www.aphroland.org/
       Everett, WA 425-348-7336            http://www.linuxpowered.net/
            Powered By:                    http://comedy.aphroland.org/
    Debian 2.1 Linux 2.0.36 SMP            http://yahoo.aphroland.org/
-----------------------------------------[mailto:aphro@netquest.net ]--
6:37pm up 129 days, 6:30, 2 users, load average: 1.77, 1.64, 1.53


Reply to: