From: Greg KH <gregkh@linuxfoundation.org>
To: Rick Mark <rickmark@outlook.com>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: Hello Kernel Hardening
Date: Wed, 31 Jul 2019 11:18:18 +0200 [thread overview]
Message-ID: <20190731091818.GB29294@kroah.com> (raw)
In-Reply-To: <BYAPR07MB5782E8E1F2105AD154035E10DADF0@BYAPR07MB5782.namprd07.prod.outlook.com>
On Wed, Jul 31, 2019 at 06:52:04AM +0000, Rick Mark wrote:
> Per the instructions in the get involved I'm here saying hello.
>
> My name is Rick Mark, currently a security engineer at Dropbox in SF.
>
> I've been toying around with various things I've found in the wild
> over the years and recently put together this CC Attribution paper
> 'Security Critical Kernel Object Confidentiality and Integrity'
> (https://dbx.link/sckoci).
Link needs permissions to view it :(
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-31 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:52 Hello Kernel Hardening Rick Mark
2019-07-31 9:18 ` Greg KH [this message]
2019-07-31 19:55 ` Kees Cook
2019-07-31 20:33 ` Rick Mark
2019-08-01 5:54 ` Greg KH
2019-08-01 20:00 ` Rick Mark
2019-08-01 20:25 ` Greg KH
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=20190731091818.GB29294@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=rickmark@outlook.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).