From: Vitaly Chikunov <vt@altlinux.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org,
Elvira Khabirova <lineprinter0@gmail.com>
Subject: Re: [PATCH v2 2/3] ima-evm-utils: Allow manual setting keyid from a cert file
Date: Wed, 5 May 2021 02:21:00 +0300 [thread overview]
Message-ID: <20210504232100.rj36uskbjiktmmyw@altlinux.org> (raw)
In-Reply-To: <2702b9ca-d20a-8348-2fc5-4e36ec6b45bf@linux.ibm.com>
Stefan,
On Tue, May 04, 2021 at 09:04:44AM -0400, Stefan Berger wrote:
>
> 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>
> > ---
> > README | 1 +
> > src/evmctl.c | 82 +++++++++++++++++++++++++++++++++++++++++++++++---
> > tests/sign_verify.test | 1 +
> > 3 files changed, 79 insertions(+), 5 deletions(-)
> >
> > @@ -2567,12 +2571,71 @@ static char *get_password(void)
> > +/* Extract keyid from SKID of the cert. No return on error. */
> > +static unsigned long int extract_keyid(const char *certfile)
> > +{
> > + uint32_t keyid_raw;
> > + const ASN1_OCTET_STRING *skid;
> > + int skid_len;
> > + X509 *x = NULL;
> > + int pem;
> > + FILE *in;
> > +
> > + if (!(in = fopen(certfile, "r"))) {
> > + log_err("Cannot open cert file %s: %s\n", certfile,
> > + strerror(errno));
> > + exit(1);
> > + }
> > + if ((pem = is_encoding_pem(in)))
>
>
> I think you should not try to detect PEM by '-----' at the beginning since
> it typically allows other text at the beginning of the file as well, such as
> a text dump of the cert. Instead search for '-----BEGIN CERTIFICATE-----' in
> the whole file or just
> try to read it as PEM first and then fall back to DER decoding if PEM failed.
This is a good idea. I will do it in v3.
Thanks,
next prev parent reply other threads:[~2021-05-04 23:21 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 [this message]
2021-05-04 13:28 ` Stefan Berger
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=20210504232100.rj36uskbjiktmmyw@altlinux.org \
--to=vt@altlinux.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=lineprinter0@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=stefanb@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;
as well as URLs for NNTP newsgroup(s).