From: wzt wzt <wzt.wzt@gmail.com>
To: Lionel Debroux <lionel_debroux@yahoo.fr>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: Open source a new kernel harden project
Date: Mon, 11 May 2020 13:51:12 +0800 [thread overview]
Message-ID: <CAEQi4bfPfkqZH77Ec6UWvMabF+F6PHEpAv74Hv9if5XP=7K3Fw@mail.gmail.com> (raw)
In-Reply-To: <62f8bcee-ac3c-e344-b95e-18ef86903f55@yahoo.fr>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
This mail and previous mail were my personal activities，I have done my
research in spare time，the name of hksp was given by myself，it's not
related to huawei company，there is no huawei product use these code.
This patch code is raised by me,as one person do not have enough energy to
cover every thing，so there is lack of quality assurance like review and
test. THis patch is just a demo code.
Thanks you for the issue have found，i am trying to fix the related code.
在 2020年5月11日星期一，Lionel Debroux <lionel_debroux@yahoo.fr> 写道：
> 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
>> [...]
> See also
>
https://grsecurity.net/huawei_hksp_introduces_trivially_exploitable_vulnerability
>
>
> Regards,
> Lionel Debroux.
>
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
next prev parent reply other threads:[~2020-05-11 11:12 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 [this message]
2020-05-11 6:42 ` Greg KH
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='CAEQi4bfPfkqZH77Ec6UWvMabF+F6PHEpAv74Hv9if5XP=7K3Fw@mail.gmail.com' \
--to=wzt.wzt@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=lionel_debroux@yahoo.fr \
/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.