public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v5 2/3] ima-evm-utils: Allow manual setting keyid from a cert file
Date: Thu, 6 May 2021 16:17:07 -0400	[thread overview]
Message-ID: <665d1368-c7a6-4aa4-1d43-fb65c692d69c@linux.ibm.com> (raw)
In-Reply-To: <20210506034702.216842-3-vt@altlinux.org>


On 5/5/21 11:47 PM, Vitaly Chikunov wrote:
>   
> +enum keyid_file_type {
> +	KEYID_FILE_PEM_KEY = 0,
> +	KEYID_FILE_UNK_CERT,
> +};
> +
> +/*
> + * @keyid:	Pointer to 32-bit value in network order, can be unaligned.
> + * @file_type:	KEYID_FILE_PEM_KEY - PEM encoded private key file with possible
> + *		appended x509 cert;
> + *		KEYID_FILE_UNK_CERT - x509 cert file (maybe PEM, maybe DER
> + *		encoded).
> + * Return:	0 on error; 1 on success.

Many other APIs of the library return -1 on error and 0 on success...



  reply	other threads:[~2021-05-06 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  3:46 [PATCH v5 0/3] ima-evm-utils: Add --keyid option Vitaly Chikunov
2021-05-06  3:47 ` [PATCH v5 1/3] ima-evm-utils: Allow manual setting keyid for signing Vitaly Chikunov
2021-05-06  3:47 ` [PATCH v5 2/3] ima-evm-utils: Allow manual setting keyid from a cert file Vitaly Chikunov
2021-05-06 20:17   ` Stefan Berger [this message]
2021-05-06  3:47 ` [PATCH v5 3/3] ima-evm-utils: Read keyid from the cert appended to the key file Vitaly Chikunov
2021-05-06 20:10 ` [PATCH v5 0/3] ima-evm-utils: Add --keyid option Stefan Berger
2021-05-07  1:43   ` Vitaly Chikunov
2021-05-07 14:01     ` Stefan Berger

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=665d1368-c7a6-4aa4-1d43-fb65c692d69c@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=dmitry.kasatkin@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