From: Carter Cheng <cartercheng@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: classes of methods for gaining access to kernel memory
Date: Fri, 22 Feb 2019 03:36:21 +0800 [thread overview]
Message-ID: <CALS6=qWmGCy5Q51_pEvY9HWADfSTa_W25cNHSmmCLfmdXG6E4g@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jJ11jw=RZ1X_KT7+9f_vjrvEpjADxdqedKLxSQjreG8Tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
One of the papers I had a brief look at is this one-
https://ieeexplore.ieee.org/abstract/document/7546545
On Fri, Feb 22, 2019 at 1:16 AM Kees Cook <keescook@chromium.org> wrote:
> On Thu, Feb 21, 2019 at 8:20 AM Carter Cheng <cartercheng@gmail.com>
> wrote:
> > I was looking over some recent papers for Usenix Security and there are
> a couple on data oriented programming and I have been wondering if there
> are known mitigation techniques for this kind of data corruption attack or
> other attacks that don't involve control flow hijacking.
>
> Can you share some URLs and/or examples? I'm sure other folks here
> would be interested to read those too.
>
> --
> Kees Cook
>
[-- Attachment #2: Type: text/html, Size: 1241 bytes --]
prev parent reply other threads:[~2019-02-21 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 11:12 classes of methods for gaining access to kernel memory Carter Cheng
2019-02-21 1:17 ` Kees Cook
2019-02-21 16:20 ` Carter Cheng
2019-02-21 17:15 ` Kees Cook
2019-02-21 19:36 ` Carter Cheng [this message]
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='CALS6=qWmGCy5Q51_pEvY9HWADfSTa_W25cNHSmmCLfmdXG6E4g@mail.gmail.com' \
--to=cartercheng@gmail.com \
--cc=keescook@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).