From: Stefan Berger <stefanb@linux.ibm.com>
To: Vitaly Chikunov <vt@altlinux.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Cc: Elvira Khabirova <lineprinter0@gmail.com>
Subject: Re: [PATCH v2 2/3] ima-evm-utils: Allow manual setting keyid from a cert file
Date: Tue, 4 May 2021 09:28:23 -0400 [thread overview]
Message-ID: <8dfb94e3-d343-191c-1013-8231874a2236@linux.ibm.com> (raw)
In-Reply-To: <20210504043357.4093409-3-vt@altlinux.org>
On 5/4/21 12:33 AM, Vitaly Chikunov wrote:
> Allow user to specify `--keyid @/path/to/cert.pem' to extract keyid from
> SKID of the certificate file. PEM or DER format is auto-detected.
>
> `--keyid' option is reused instead of adding a new option (like possible
> `--cert') to signify to the user it's only keyid extraction and nothing
> more.
>
> Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
>
> +/* Extract keyid from SKID of the cert. No return on error. */
> +static unsigned long int extract_keyid(const char *certfile)
> +{
This could be a library function imaevm_cert_extract_keyid or so, which
could be useful for other users of the library.
next prev parent reply other threads:[~2021-05-04 13:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 4:33 [PATCH v2 0/3] ima-evm-utils: Add --keyid option Vitaly Chikunov
2021-05-04 4:33 ` [PATCH v2 1/3] ima-evm-utils: Allow manual setting keyid for signing Vitaly Chikunov
2021-05-04 12:51 ` Stefan Berger
2021-05-04 23:18 ` Vitaly Chikunov
2021-05-04 23:43 ` Dmitry V. Levin
2021-05-06 1:15 ` Vitaly Chikunov
2021-05-04 4:33 ` [PATCH v2 2/3] ima-evm-utils: Allow manual setting keyid from a cert file Vitaly Chikunov
2021-05-04 13:04 ` Stefan Berger
2021-05-04 23:21 ` Vitaly Chikunov
2021-05-04 13:28 ` Stefan Berger [this message]
2021-05-04 4:33 ` [PATCH v2 3/3] ima-evm-utils: Read keyid from the cert appended to the key file Vitaly Chikunov
2021-05-04 13:38 ` Stefan Berger
2021-05-04 22:27 ` Vitaly Chikunov
2021-05-05 1:04 ` Stefan Berger
2021-05-05 1:15 ` Vitaly Chikunov
2021-05-05 5:15 ` 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=8dfb94e3-d343-191c-1013-8231874a2236@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=lineprinter0@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=vt@altlinux.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).