Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20181022222614.41016-1-mikewu@google.com> <20181031093619.24n53lfeink3qsk6@linux-8ccs>
In-Reply-To: <20181031093619.24n53lfeink3qsk6@linux-8ccs>
From:   Ke Wu <mikewu@google.com>
Date:   Mon, 5 Nov 2018 11:13:17 -0800
Message-ID: <CANRnR9Qs0wjAprhLzNTg1COLyyh9pcv_SxtZnKBoadED0RJVjg@mail.gmail.com>
Subject: Re: [PATCH] modsign: use all trusted keys to verify module signature
To:     jeyu@kernel.org
Cc:     dhowells@redhat.com, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi, I'm wondering if there is any update for the patch.

Thanks!

On Wed, Oct 31, 2018 at 2:36 AM Jessica Yu <jeyu@kernel.org> wrote:
>
> +++ Ke Wu [22/10/18 15:26 -0700]:
> >Make mod_verify_sig to use all trusted keys. This allows keys in
> >secondary_trusted_keys to be used to verify PKCS#7 signature on a
> >kernel module.
> >
> >Signed-off-by: Ke Wu <mikewu@google.com>
>
> Thanks for the ping, I had missed this patch.
>
> David, could I get an ACK please?
>
> Thanks!
>
> Jessica
>
> >---
> > kernel/module_signing.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/kernel/module_signing.c b/kernel/module_signing.c
> >index f2075ce8e4b3..a8b923ba1a39 100644
> >--- a/kernel/module_signing.c
> >+++ b/kernel/module_signing.c
> >@@ -83,6 +83,6 @@ int mod_verify_sig(const void *mod, struct load_info *info)
> >       }
> >
> >       return verify_pkcs7_signature(mod, modlen, mod + modlen, sig_len,
> >-                                    NULL, VERIFYING_MODULE_SIGNATURE,
> >+                                    (void *)1UL, VERIFYING_MODULE_SIGNATURE,
> >                                     NULL, NULL);
> > }
> >--
> >2.19.1.568.g152ad8e336-goog
> >


-- 
Ke Wu | Software Engineer | mikewu@google.com | Google Inc.