From: Ned Ludd <solar@gentoo.org>
To: Allen Parker <infowolfe@gmail.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Considering dropping the hardened toolchain (A Quantitive Approach)
Date: Sun, 19 Sep 2004 01:41:00 -0400 [thread overview]
Message-ID: <1095572460.26130.2187.camel@simple> (raw)
In-Reply-To: <9f279016040918221659d98b1f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2400 bytes --]
On Sun, 2004-09-19 at 01:16, Allen Parker wrote:
> Hey Ned, solar, hardened folks...
>
> I've got a couple of pennies to throw into this mix:
> Even though my own participation (due to work schedules - 3 jobs
> doesn't leave a whole lot of time for other stuff) has waned, I
> believe that your hardened toolchain is top-notch. Yes, it's bleeding
> edge, it's not mature, etc... that doesn't mean we should have a
> partial-birth abortion. Hardened has been around for a while, yes, but
> if you spend 10 minutes in #gentoo you'll see, a LOT of our users
> aren't prepared for something as in-depth as hardened.
>
> Gentoo currently LEADS linux distributions in configurability in
> regards to hardened/selinux/security. Bar NONE! For the experienced,
> hardened *can't* be replaced by anything out there. If I had the skill
> level to assist in any way, I'd be the first guy in line to help.
> Unfortunately, my experience is more limited to finding
> non-programming solutions to get the job, whatever that job may be,
> done. Perhaps this thread will catch someone's eye, someone that CAN
> help, at least drum up some user support.
>
> Solar, before reading your email, I had no idea that you were feeling
> like that. Maybe we can get someone with a *little* more experience
> than me, perhaps a trusted user/non-dev that can be a bug-filter?
>
> To the hardened community: If you can afford the time, check
> bugs.gentoo.org for hardened bugs... if there are bugs that you know
> of that are FUD, email a list of bug #'s to your favorite hardened
> dev, after replying with a solution to the particular user, whether or
> not it's a PEBKAC issue or not.
>
> that's all for me, gotta head back to work *sigh*
Don't panic yet..
So far I have been getting good feedback from some users and atleast one
potential developer in some mails off list. I plan to put a detailed
mail together in as few days and mail the interested parties and
hopefully assemble a larger more professional team so we can fully
continue to offer these types of technologies and continue to push fwd
together.
>
> Allen Parker
> infowolfe@irc.freenode.net (when i'm online) #/tmp #gentoo-hardened #gentoo-dev.
>
> --
> gentoo-dev@gentoo.org mailing list
--
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-19 5:41 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
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 [this message]
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=1095572460.26130.2187.camel@simple \
--to=solar@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=infowolfe@gmail.com \
/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