From: Mimi Zohar <zohar@linux.ibm.com>
To: "Bruno E. O. Meneguele" <bmeneg@redhat.com>,
linux-integrity@vger.kernel.org
Cc: zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com
Subject: Re: [PATCH] ima-evm-utils: libimaevm: get key description out of verbose condition
Date: Sun, 02 Dec 2018 11:17:58 -0500 [thread overview]
Message-ID: <1543767478.4216.206.camel@linux.ibm.com> (raw)
In-Reply-To: <20181130200547.20490-1-bmeneg@redhat.com>
On Fri, 2018-11-30 at 18:05 -0200, Bruno E. O. Meneguele wrote:
> Key description in keyring is being filled with memory garbage during import
> process if the LOG_LEVEL is not satisfied (using '-vv').
>
> Testing in kernels without trusted keyring support, and importing a v1 (RSA) key
> pair, the kernel fails to find the key since it looks for the key description,
> which is not found due to this issue:
>
> "digsig: key not found, id: DD0558FEB7DDBD26"
>
> Looking at:
> # keyctl show
> Session Keyring
> 635748007 --alswrv 0 0 keyring: _ses
> 673181018 --alswrv 0 65534 \_ keyring: _uid.0
> 360651479 --alswrv 0 0 \_ keyring: _ima
> 499360916 --alswrv 0 0 | \_ user: .N=
> 266933436 --alswrv 0 0 | \_ user: B641632DA94DEE26
>
> Key id 499360916 and 266933436 are both the same key, but the first was added
> without '-vv' in the command line, while the second one was using it.
>
> Signed-off-by: Bruno E. O. Meneguele <bmeneg@redhat.com>
Thanks!
Mimi
> ---
> src/libimaevm.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/src/libimaevm.c b/src/libimaevm.c
> index 6fa0ed4..b6f9b9f 100644
> --- a/src/libimaevm.c
> +++ b/src/libimaevm.c
> @@ -672,12 +672,11 @@ void calc_keyid_v1(uint8_t *keyid, char *str, const unsigned char *pkey, int len
> memcpy(keyid, sha1 + 12, 8);
> log_debug("keyid: ");
> log_debug_dump(keyid, 8);
> + id = __be64_to_cpup((__be64 *) keyid);
> + sprintf(str, "%llX", (unsigned long long)id);
>
> - if (params.verbose > LOG_INFO) {
> - id = __be64_to_cpup((__be64 *) keyid);
> - sprintf(str, "%llX", (unsigned long long)id);
> + if (params.verbose > LOG_INFO)
> log_info("keyid-v1: %s\n", str);
> - }
> }
>
> void calc_keyid_v2(uint32_t *keyid, char *str, RSA *key)
> @@ -694,11 +693,10 @@ void calc_keyid_v2(uint32_t *keyid, char *str, RSA *key)
> memcpy(keyid, sha1 + 16, 4);
> log_debug("keyid: ");
> log_debug_dump(keyid, 4);
> + sprintf(str, "%x", __be32_to_cpup(keyid));
>
> - if (params.verbose > LOG_INFO) {
> - sprintf(str, "%x", __be32_to_cpup(keyid));
> + if (params.verbose > LOG_INFO)
> log_info("keyid: %s\n", str);
> - }
>
> free(pkey);
> }
prev parent reply other threads:[~2018-12-02 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 20:05 [PATCH] ima-evm-utils: libimaevm: get key description out of verbose condition Bruno E. O. Meneguele
2018-12-02 16:17 ` Mimi Zohar [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=1543767478.4216.206.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=bmeneg@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).