From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] kernel: proper handle signed modules
Date: Thu, 1 Apr 2021 08:54:17 +0200 [thread overview]
Message-ID: <f0855dc5-c5c8-3496-97c7-fd9e9fa8b683@pengutronix.de> (raw)
In-Reply-To: <20210401055938.GJ8755@pengutronix.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1141 bytes --]
On 4/1/21 7:59 AM, Michael Olbrich wrote:
> On Wed, Mar 31, 2021 at 11:37:11AM +0000, Denis Osterland-Heim wrote:
>> If CONFIG_MODULE_SIG_ALL is set in kernelconfig then modules will be
>> automatically signed during the modules_install phase of a kernel build.
>>
>> Signed modules are BRITTLE as the signature is outside of the defined ELF
>> container. Thus they MAY NOT be stripped once the signature is computed
>> and attached. Note the entire module is the signed payload, including any
>> and all debug information present at the time of signing.
>>
>> See: https://www.kernel.org/doc/html/latest/admin-guide/module-signing.html
>> Signed-off-by: Denis Osterland-Heim <denis.osterland@diehl.com>
>> ---
>> v2 -> v3:
>> - move TARGET_COMPILER_RECORD_SWITCHES to PTXDIST_LOWLEVEL_WRAPPER_BLACKLIST
>
> Marc, what do you think?
lgtm
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-04-01 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 11:37 Denis Osterland-Heim
2021-04-01 5:59 ` Michael Olbrich
2021-04-01 6:54 ` Marc Kleine-Budde [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=f0855dc5-c5c8-3496-97c7-fd9e9fa8b683@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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