Re: Secure 2.4.x kernel
Since we're on the 2.4 kernel, I have a question thats been
jawing at me and haven't really had the time to peel through
code and look...
In the kernel (ok, stand up you kernel guru's!), when a
"segmentation fault" is raised, I don't care where, doesn't the
kernel get some sort of notification event?
For example, say my process (inetd or exim) does a core
dump, doesn't the kernel get some sort of event that this
occurred and what address/offset it occurred at? Or since
the process is outside of the "kernel", it doesn't know?
Gary
----- Original Message -----
From: "Phillip Hofmeister" <plhofmei@svsu.edu>
To: <jorel@austin.rr.com>
Cc: <debian-security@lists.debian.org>
Sent: Friday, December 21, 2001 8:28 AM
Subject: Re: Secure 2.4.x kernel
>
>
> Or is it the
> > case that such a secure kernel doesnt exist yet in the
> 2.4 line? Given
> > Debian's tradition of backporting security fixes, perhaps
> there is a
> > Debian-ized 2.4 kernel that would be suited to what I
> have in mind?
>
> I run 2.2.18pre21 on my firewall. It has been known to be
> stable and secure. Unless you like recompiling your kernel
> 2 or 3 times a month I wouldn't look to 2.4 for a FIREWALL
> kernel yet. If you want the neat features of 2.4 I would
> recomend installing 2.2 on the firewall and another box on
> the internal network with 2.4
>
> Phil
>
> >
> > Thanks,
> > Jor-el
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-security-
> request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
> >
>
>
>
> --
> To UNSUBSCRIBE, email to debian-security-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
Reply to: