From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Binary blobs
Date: Fri, 13 Nov 2015 03:07:31 -0500 [thread overview]
Message-ID: <56459A43.3020400@gmail.com> (raw)
In-Reply-To: <d5b6cf123db60902d480129396d0a8fb@opensec.fr>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
> all hardened options for GCC.
Well, you probably can't get away with -fsanitize=undefined
-fsanitize-undefined-trap-on-error yet (object-size and
signed-integer-overflow checks specifically). I know what you mean
though :).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-13 8:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 20:59 [kernel-hardening] Kernel Self Protection Project Kees Cook
2015-11-05 21:14 ` David Windsor
2015-11-06 19:37 ` Kees Cook
2015-11-06 19:42 ` Greg KH
2015-11-06 13:28 ` Yves-Alexis Perez
2015-11-06 18:11 ` Kees Cook
2015-11-06 18:32 ` Richard Weinberger
2015-11-08 10:39 ` Yves-Alexis Perez
2015-11-06 16:00 ` [kernel-hardening] " Quentin Casasnovas
2015-11-06 18:15 ` Kees Cook
2015-11-07 9:52 ` Quentin Casasnovas
2015-11-08 6:50 ` Kees Cook
2015-11-08 10:45 ` Quentin Casasnovas
2015-11-09 21:29 ` Kees Cook
2015-11-09 21:44 ` Valdis.Kletnieks
2015-11-09 21:55 ` David Windsor
2015-11-09 23:35 ` Kees Cook
2015-11-10 8:32 ` Quentin Casasnovas
2015-11-09 23:36 ` Kees Cook
2015-11-09 10:02 ` Rasmus Villemoes
2015-11-09 10:33 ` Quentin Casasnovas
2015-11-09 19:24 ` Rasmus Villemoes
2015-11-09 21:34 ` Kees Cook
2015-11-09 21:59 ` [kernel-hardening] Binary blobs HacKurx
2015-11-09 22:20 ` Valdis.Kletnieks
2015-11-09 23:33 ` Kees Cook
2015-11-13 8:04 ` HacKurx
2015-11-13 8:07 ` Daniel Micay [this message]
2015-11-13 8:55 ` HacKurx
2015-11-06 21:27 ` [kernel-hardening] Kernel Self Protection Project Mickaël Salaün
2015-11-06 22:04 ` Kees Cook
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=56459A43.3020400@gmail.com \
--to=danielmicay@gmail.com \
--cc=kernel-hardening@lists.openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.