From: Dale Pontius <DEPontius@edgehp.net>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Assessing the Tux Strength: Part 2 - Into the Kernel
Date: Thu, 16 Sep 2010 19:35:20 -0400 [thread overview]
Message-ID: <4C92A9B8.8000607@edgehp.net> (raw)
In-Reply-To: <201009022343.33281.radegand@o2.pl>
On 09/02/10 18:43, Radoslaw Madej wrote:
> Hi Guys,
>
> For anyone interested, I'd like to announce that the second part of my
> comparison between different Linux distros and their security features (which
> includes Gentoo Hardened of course! ;) ) can be found here:
> http://labs.mwrinfosecurity.com/notices/assessing_the_tux_strength_part_2_into_the_kernel/
>
> As always - all feedback is appreciated. Also please note that the previous
> feedback is not to be forgotten and I shall address these ((-fstack-protector
> vs. -fstack-protector-all, cookie strength and prelink) in my fourth post :)
>
> Also - congrats to Zorry for becoming the new Gentoo Hardened lead and thanks
> for all your support! :)
>
I read this today, too. Quite interesting, but it leaves me asking a
simple question...
I've been running my servers for years on hardened Gentoo, but I always
figured it would be too problematic for my deskside and laptop machines.
Is this true? Have things gotten better, and is it perfectly reasonable
to run hardened Gentoo for general purpose use?
Two problem factors... My family likes YouTube and the like, and for my
job I have to run proprietary binary-only software. (Silicon CAD tools)
Thanks,
Dale Pontius
next prev parent reply other threads:[~2010-09-16 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 22:43 [gentoo-hardened] Assessing the Tux Strength: Part 2 - Into the Kernel Radoslaw Madej
2010-09-03 9:56 ` Daniel Kuehn
2010-09-07 22:27 ` pageexec
2010-09-08 15:19 ` radegand
2010-09-16 23:35 ` Dale Pontius [this message]
2010-09-17 0:04 ` "Tóth Attila"
2010-09-17 18:50 ` Radoslaw Madej
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=4C92A9B8.8000607@edgehp.net \
--to=depontius@edgehp.net \
--cc=gentoo-hardened@lists.gentoo.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