public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Jason Czerak <Jason-Czerak@Jasnik.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suggestions for linux security patches
Date: Wed, 19 Dec 2001 15:50:20 -0800	[thread overview]
Message-ID: <20011219155020.A4424@figure1.int.wirex.com> (raw)
In-Reply-To: <1008794926.842.6.camel@neworder>
In-Reply-To: <1008794926.842.6.camel@neworder>; from Jason-Czerak@Jasnik.net on Wed, Dec 19, 2001 at 03:48:46PM -0500

* Jason Czerak (Jason-Czerak@Jasnik.net) wrote:
> 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.

have you looked at linux security modules?  the patches are at
http://lsm.immunix.org.  it pushes security policy into modules so you can
try different modules to see which policy you prefer.

> Local security/control isn't much of an issue and most likly won't be
> for a while. Remote security and protection from server deamons that
> have buffer problems are high priority to get the best protection for. 

note, non-executable stack does not prevent buffer overflow attacks.
the exploit just needs to change.  check out tools like libsafe and
StackGuard as well for buffer overflow protection.

thanks,
-chris

  parent reply	other threads:[~2001-12-19 23:51 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
2001-12-19 23:50 ` Chris Wright [this message]
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=20011219155020.A4424@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=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