From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [PATCH ima-evm-utils] Check for tsspcrread in runtime
Date: Wed, 15 Jul 2020 15:15:29 +0200 [thread overview]
Message-ID: <20200715131529.GA32201@dell5510> (raw)
In-Reply-To: <1594813634.12900.264.camel@linux.ibm.com>
Hi Mimi,
> > > Nice! It works.
> > Thanks a lot for a testing?
> Yes, reviewed/tested together.
Sorry, I put question mark by accident, but thanks for confirmation anyway.
...
> When running these tests remotely, it helps to know which method of
> reading the PCRs is used. How about adding something like this to
> both instances of tpm2_pcr_supported()?
> if (imaevm_params.verbose > LOG_INFO)
> log_info("Using %s to read PCRs.\n", CMD);
+1
> > Shell I post v2 or you amend my patch?
> Either way is fine.
Sending v2 in a minute. Feel free to amend it to suit your needs.
> > BTW I was thinking to create custom function / macro for handling errmsg to
> > reduce duplicity.
> Sure, I assume that would be in addition to log_err() and log_errno().
I'll probably postpone this cleanup after this patchset is merged (unless you do
the cleanup yourself). It can even wait after the release, I don't want to block
release with minor cleanup.
> > + there is minor warning on newer gcc, I'm not sure how to fix that:
> > evmctl.c: In function ‘read_tpm_banks’:
> > evmctl.c:1404:25: warning: ‘%2.2d’ directive writing between 2 and 10 bytes into a region of size 3 [-Wformat-overflow=]
> > 1404 | sprintf(pcr_str, "PCR-%2.2d", i);
> > | ^~~~~
> > evmctl.c:1404:20: note: directive argument in the range [0, 2147483647]
> > 1404 | sprintf(pcr_str, "PCR-%2.2d", i);
> > | ^~~~~~~~~~~
> > evmctl.c:1404:3: note: ‘sprintf’ output between 7 and 15 bytes into a destination of size 7
> > 1404 | sprintf(pcr_str, "PCR-%2.2d", i);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Interesting. Checking that "i" isn't greater than 99 solves this
> warning. Changing pcr_str size from 7 to 8 solves the other warning.
Nice, how simple. I wasn't sure myself about changing of the array size.
Feel free to just fix it.
Kind regards,
Petr
prev parent reply other threads:[~2020-07-15 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 15:46 [PATCH ima-evm-utils] Check for tsspcrread in runtime Petr Vorel
2020-07-14 20:06 ` Mimi Zohar
2020-07-15 6:21 ` Petr Vorel
2020-07-15 11:47 ` Mimi Zohar
2020-07-15 13:15 ` Petr Vorel [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=20200715131529.GA32201@dell5510 \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.ibm.com \
--cc=zohar@linux.vnet.ibm.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