From: Omri Sarig <omri.sarig13@gmail.com>
To: akuster808@gmail.com
Cc: yocto-patches@lists.yoctoproject.org,
Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: Re: [yocto-patches] [PATCH v2 3/3] oeqa/cases/tpm2: Add tpm2-pkcs11-tools sanity test
Date: Tue, 18 Mar 2025 11:42:11 +0100 [thread overview]
Message-ID: <b5bf682d-62a0-4388-9196-025e8fc32a10@gmail.com> (raw)
In-Reply-To: <Z9FsubzQXInmctnY@nuoska>
Hi Armin,
Haven't heard anything in about a week.
Will you consider adding these patches to meta-security?
Thanks,
With Kind Regards,
Omri
On 3/12/25 12:15, Mikko Rapeli wrote:
> Hi,
>
> On Wed, Mar 12, 2025 at 12:07:29PM +0100, Omri Sarig wrote:
>> On 3/12/25 11:38, Mikko Rapeli wrote:
>>> Hi,
>> Thanks for the fast reply!
>>
>>> On Wed, Mar 12, 2025 at 11:32:41AM +0100, Omri Sarig via lists.yoctoproject.org wrote:
>>>> Add a very simple sanity test, which ensures that tpm2_ptool can run
>>>> without problems when the relevant package is available.
>>>>
>>>> This test case is available here to help prevent future errors, where
>>>> the tool is unable to run after installation, due to missing
>>>> dependencies for example.
>>>>
>>>> Contrary to other tests in the file, this test does not communicate with
>>>> the TPM module itself, it only ensures that the tool (tpm2_ptool) can be
>>>> loaded without any errors. Therefore, we don't need to depend on
>>>> anything other than having the package installed.
>>>>
>>>> Signed-off-by: Omri Sarig <omri.sarig13@gmail.com>
>>>> ---
>>>> meta-tpm/lib/oeqa/runtime/cases/tpm2.py | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> diff --git a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py
>>>> index 8e90dc9..c2e6dfa 100644
>>>> --- a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py
>>>> +++ b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py
>>>> @@ -67,3 +67,8 @@ class Tpm2Test(OERuntimeTestCase):
>>>> def test_tpm2_swtpm_reset(self):
>>>> (status, output) = self.target.run('swtpm_ioctl -i --tcp :2322')
>>>> self.assertEqual(status, 0, msg="swtpm reset failed: %s" % output)
>>>> +
>>>> + @OEHasPackage(['tpm2-pkcs11-tools'])
>>>> + def test_tpm2_pkcs11_tools(self):
>>>> + (status, output) = self.target.run("tpm2_ptool --help")
>>>> + self.assertEqual(status, 0, msg="Module cannot be run with error: %s" % output)
>>> Thanks! This good to start with. I think it's a separate question now if
>>> meta-tpm test images will include tpm2-pkcs11-tools and actually run
>>> this test.
>> I've looked into it now.
>> If I understand it correctly, and the image used for testing is
>> security-tpm2-image
>> (meta-security/meta-tpm/recipes-core/images/security-tpm2-image.bb), then
>> the image already have tpm2-pkcs11-tools implicitly installed in it.
>>
>> This is done as the image have the recipe of swtpm and the config of gnutls,
>> which adds tpm2-pkcs11-tools to the runtime dependencies of swtpm.
>>
>> I think we can do one of the following:
>>
>> 1. Update the image to explicitly install tpm2-pkcs11-tools (as a package in
>> IMAGE_INSTALL).
>> 2. Update the commit message to add the above explanation, so users will
>> know that the tool is added to the image (and thus tested).
>> 3. Leave the commits as-is.
>>
>> What do you think makes the most sense?
> If the image already has it then I think we can leave as is.
>
> But Armin as the layer maintainer can decide.
>
> Cheers,
>
> -Mikko
prev parent reply other threads:[~2025-03-18 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:32 [PATCH v2 0/3] meta-tpm: Update python runtime dependencies Omri Sarig
2025-03-12 10:32 ` [PATCH v2 1/3] tpm2-pytss: Add python3-asn1crypto runtime dependency Omri Sarig
2025-03-12 10:32 ` [PATCH v2 2/3] tpm2-pkcs11: Add tools python runtime dependencies Omri Sarig
2025-03-12 10:32 ` [PATCH v2 3/3] oeqa/cases/tpm2: Add tpm2-pkcs11-tools sanity test Omri Sarig
2025-03-12 10:38 ` [yocto-patches] " Mikko Rapeli
2025-03-12 11:07 ` Omri Sarig
2025-03-12 11:15 ` Mikko Rapeli
2025-03-18 10:42 ` Omri Sarig [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=b5bf682d-62a0-4388-9196-025e8fc32a10@gmail.com \
--to=omri.sarig13@gmail.com \
--cc=akuster808@gmail.com \
--cc=mikko.rapeli@linaro.org \
--cc=yocto-patches@lists.yoctoproject.org \
/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.