mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] kernel: proper handle signed modules
Date: Wed, 31 Mar 2021 09:08:18 +0200	[thread overview]
Message-ID: <20210331070818.GA8755@pengutronix.de> (raw)
In-Reply-To: <8077d09253fb57d2305d9f29c5bea2537b51297f.camel@diehl.com>

On Wed, Mar 31, 2021 at 05:17: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>
> ---
> v1 -> v2:
>  - remove config switch
>  - do not strip at targetinstall unconditionally
>  - use INSTALL_MOD_STRIP kbuild option to strip modules
>  - add TARGET_COMPILER_RECORD_SWITCHES to wrapper blacklist
> 
>  rules/kernel.make | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/rules/kernel.make b/rules/kernel.make
> index ea748fc8a..94f57285e 100644
> --- a/rules/kernel.make
> +++ b/rules/kernel.make
> @@ -38,7 +38,8 @@ KERNEL_BUILD_OOT	:= KEEP
>  
>  # use CONFIG_CC_STACKPROTECTOR if available. The rest makes no sense for the kernel
>  KERNEL_WRAPPER_BLACKLIST := \
> -	$(PTXDIST_LOWLEVEL_WRAPPER_BLACKLIST)
> +	$(PTXDIST_LOWLEVEL_WRAPPER_BLACKLIST) \
> +	TARGET_COMPILER_RECORD_SWITCHES

Oh, I meant adding this to PTXDIST_LOWLEVEL_WRAPPER_BLACKLIST. That should
be a separate commit. Adding it to any lowlevel Code may be problematic,
because that stuff is never stripped by ptxdist. It' probably not a problem
in most cases, because most custom linker scripts drop the section anyways,
but better save than sorry.

I should have made it clearer what I meant here, sorry.

Regards,
Michael

>  
>  # Note: for some reason, the error is not visible without the dummy '$(shell :)'
>  # when running 'ptxdist -j -q go'.
> @@ -61,6 +62,7 @@ KERNEL_BASE_OPT		:= \
>  	CROSS_COMPILE=$(KERNEL_CROSS_COMPILE) \
>  	DEPMOD=$(PTXDIST_SYSROOT_HOST)/sbin/depmod \
>  	\
> +	INSTALL_MOD_STRIP=1 \
>  	INSTALL_MOD_PATH=$(KERNEL_PKGDIR) \
>  	PTX_KERNEL_DIR=$(KERNEL_DIR) \
>  	$(call remove_quotes,$(PTXCONF_KERNEL_EXTRA_MAKEVARS))
> @@ -313,7 +315,7 @@ ifdef PTXCONF_KERNEL_MODULES_INSTALL
>  	@$(call install_fixup, kernel-modules, AUTHOR,"Robert Schwebel <r.schwebel@pengutronix.de>")
>  	@$(call install_fixup, kernel-modules, DESCRIPTION,missing)
>  
> -	@$(call install_glob, kernel-modules, 0, 0, -, /lib/modules, *.ko,, k)
> +	@$(call install_glob, kernel-modules, 0, 0, -, /lib/modules, *.ko,, n)
>  	@$(call install_glob, kernel-modules, 0, 0, -, /lib/modules,, *.ko */build */source, n)
>  
>  	@$(call install_finish, kernel-modules)
> -- 
> 2.31.1
> 

> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2021-03-31  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  5:17 Denis Osterland-Heim
2021-03-31  7:08 ` Michael Olbrich [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=20210331070818.GA8755@pengutronix.de \
    --to=m.olbrich@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