DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] reason: silence reason warning about CFG_INSECURE being set
Date: Mon, 24 Mar 2025 19:40:37 +0100	[thread overview]
Message-ID: <791fbb47-5af2-4d9a-a67b-022e6c96a94e@pengutronix.de> (raw)
In-Reply-To: <b44e80d8-ca43-443c-b73e-5dec0e0a4297@pengutronix.de>

Hello Robert,

On 16.12.24 18:17, Ahmad Fatoum wrote:
> On 16.12.24 15:10, Robert Schwebel wrote:
>> On Fri, Dec 13, 2024 at 10:59:55AM +0100, Ahmad Fatoum wrote:
>>> In actual products, CFG_INSECURE should be disabled after we verify
>>> the configuration to be secure. DistroKit uses OP-TEE only on STM32MP13
>>> and not for security, but for power management, so we'll just override
>>> the option and live with the boot-time warning.
>>>
>>> Reported-by: Michael Olbrich <m.olbrich@pengutronix.de>
>>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>>
>> Applied to next
> 
> Please drop again. We only need this override with newer OP-TEE versions.
> This will likely be the case with PTXdist v2025.01.0, but for now it's
> not needed.

With the v2025.03 bump now in next, can you cherry-pick this patch
to next as well?

Thanks,
Ahmad

> 
> Thanks,
> Ahmad
> 
>>
>>> ---
>>>  configs/platform-v7a/bsp.ref | 8 ++++++++
>>>  1 file changed, 8 insertions(+)
>>>
>>> diff --git a/configs/platform-v7a/bsp.ref b/configs/platform-v7a/bsp.ref
>>> index 169e555df53a..bda4db20af2c 100644
>>> --- a/configs/platform-v7a/bsp.ref
>>> +++ b/configs/platform-v7a/bsp.ref
>>> @@ -9,4 +9,12 @@ optee_disabled_features:
>>>      - CFG_ENABLE_EMBEDDED_TESTS
>>>      - CFG_TEE_CORE_TA_TRACE
>>>  
>>> +optee_security_warning_disabled:
>>> +  description: |
>>> +    OP-TEE is used as secure monitor on STM32MP13x providing power
>>> +    management and clock/reset control support. We don't use it as
>>> +    part of a trusted boot setup, so it's apt for OP-TEE to warn
>>> +    about this at startup and thus we'll keep CFG_INSECURE enabled.
>>> +  value: True
>>> +
>>>  # vim: filetype=yaml shiftwidth=2 expandtab
>>> -- 
>>> 2.39.5
>>
> 
> 


-- 
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 |



  reply	other threads:[~2025-03-24 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  9:59 Ahmad Fatoum
2024-12-16 14:10 ` Robert Schwebel
2024-12-16 17:17   ` Ahmad Fatoum
2025-03-24 18:40     ` Ahmad Fatoum [this message]
2025-03-25  6:42       ` Robert Schwebel
2025-03-25  9:17         ` Ahmad Fatoum

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=791fbb47-5af2-4d9a-a67b-022e6c96a94e@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    --cc=r.schwebel@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