From: Jason Czerak <Jason-Czerak@Jasnik.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Suggestions for linux security patches
Date: 19 Dec 2001 16:44:03 -0500 [thread overview]
Message-ID: <1008798243.6214.2.camel@neworder> (raw)
In-Reply-To: <1008794926.842.6.camel@neworder>
In-Reply-To: <1008794926.842.6.camel@neworder>
On Wed, 2001-12-19 at 15:48, Jason Czerak wrote:
> I'm running linux 2.4.16, and I"m looking to the best possibly kernel
> patch to harden things up a bit. Primarly I wish to have what is in
> openwall's and grsecurity's patches is the buffer oveflow protection,
> but I'm unable to use the openwall patch because it only support 2.2.X
> kernels ATM. I applied the grsecurity patch but for some reason when
> running mozilla as non-root, the GUI for mozilla is all messed up (and
I
> enabled sysctl support so nothing was enabled by default except stuff
> that isn't able to use sysctl).
>
> So to advoid applying 20 or so differnet patches, and evaluate each of
> them (taking up what little time I have in a day...), I wish to get
the
> lists opinions on the matter.
>
Ok, so 20 or so was a little off base. :) it's more like 3 packages that
are for my type of system and that appear to be activtly developed
1: SeLinux
2. Grsecurity
3. Lids
Lids, and grsecurity appear to be highly configureable and grsecurity
isn't playing nice with some applictions on my system. I'll be testing
out SeLinux and Lids tomarrow, but as one list memeber emailed me
ealier, LIDS has over 500 differnent options, That right there maybe a
turn off for sake of sanity right now. :)
--
Jason Czerak
next prev parent reply other threads:[~2001-12-19 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 20:48 Suggestions for linux security patches Jason Czerak
2001-12-19 21:28 ` Tomas Konir
2001-12-19 21:44 ` Jason Czerak [this message]
2001-12-19 23:50 ` Chris Wright
2001-12-20 5:19 ` Kevin
2001-12-21 11:07 ` Tracy R Reed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1008798243.6214.2.camel@neworder \
--to=jason-czerak@jasnik.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox