From: radegand <radegand@o2.pl>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Assessing the Tux Strength: Part 2 - Into the Kernel
Date: Wed, 08 Sep 2010 17:19:51 +0200 [thread overview]
Message-ID: <6749d1ff.717bd429.4c87a997.ee5fa@o2.pl> (raw)
In-Reply-To: <4C86BC3E.31174.D0D10BE@pageexec.freemail.hu>
Hi,
Thanks for your feedback.
Dnia 8 września 2010 0:27 pageexec@freemail.hu napisał(a):
>
> > On 3 Sep 2010 at 11:56, Daniel Kuehn wrote:
>
> > The randomisation bit was particularily interesting because as far as I
> > understand that is one of the better security measures we can use.
>
> actually, if you ask me, ASLR is the least useful security feature :P. it's not
> even really security, it's mere obfuscation, and it's great when it's works but
> it'll never provide guarantees (which is what we prefer in security).
I'd agree. Nevertheless, IMHO, even if no guarantees can be given, ASLR when done correctly (and together with PIE) makes exploitation way harder and is reasonably (?) easy to implement and maintain. Why making attacker's life easier? ;)
>
> > Shame on fedora for only 3-bits randomisation for shared libs :P
>
> a note here: fedora uses exec-shield which maps libraries in two different
> regions: ascii-armor (lower 16MB) and the rest. i think what paxtest measured
> there is the former where the usable entropy is necessarily less than elsewhere
> and may not be representative of real life apps and their address spaces (not
> saying the whole ascii-armor region is worth anything for security though ;).
Seems like I need to find out more about exec-shield then... :)
>
> PS: when discussing null deref protections, it's worth mentioning UDEREF which
> is a tad bit more general and useful than mmap_min_addr ;).
>
Oopps, yep, I totally missed UDEREF, my bad...!
Regards,
Radek
next prev parent reply other threads:[~2010-09-08 16:02 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 [this message]
2010-09-16 23:35 ` Dale Pontius
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=6749d1ff.717bd429.4c87a997.ee5fa@o2.pl \
--to=radegand@o2.pl \
--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