From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/testing: add sudo package test
Date: Mon, 10 May 2021 22:14:45 +0200 [thread overview]
Message-ID: <875yzqs5vu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210505191344.2108832-1-arnout@mind.be> (Arnout Vandecappelle's message of "Wed, 5 May 2021 21:13:44 +0200")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> Create a new user 'sudotest' to validate that sudo really works (i.e.
> properly has setuid).
> Creating the user and adding it to sudoers is done at runtime, otherwise
> we'd need to add extra files to the config which complicates things a
> little bit.
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> support/testing/tests/package/test_sudo.py | 36 ++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 support/testing/tests/package/test_sudo.py
> diff --git a/support/testing/tests/package/test_sudo.py b/support/testing/tests/package/test_sudo.py
> new file mode 100644
> index 0000000000..f9d0a6f301
> --- /dev/null
> +++ b/support/testing/tests/package/test_sudo.py
> @@ -0,0 +1,36 @@
> +import os
> +
> +import infra.basetest
> +
> +
> +class TestSudo(infra.basetest.BRTest):
> + config = infra.basetest.BASIC_TOOLCHAIN_CONFIG + \
> + """
> + BR2_PACKAGE_SUDO=y
> + BR2_TARGET_ROOTFS_CPIO=y
> + # BR2_TARGET_ROOTFS_TAR is not set
> + """
initrd, so that implies writable rootfs - So we don't really need those
special adduser flags, but OK.
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-05-10 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:13 [Buildroot] [PATCH] support/testing: add sudo package test Arnout Vandecappelle
2021-05-10 20:14 ` Peter Korsgaard [this message]
2021-05-11 7:17 ` Arnout Vandecappelle
2021-05-11 7:31 ` Peter Korsgaard
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=875yzqs5vu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.