Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Matthew Garrett <mjg59@google.com>, linux-integrity@vger.kernel.org
Subject: Re: [PATCH] evm: Allow non-SHA1 digital signatures
Date: Thu, 10 May 2018 13:10:20 -0300	[thread overview]
Message-ID: <87a7t71ogj.fsf@morokweng.localdomain> (raw)
In-Reply-To: <1525915585.3551.302.camel@linux.vnet.ibm.com>


Mimi Zohar <zohar@linux.vnet.ibm.com> writes:

> [Cc'ing Thiago Bauermann]
>
> On Fri, 2018-04-20 at 13:34 -0700, Matthew Garrett wrote:
>> SHA1 is reasonable in HMAC constructs, but it's desirable to be able to
>> use stronger hashes in digital signatures. Modify the EVM crypto code so
>> the hash type is imported from the digital signature and passed down to
>> the hash calculation code, and return the digest size to higher layers
>> for validation.
>
> Currently the code passes just the digest field of the
> evm_ima_xattr_data structure to evm_calc_hmac() and evm_calc_hash().
> Instead of passing three fields - hash algorithm, digest size, and
> digest - pass a structure. Consider using the existing
> ima_digest_data structure.
>
> My only concern is that Thiago is working in this area of the code.
> Thiago, any comments?

Thanks for your concern. This is not a problem for me. It will be simple
to rebase on top of this patch when I post my patches.

-- 
Thiago Jung Bauermann
IBM Linux Technology Center

  reply	other threads:[~2018-05-10 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 20:34 [PATCH] evm: Allow non-SHA1 digital signatures Matthew Garrett
2018-05-09 22:06 ` Matthew Garrett
2018-05-10  1:26 ` Mimi Zohar
2018-05-10 16:10   ` Thiago Jung Bauermann [this message]
2018-05-10 16:28 ` Thiago Jung Bauermann

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=87a7t71ogj.fsf@morokweng.localdomain \
    --to=bauerman@linux.vnet.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.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