All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Matthew Garrett <mjg59@google.com>, wangjunwen@baidu.com
Cc: linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH] evm: Don't deadlock if a crypto algorithm is unavailable
Date: Thu, 31 May 2018 15:55:02 -0400	[thread overview]
Message-ID: <1527796502.3427.46.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACdnJutzAbjwieaxH1N5Z-Vt9Q=Gwf5WamPURkO1epVZEUy_8g@mail.gmail.com>

On Thu, 2018-05-31 at 12:30 -0700, Matthew Garrett wrote:
> Cool. Mimi, does this satisfy your concerns with the non-SHA1 patch?

This should be posted as a separate patch, with the appropriate
"Fixes" commit info.  It requires an ack from Herbert Xu.

thanks,

Mimi

  reply	other threads:[~2018-05-31 19:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 17:53 [PATCH V4] evm: Allow non-SHA1 digital signatures Matthew Garrett
2018-05-16 22:12 ` Mimi Zohar
2018-05-17 22:09   ` Matthew Garrett
2018-05-18 16:03     ` Mimi Zohar
2018-05-29 18:26       ` Matthew Garrett
     [not found]         ` <15252CF8C1B4384C8CE16D7D55C66479011414E7BF@BC-MAIL-M04.internal.baidu.com>
2018-05-30 18:29           ` Matthew Garrett
2018-05-30 20:28             ` [PATCH] evm: Don't deadlock if a crypto algorithm is unavailable Matthew Garrett
     [not found]               ` <15252CF8C1B4384C8CE16D7D55C66479011414E83B@BC-MAIL-M04.internal.baidu.com>
2018-05-31 19:30                 ` Matthew Garrett
2018-05-31 19:55                   ` Mimi Zohar [this message]
2018-05-31 20:07                     ` Matthew Garrett
2018-05-31 20:32                       ` Mimi Zohar
2018-05-31 21:06                         ` Matthew Garrett
2018-06-01 11:21                           ` Mimi Zohar
2018-06-01 20:52                             ` Matthew Garrett
2018-06-01 22:26                               ` Mimi Zohar

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=1527796502.3427.46.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=wangjunwen@baidu.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 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.