From: Greg KH <gregkh@linuxfoundation.org>
To: wzt wzt <wzt.wzt@gmail.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: Open source a new kernel harden project
Date: Mon, 11 May 2020 08:42:56 +0200 [thread overview]
Message-ID: <20200511064256.GB1279905@kroah.com> (raw)
In-Reply-To: <CAEQi4beJgmNfZ0NsWSHCok9-5H_qLze_sFJ_G=1j8CBz9qi2rQ@mail.gmail.com>
On Sun, May 10, 2020 at 10:16:25AM +0800, wzt wzt wrote:
> hi:
> This is a new kernel harden project called hksp(huawei kernel self
> protection), hope some of the mitigation ideas may help you, thanks.
> patch: https://github.com/cloudsec/hksp
<snip>
Interesting.
Are you all going to split this up into submittable pieces so that they
can get proper review and merged upstream? In the format it currently
is in, it's not going to really go anywhere.
thanks,
greg k-h
next prev parent reply other threads:[~2020-05-11 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 2:16 Open source a new kernel harden project wzt wzt
2020-05-10 16:12 ` Lionel Debroux
2020-05-11 5:51 ` wzt wzt
2020-05-11 6:42 ` Greg KH [this message]
2020-05-11 16:12 ` 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=20200511064256.GB1279905@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=wzt.wzt@gmail.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