From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/3] IMA: Refactor datafiles directory
Date: Fri, 7 Aug 2020 09:17:54 +0200 [thread overview]
Message-ID: <20200807071754.GA9748@dell5510> (raw)
In-Reply-To: <20200803184726.2416-3-t-josne@linux.microsoft.com>
Hi Lachlan,
> The IMA datafiles directory is structured so that it cannot be directly
> expanded to include datafiles for tests other than `ima_policy.sh`.
> Move the contents of the IMA datafiles directory into an IMA
> datafiles/policy directory.
Why it's required? Can't you use glob for inclusion?
*.policy for valid policies
*.policy-invalid for invalid policies
*.policy* for all policies
BTW I plan to use policies for other tests than just ima_policy.sh
I don't refuse this patch, I just simply don't understand why it's required.
Kind regards,
Petr
next prev parent reply other threads:[~2020-08-07 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 18:47 [LTP] [PATCH v1 0/3] Verify measurement of certificate imported into a keyring Lachlan Sneff
2020-08-03 18:47 ` [LTP] [PATCH 1/3] IMA: Update key test documentation Lachlan Sneff
2020-08-04 4:35 ` Petr Vorel
2020-08-04 16:42 ` Lachlan Sneff
2020-08-05 8:36 ` Petr Vorel
2020-08-05 8:44 ` Petr Vorel
2020-08-03 18:47 ` [LTP] [PATCH 2/3] IMA: Refactor datafiles directory Lachlan Sneff
2020-08-07 7:17 ` Petr Vorel [this message]
2020-08-07 9:01 ` Petr Vorel
2020-08-07 12:27 ` Petr Vorel
2020-08-03 18:47 ` [LTP] [PATCH 3/3] IMA: Add a test to verify measurement of certificate imported into a keyring Lachlan Sneff
-- strict thread matches above, loose matches on Subject: below --
2020-08-03 17:59 [LTP] [PATCH v1 0/3] Verify " Lachlan Sneff
2020-08-03 17:59 ` [LTP] [PATCH 2/3] IMA: Refactor datafiles directory Lachlan Sneff
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=20200807071754.GA9748@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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