From: Mimi Zohar <zohar@linux.ibm.com>
To: Vitaly Chikunov <vt@altlinux.org>,
Mimi Zohar <zohar@linux.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v7 0/3] ima-evm-utils: Add --keyid option
Date: Tue, 06 Jul 2021 12:23:26 -0400 [thread overview]
Message-ID: <7d201d4724e7399f87c0cc2f7291cfd13351d156.camel@linux.ibm.com> (raw)
In-Reply-To: <20210701011323.2377251-1-vt@altlinux.org>
Hi Vitaly,
On Thu, 2021-07-01 at 04:13 +0300, Vitaly Chikunov wrote:
> Allow user to set signature's keyid using `--keyid' option. Keyid should
> correspond to SKID in certificate. When keyid is calculated using SHA-1
> in libimaevm it may mismatch keyid extracted by the kernel from SKID of
> certificate (the way public key is presented to the kernel), thus making
> signatures not verifiable. This may happen when certificate is using non
> SHA-1 SKID (see rfc7093) or just 'unique number' (see rfc5280 4.2.1.2).
> As a last resort user may specify arbitrary keyid using the new option.
> Certificate filename could be used instead of the hex number with
> `--keyid-from-cert' option. And, third option is to read keyid from the
> cert appended to the key file.
>
> These commits create backward incompatible ABI change for libimaevm,
> thus soname should be incremented on release.
I haven't started using Github actions. Here are some new Travis
complaints:
Alpine:
libimaevm.c: In function 'sign_hash_v2':
libimaevm.c:996:47: warning: taking address of packed member of 'struct
signature_v2_hdr' may result in an unaligned pointer value [-Waddress-
of-packed-member]
996 | int keyid_read_failed = read_keyid_from_key(&hdr->keyid,
keyfile);
| ^~~~~~~~~~~
libimaevm.c:999:18: warning: taking address of packed member of 'struct
signature_v2_hdr' may result in an unaligned pointer value [-Waddress-
of-packed-member]
999 | calc_keyid_v2(&hdr->keyid, name, pkey);
| ^~~~~~~~~~~
centos:
./.libs/libimaevm.so: undefined reference to `X509_get0_subject_key_id'
./.libs/libimaevm.so: undefined reference to `ASN1_STRING_get0_data'
xenial:
libimaevm.c: In function 'extract_keyid':
libimaevm.c:695:2: warning: implicit declaration of function
'X509_get0_subject_key_id' [-Wimplicit-function-declaration]
if (!(skid = X509_get0_subject_key_id(x))) {
^
libimaevm.c:695:13: warning: assignment makes pointer from integer
without a cast [enabled by default]
if (!(skid = X509_get0_subject_key_id(x))) {
thanks,
Mimi
next prev parent reply other threads:[~2021-07-06 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 1:13 [PATCH v7 0/3] ima-evm-utils: Add --keyid option Vitaly Chikunov
2021-07-01 1:13 ` [PATCH v7 1/3] ima-evm-utils: Allow manual setting keyid for signing Vitaly Chikunov
2021-07-01 1:13 ` [PATCH v7 2/3] ima-evm-utils: Allow manual setting keyid from a cert file Vitaly Chikunov
2021-07-05 19:59 ` Mimi Zohar
2021-07-05 20:50 ` Vitaly Chikunov
2021-07-01 1:13 ` [PATCH v7 3/3] ima-evm-utils: Read keyid from the cert appended to the key file Vitaly Chikunov
2021-07-05 20:04 ` Mimi Zohar
2021-07-05 21:15 ` Vitaly Chikunov
2021-07-06 16:23 ` Mimi Zohar [this message]
2021-07-06 21:13 ` [PATCH v7 0/3] ima-evm-utils: Add --keyid option Vitaly Chikunov
2021-07-08 15:37 ` Mimi Zohar
2021-07-08 15:46 ` Vitaly Chikunov
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=7d201d4724e7399f87c0cc2f7291cfd13351d156.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=vt@altlinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox