From: "Andrea Cervesato" <andrea.cervesato@suse.com>
To: "Petr Vorel" <pvorel@suse.cz>, <ltp@lists.linux.it>
Cc: <linux-integrity@vger.kernel.org>
Subject: Re: [LTP] [PATCH 0/4] ima_{conditionals,measurements}.sh enhancements
Date: Mon, 06 Oct 2025 09:26:22 +0200 [thread overview]
Message-ID: <DDB27AD5V8CC.HACBLFITNI9R@suse.com> (raw)
In-Reply-To: <20251002083701.315334-1-pvorel@suse.cz>
hi!
On Thu Oct 2, 2025 at 10:36 AM CEST, Petr Vorel wrote:
>
> Petr Vorel (4):
> ima_{conditionals,measurements}.sh: Add temporary user
> ima_conditionals.sh: Split test by request
> ima_conditionals.sh: Use 'sg' without 'sudo'
> ima_{conditionals,measurements}.sh: Use 'su' instead of 'sudo'
>
> runtest/ima | 5 +-
> .../integrity/ima/tests/ima_conditionals.sh | 81 ++++++++++++-------
> .../integrity/ima/tests/ima_measurements.sh | 15 ++--
> .../security/integrity/ima/tests/ima_setup.sh | 12 +++
> 4 files changed, 71 insertions(+), 42 deletions(-)
What about creating a tool simulating sudo? I thought that was our main
goal. Using 'su' is ok, but this forces us to create a new user all the
times we execute a new suite, while our new sudo implementation would
create and destroy the user only for the specific session.
- Andrea
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>, <ltp@lists.linux.it>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [LTP] [PATCH 0/4] ima_{conditionals, measurements}.sh enhancements
Date: Mon, 06 Oct 2025 09:26:22 +0200 [thread overview]
Message-ID: <DDB27AD5V8CC.HACBLFITNI9R@suse.com> (raw)
In-Reply-To: <20251002083701.315334-1-pvorel@suse.cz>
hi!
On Thu Oct 2, 2025 at 10:36 AM CEST, Petr Vorel wrote:
>
> Petr Vorel (4):
> ima_{conditionals,measurements}.sh: Add temporary user
> ima_conditionals.sh: Split test by request
> ima_conditionals.sh: Use 'sg' without 'sudo'
> ima_{conditionals,measurements}.sh: Use 'su' instead of 'sudo'
>
> runtest/ima | 5 +-
> .../integrity/ima/tests/ima_conditionals.sh | 81 ++++++++++++-------
> .../integrity/ima/tests/ima_measurements.sh | 15 ++--
> .../security/integrity/ima/tests/ima_setup.sh | 12 +++
> 4 files changed, 71 insertions(+), 42 deletions(-)
What about creating a tool simulating sudo? I thought that was our main
goal. Using 'su' is ok, but this forces us to create a new user all the
times we execute a new suite, while our new sudo implementation would
create and destroy the user only for the specific session.
- Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-06 7:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:36 [PATCH 0/4] ima_{conditionals,measurements}.sh enhancements Petr Vorel
2025-10-02 8:36 ` [LTP] " Petr Vorel
2025-10-02 8:36 ` [PATCH 1/4] ima_{conditionals,measurements}.sh: Add temporary user Petr Vorel
2025-10-02 8:36 ` [LTP] [PATCH 1/4] ima_{conditionals, measurements}.sh: " Petr Vorel
2025-10-02 8:36 ` [PATCH 2/4] ima_conditionals.sh: Split test by request Petr Vorel
2025-10-02 8:36 ` [LTP] " Petr Vorel
2025-10-06 7:26 ` Andrea Cervesato
2025-10-06 7:26 ` Andrea Cervesato via ltp
2025-10-06 11:21 ` Petr Vorel
2025-10-06 11:21 ` Petr Vorel
2025-10-06 11:40 ` Andrea Cervesato
2025-10-06 11:40 ` Andrea Cervesato via ltp
2025-10-08 4:38 ` Petr Vorel
2025-10-08 4:38 ` Petr Vorel
2025-10-02 8:37 ` [PATCH 3/4] ima_conditionals.sh: Use 'sg' without 'sudo' Petr Vorel
2025-10-02 8:37 ` [LTP] " Petr Vorel
2025-10-02 8:37 ` [PATCH 4/4] ima_{conditionals,measurements}.sh: Use 'su' instead of 'sudo' Petr Vorel
2025-10-02 8:37 ` [LTP] [PATCH 4/4] ima_{conditionals, measurements}.sh: " Petr Vorel
2025-10-06 7:26 ` Andrea Cervesato [this message]
2025-10-06 7:26 ` [LTP] [PATCH 0/4] ima_{conditionals, measurements}.sh enhancements Andrea Cervesato via ltp
2025-10-06 9:35 ` [LTP] [PATCH 0/4] ima_{conditionals,measurements}.sh enhancements Petr Vorel
2025-10-06 9:35 ` [LTP] [PATCH 0/4] ima_{conditionals, measurements}.sh enhancements Petr Vorel
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=DDB27AD5V8CC.HACBLFITNI9R@suse.com \
--to=andrea.cervesato@suse.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.