From: Mimi Zohar <zohar@linux.ibm.com>
To: Ken Goldman <kgold@linux.ibm.com>,
Linux Integrity <linux-integrity@vger.kernel.org>,
Ken Goldman <kgoldman@us.ibm.com>
Subject: Re: Spec needed for ima-modsig template
Date: Mon, 06 Jan 2020 10:50:21 -0500 [thread overview]
Message-ID: <1578325821.5222.42.camel@linux.ibm.com> (raw)
In-Reply-To: <748a5aaf-8537-4313-a020-18c57a6056bb@linux.ibm.com>
On Mon, 2020-01-06 at 09:36 -0500, Ken Goldman wrote:
> On 1/4/2020 6:32 PM, Mimi Zohar wrote:
> > The "sig" and "modsig" hash algorithms are independent
> > of each other. They might or might not be the same.
>
> My question was about the d-modsig hash algorithm. Should the spec say:
>
> 1 - If d-ng and d-modsig are both present, the hash algorithms MUST be
> the same.
No, the hash algorithm does not need to be the same. The "d-ng" hash
algorithm is based on the "sig" field, if present, and defaults to the
IMA default algorithm as specified in the Kconfig -
CONFIG_IMA_DEFAULT_HASH. The appended signature ("sig" field), like
in the case of the kexec kernel image, might be a third party
signature.
>
> I did have a question about the 'd-ng | sig | sig' template. Is that an
> error or could a file be signed with e.g. both RSA-2048 and RSA-3072?
>
> Etc. You can see where I'm going - precise rules for an IMA log verifier.
The "sig" field is the original IMA signature, stored as an extended
attribute. If/when IMA fs-verity support is added, that signature
would require defining new digest and signature field types. A
template with two "sig" fields doesn't make sense.
Mimi
next prev parent reply other threads:[~2020-01-06 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 20:10 Spec needed for ima-modsig template Ken Goldman
2020-01-02 20:25 ` Mimi Zohar
2020-01-02 22:24 ` Ken Goldman
2020-01-02 23:22 ` Mimi Zohar
2020-01-03 18:27 ` Ken Goldman
2020-01-03 18:57 ` Spec needed for ima-buf template Ken Goldman
2020-01-03 19:25 ` Spec needed for ima-buf template - missing hash algorithm Ken Goldman
2020-01-04 23:32 ` Spec needed for ima-modsig template Mimi Zohar
2020-01-06 14:27 ` Ken Goldman
2020-01-06 17:18 ` Mimi Zohar
2020-01-06 14:36 ` Ken Goldman
2020-01-06 15:50 ` Mimi Zohar [this message]
2020-01-06 16:01 ` Ken Goldman
2020-01-06 16:55 ` Mimi Zohar
2020-01-07 8:53 ` Roberto Sassu
2020-01-07 15:40 ` Ken Goldman
2020-01-07 17:53 ` Roberto Sassu
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=1578325821.5222.42.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=kgold@linux.ibm.com \
--cc=kgoldman@us.ibm.com \
--cc=linux-integrity@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.