Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: joerg.sommer@navimatix.de
Cc: matthias.schiffer@ew.tq-group.com,
	openembedded-core@lists.openembedded.org, oss@ew.tq-group.com
Subject: Re: [OE-core] [PATCH] kernel.bbclass: install .config to deploy dir
Date: Fri, 9 Feb 2024 00:16:33 +0100	[thread overview]
Message-ID: <20240208231633e8d8b5ad@mail.local> (raw)
In-Reply-To: <104bcdd2-27f1-40fb-9ad0-0fd506af3041@navimatix.de>

On 08/02/2024 14:54:49+0100, J�rg Sommer via lists.openembedded.org wrote:
> On 07.02.24 11:25, Matthias Schiffer via lists.openembedded.org wrote:
> > Deploy the kernel configuration with the built images, so it is easy to
> > check its contents, or rebuild the same configuration outside of the
> > Yocto build system.
> 
> Isn't the kernel already in the -dev package included?
> 
> From a security point of view I wouldn't welcome the inclusion in the
> main package, because the config should not be deployed by default. The
> config contains many information about the available code in the kernel,
> which an attacker can only guess otherwise.

However, as per the GPL, you will have to provide the kernel
configuration to the recipients of the product upon request which can be
any attacker.


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2024-02-08 23:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 10:25 [PATCH] kernel.bbclass: install .config to deploy dir Matthias Schiffer
2024-02-07 12:42 ` [OE-core] " Bruce Ashfield
2024-02-07 13:14   ` Matthias Schiffer
2024-02-07 13:33     ` Mikko Rapeli
2024-02-07 13:51       ` Bruce Ashfield
2024-02-07 15:58 ` Ross Burton
2024-02-08  8:50   ` Matthias Schiffer
2024-02-08  9:31     ` Jose Quaresma
2024-02-08 13:54 ` Jörg Sommer
2024-02-08 23:16   ` Alexandre Belloni [this message]
2024-02-09  7:25     ` Jörg Sommer

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=20240208231633e8d8b5ad@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=joerg.sommer@navimatix.de \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=oss@ew.tq-group.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