From: yumeng <yumeng18@huawei.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
<keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<davem@davemloft.net>, <herbert@gondor.apana.org.au>,
<dhowells@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <patrick@puiterwijk.org>,
<linux-integrity@vger.kernel.org>,
Stefan Berger <stefanb@linux.ibm.com>
Subject: [PATCH v9 9/9] certs: Add support for using elliptic curve keys for signing modules
Date: Tue, 2 Mar 2021 09:04:53 +0800 [thread overview]
Message-ID: <f49f8d88-d7c1-3a78-115f-07b93d2eb160@huawei.com> (raw)
In-Reply-To: <8618fdb7107ec6ec1aeb4e37faf82421050bdf91.camel@linux.ibm.com>
在 2021/3/1 21:11, Mimi Zohar 写道:
> On Sat, 2021-02-27 at 11:35 +0800, yumeng wrote:
>> 在 2021/2/26 0:08, Stefan Berger 写道:
>>> From: Stefan Berger <stefanb@linux.ibm.com>
>>>
>>
>>> diff --git a/certs/Makefile b/certs/Makefile
>>> index 3fe6b73786fa..c487d7021c54 100644
>>> --- a/certs/Makefile
>>> +++ b/certs/Makefile
>>> @@ -69,6 +69,18 @@ else
>>> SIGNER = -signkey $(obj)/signing_key.key
>>> endif # CONFIG_IMA_APPRAISE_MODSIG
>>>
>>
>> Is there anything wrong in this patch?
>> I can't apply it when I use 'git am '.
>> errors like below:
>>
>> error: certs/Kconfig: does not match index
>> error: patch failed: certs/Makefile:69
>> error: certs/Makefile: patch does not apply
>>
>> Thanks
>
> Nothing wrong with the patch, just a dependency. From the Change log:
> - This patch builds on top Nayna's series for 'kernel build support
> for loading the kernel module signing key'.
> - https://lkml.org/lkml/2021/2/18/856
>
> thanks,
>
> Mimi
>
>
OK, thank you. Sorry for the noise.
next prev parent reply other threads:[~2021-03-02 7:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 16:07 [PATCH v9 0/9] Add support for x509 certs with NIST P384/256/192 keys Stefan Berger
2021-02-25 16:07 ` [PATCH v9 1/9] crypto: Add support for ECDSA signature verification Stefan Berger
2021-02-25 16:07 ` [PATCH v9 2/9] x509: Detect sm2 keys by their parameters OID Stefan Berger
2021-03-03 23:46 ` Stefan Berger
2021-03-05 7:37 ` Tianjia Zhang
2021-03-05 15:04 ` Stefan Berger
2021-03-08 6:58 ` Tianjia Zhang
2021-02-25 16:07 ` [PATCH v9 3/9] x509: Add support for parsing x509 certs with ECDSA keys Stefan Berger
2021-02-25 16:07 ` [PATCH v9 4/9] ima: Support EC keys for signature verification Stefan Berger
2021-02-25 16:07 ` [PATCH v9 5/9] x509: Add OID for NIST P384 and extend parser for it Stefan Berger
2021-02-25 16:07 ` [PATCH v9 6/9] crypto: Add NIST P384 curve parameters Stefan Berger
2021-03-04 5:28 ` Herbert Xu
2021-03-04 13:59 ` Stefan Berger
2021-03-04 22:31 ` Herbert Xu
2021-02-25 16:08 ` [PATCH v9 7/9] crypto: Add math to support fast NIST P384 Stefan Berger
2021-02-25 16:08 ` [PATCH v9 8/9] ecdsa: Register NIST P384 and extend test suite Stefan Berger
2021-02-25 16:08 ` [PATCH v9 9/9] certs: Add support for using elliptic curve keys for signing modules Stefan Berger
2021-02-27 3:35 ` yumeng
2021-03-01 13:11 ` Mimi Zohar
2021-03-02 1:04 ` yumeng [this message]
2021-03-01 21:19 ` Stefan Berger
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=f49f8d88-d7c1-3a78-115f-07b93d2eb160@huawei.com \
--to=yumeng18@huawei.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@puiterwijk.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.com \
--cc=zohar@linux.ibm.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
all inboxes | Powered by JetHome®