public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rumen Yotov <rumen_yotov@dir.bg>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Considering dropping the hardened toolchain (A Quantitive Approach)
Date: Sat, 18 Sep 2004 20:27:21 +0300	[thread overview]
Message-ID: <1095528440.5931.22.camel@mymach.qrypto.org> (raw)
In-Reply-To: <414C69DD.1080901@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

On сб, 2004-09-18 at 20:01, Thierry Carrez wrote:
> Alexander Gabert wrote:
> 
> > But, in my eyes, you are underestimating the negative impact of that
> > decision on people
> > successfully using the solution.
> > 
> > Do you need success stories for letting it continue?
> > Do you need mails of people that tell you: good job, things broke left and
> > right of me, but i am a proud owner of a hardened gcc.
> > 
> > You and me know that you will never get such mails.
> 
> It works, it's great, it never failed for me, and I think it's a great
> asset to have in a metadistribution environment like Gentoo.
> 
> Maybe there is a problem of scope. It's probably too much work to have
> it work/documented for the default user to use on a general-purpose
> workstation, where xfree/mplayer/whatever will break or where the user
> won't read the F manual. Maybe the scope should be server/router
> environments only, so that the number of packages to check and support
> would be more reasonable and the user level would be higher...
Hi All,
i've been using hardened platform for about a year. Firstly through
CFLAGS in make.conf, later by using hardened toolchain.
It's not a server, something special just my only home computer, i use
it for everything - including music, video etc.
Quite always there is a price u have to pay to use some things. Example
is that i used Xorg compiled static to get X on my desktop. Didn't have
3-D accel. but it worked, and whats more i was using full PaX-protection
+ grsec2 and hardened GCC.
Don't know about the others but i have maybe no more then 10 bugs for a
month, more or less (rarely due to using hardened). Frankly sometimes
ever forget that i'm using a hardened system.
It's true for some time there are more and longer standing (nasty
hardened) bugs, but hope later there will be less, the life isn't always
nice.
PS: about the help needed, sorry for the moment can't help (no asm
experience, nor ELF-binaries knowledge etc). Maybe some documentation or
testing, don't know.
Truly think hardened is a great thing in Gentoo and it works, just see
all major hardened projects (grsec2, RSBAC, SElinux) are here.
Just my experience and point of view.
Thanks
Rumen


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-18 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18  6:10 [gentoo-dev] Considering dropping the hardened toolchain Ned Ludd
2004-09-18 15:54 ` [gentoo-dev] Considering dropping the hardened toolchain (A Quantitive Approach) Alexander Gabert
2004-09-18 17:01   ` Thierry Carrez
2004-09-18 17:27     ` Rumen Yotov [this message]
2004-09-18 18:27   ` Ned Ludd
2004-09-19  2:06     ` Thomas Zimmerman
2004-09-19  5:16       ` Allen Parker
2004-09-19  5:41         ` Ned Ludd
2004-09-19 22:16     ` Lars Weiler

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=1095528440.5931.22.camel@mymach.qrypto.org \
    --to=rumen_yotov@dir.bg \
    --cc=gentoo-dev@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