public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: michalwsieron@gmail.com
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: alex.kanavin@gmail.com, Ross Burton <ross.burton@arm.com>,
	ChenQi <Qi.Chen@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] sanity.bbclass: raise_sanity_error if /tmp is noexec
Date: Thu, 22 Feb 2024 09:41:00 +0000	[thread overview]
Message-ID: <19fa9384f52fb2bc0bd11a32548d8bad@gmail.com> (raw)
In-Reply-To: <b83edeb7-62c3-43af-80cf-c22f2e4041e4@windriver.com>

> Michal, what problem are you seeing?

So originally I encountered this issue when building sbsigntool. Now I 
see that I was simply using a modified version of an older recipe 
revision.
If I were to use a somewhat recent one, I would have this change in 
place 
https://github.com/Wind-River/meta-secure-core/commit/f341b8653c65460d03a652a4af39fc876ea8a992

Anyway, when I talked about this on IRC, I suggested making this a 
warning, but Ross and Richard wanted to hard error on this instead. I 
guess we could make it a warning after all if that would break your 
setup.

Michał


      reply	other threads:[~2024-02-22  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 14:09 [PATCH] sanity.bbclass: raise_sanity_error if /tmp is noexec Michal Sieron
2024-02-09 15:57 ` [OE-core] " Ross Burton
2024-02-21  7:18   ` ChenQi
2024-02-21  9:48     ` Ross Burton
2024-02-21 10:08       ` Alexander Kanavin
2024-02-21 21:36         ` Randy MacLeod
2024-02-22  9:41           ` michalwsieron [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=19fa9384f52fb2bc0bd11a32548d8bad@gmail.com \
    --to=michalwsieron@gmail.com \
    --cc=Qi.Chen@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=ross.burton@arm.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