public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kyle Bader <kyle.bader@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] binary protection mechanisms in different Linux  distros
Date: Thu, 1 Jul 2010 14:08:03 -0700	[thread overview]
Message-ID: <AANLkTin0nnDriqz_scondnf13OEusGDuFf48PbkKkKoB@mail.gmail.com> (raw)
In-Reply-To: <201007012205.22967.radegand@o2.pl>

> Javier: good point, I haven't really considered the differences between the
> use of  fstack-protector and fstack-protector-all - maybe something to do in
> the future. Would there be a way to find out which option was used on a given
> binary 'post mortem'? (read: after compilation? ;))

While it doesn't differentiate between fstack-protector and
fstack-protector-all this script [1] can detect RELRO, canary, NX/PAX
& PIE:

[509] kyle@blah:~/security-bin$ ./checksec-new.sh --file buggy
RELRO           STACK CANARY      NX/PaX        PIE                     FILE
No RELRO        Canary found      NX enabled    No PIE                  buggy

[1] http://tk-blog.blogspot.com/2009/02/checksec.html
-- 

Kyle



  reply	other threads:[~2010-07-01 21:10 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
2010-07-01 21:05   ` Radoslaw Madej
2010-07-01 21:08     ` Kyle Bader [this message]
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=AANLkTin0nnDriqz_scondnf13OEusGDuFf48PbkKkKoB@mail.gmail.com \
    --to=kyle.bader@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