From: Solar Designer <solar@openwall.com>
To: oss-security@lists.openwall.com
Cc: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: Stack guard canary massaging
Date: Mon, 31 Oct 2016 12:22:36 +0100 [thread overview]
Message-ID: <20161031112236.GA6816@openwall.com> (raw)
In-Reply-To: <14b76703-8185-dadb-7605-10496331452c@redhat.com>
On Mon, Oct 31, 2016 at 11:48:45AM +0100, Florian Weimer wrote:
> Sorry for cross-posting.
Sorry to bikeshed, but I think this isn't a kernel-hardening topic at
all, so the thread should continue on oss-security only, please.
Florian, if there's a reason why you think it's kernel-hardening
related, please let me know. To me, it looks like userspace hardening
that is not even kernel-assisted (at least not directly in this place,
even though the kernel may have helped provide the random numbers).
If your cross-posting was to reach more of the right people, then you
have already done so, and they can join oss-security now. ;-)
Alexander
next prev parent reply other threads:[~2016-10-31 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:48 [kernel-hardening] Stack guard canary massaging Florian Weimer
2016-10-31 11:22 ` Solar Designer [this message]
2016-10-31 11:41 ` [kernel-hardening] " Daniel Micay
2016-10-31 13:14 ` Jann Horn
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=20161031112236.GA6816@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=oss-security@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.