From: "Javier Juan Martínez Cabezón" <tazok.id0@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] binary protection mechanisms in different Linux distros
Date: Thu, 1 Jul 2010 10:16:17 +0200 [thread overview]
Message-ID: <AANLkTimMf2IPQIiQr-zaHguP_7ix36SpL61Nh6ZLO-AH@mail.gmail.com> (raw)
In-Reply-To: <201007010846.11482.radegand@o2.pl>
Hi, I think it's a bad day to make comparisons with hardened gentoo.
Hardened gentoo traditionally doesn't use only -fstack-protector as
ubuntu does and some others, it use -fstack-protector-all in
everywhere it could. It's an important difference. I think that the
actually ssp bug in the last version isn't representative of what
hardened gentoo does (it's a bug, an exception). It has always shipped
-fstack-protector-all everywhere.
2010/7/1 Radoslaw Madej <radegand@o2.pl>
>
> Hi guys,
>
> I convinced the company I work for to allow me to spend some time on reviewing
> different security aspects of Linux OS and different distros. As it also
> involves Gentoo Hardened (which I also happily use on a daily basis), I
> thought I'd share. :)
>
> http://labs.mwrinfosecurity.com/projectdetail.php?project=13&view=news
>
> There should be more to come in a near future. Any feedback appreciated :)
>
> Thanks to all hardened-dev for making the Hardened Gentoo happen! :)
> Regards,
> Radek Madej
>
next prev parent reply other threads:[~2010-07-01 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 7:46 [gentoo-hardened] binary protection mechanisms in different Linux distros Radoslaw Madej
2010-07-01 8:10 ` Daniel Kuehn
2010-07-01 8:16 ` Javier Juan Martínez Cabezón [this message]
2010-07-01 21:05 ` Radoslaw Madej
2010-07-01 21:08 ` Kyle Bader
2010-07-01 21:09 ` Kyle Bader
2010-07-01 23:12 ` Radoslaw Madej
2010-07-02 0:07 ` Matthew Thode
2010-07-02 0:13 ` Matthew Thode
2010-07-02 5:58 ` Javier Juan Martínez Cabezón
[not found] ` <20100702074146.GG28068@felinemenace.org>
2010-07-02 21:31 ` 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=AANLkTimMf2IPQIiQr-zaHguP_7ix36SpL61Nh6ZLO-AH@mail.gmail.com \
--to=tazok.id0@gmail.com \
--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