From: atoth@atoth.sote.hu
To: linux-kernel@vger.kernel.org
Subject: Re: Grsecurity is about to be discontinued...
Date: Sun, 4 Jan 2009 18:34:24 +0100 (CET) [thread overview]
Message-ID: <213db97b75b3c08d1a7f9af580563b86.squirrel@atoth.sote.hu> (raw)
In Reply to Linus Torvalds on Grsecurity:
These days people out there are running closed-source adobe flash plugin
to browse pages like ebay.com where one can come across some applets
causing execution attempts daily. It can be detected using improved
techniques only.
I don't care about what code will run on many noobs' machine, but I'd like
to stay secure. So even if it seems insane, it surely makes sense -
unfortunately.
I suspect some of the most important improvements are labeled "annoying"
by Linus. However some other operating system's board chose to include
parts of such implementations (I won't list them here). It would be good
to see as many snippets of PaX/Grsec in the mainline as possible. Please
take this message as a sign, that Gabor Micsko (trey@hup.hu) is not alone
with his idea.
Grsecurity proved itself as a viable, valuable solution for combined
techniques for hardening Linux. I'm using a laptop which has every
application running regulated by Grsecurity's RBAC system - including
_all_ GUI apps. Please warn me, when there will be some security policies
available to convert a targeted SELinux machine into a fully hardened
SELinux box with GUI.
I'm not sure, that putting Grsecurity in the mainline would save the
project. I rather hope, that some companies using the software will give a
helping hand to the developers. However the Linux community should turn
its attention to defensive security solutions, IMHO. As it gets more and
more abundant, there will be more exploits floating around. Some lessons
can be learned from those "monkeys" on how to think secure.
A polished full-featured security system can raise Linux above other
solutions. The better if there are more possibilities to choose between.
All features of PaX and Grsecurity can be disabled by default: so an
ordinary user shouldn't worry about being secure.
Please consider to think about how secure is your on system and what can
be done to fix it. If some focused persons provide a specialized solution
it worth to be investigated.
Regards,
Dwokfur
--
dr Tóth Attila, Radiológus
Attila Toth MD, Radiologist
next reply other threads:[~2009-01-04 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 17:34 atoth [this message]
2009-01-04 19:38 ` Robert Hancock
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=213db97b75b3c08d1a7f9af580563b86.squirrel@atoth.sote.hu \
--to=atoth@atoth.sote.hu \
--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
all inboxes | Powered by JetHome®