From: anlar@hellfish.org
To: linux-kernel@vger.kernel.org
Subject: Future of the security features
Date: Sun, 12 Oct 2003 23:26:35 +0300 [thread overview]
Message-ID: <1065990395.3f89b8fb73015@mail.hellfish.org> (raw)
I have been playing with the Grsecurity (www.grsecurity.org) patches now for a
while and I wouldn't run a server anymore without it. I noticed from the kernel
list archives that the inclusion of features like Pax have been discussed
before and as I have understood, this might be a good time to try to get the
matter hot again.
There are a lot of nice security improving patches for the kernel. Pax against
many of the overflows in software for instance could be one nice day saving
feature. Making such features upstream would not cure the situation alone. I
believe though that it would help generally in making our computing safer.
Just take a look at all the small tweaks and improvements that are available
for
instance in Grsecurity. Whoa. Not bad. Would break some (poorly designed
mostly) software though if forced on. (The only really problematic in my
experience has been the Xfree86 server but even it can be fixed afaik to run
with all the Grsecurity patches.)
The Linux kernel could be tweaked to be one nasty animal (can penguins be
nasty?) guarding the security. Linux based systems could be a lot more secure
with "some light tweaking" and now it is mostly up to the kernel developers.
So, why not?
To remind you, even Windowses are going that way. Including that kind of
features. (No, not yet available. They just recompiled some of their software
with stack protection stuff that is on the newest compilers of theirs.) You
don't want the Linux to be laughed at. :) Heh.
next reply other threads:[~2003-10-12 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 20:26 anlar [this message]
2003-10-13 0:37 ` Future of the security features Rik van Riel
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=1065990395.3f89b8fb73015@mail.hellfish.org \
--to=anlar@hellfish.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.