public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: dhowells@redhat.com, Andy Lutomirski <luto@kernel.org>,
	James Morris <jmorris@namei.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Luis Rodriguez <mcgrof@gmail.com>,
	keyrings@linux-nfs.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] MODSIGN: Use PKCS#7 for module signatures
Date: Tue, 28 Jul 2015 10:03:11 +0100	[thread overview]
Message-ID: <6447.1438074191@warthog.procyon.org.uk> (raw)
In-Reply-To: <CALCETrVwxZD=f38aK1EpHLjv9fnzMsTiuHbHDRqECpFkaMKdqg@mail.gmail.com>

Andy Lutomirski <luto@amacapital.net> wrote:

> How would it cause kexec problems?  I can only see it being a problem
> if Authenticode can't handle authattrs, right?  There shouldn't be any
> legacy PKCS7 kexec images whatsoever, because no existing kernel will
> boot them or generate them.

I was wondering if it is possible to get an mscode message that doesn't have
authattrs in it.  I guess we can just ignore the possibility until the matter
arises, if it does, and deal with it then as appropriate.

David

  reply	other threads:[~2015-07-28  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 19:33 [GIT PULL] MODSIGN: Use PKCS#7 for module signatures David Howells
2015-07-27 20:46 ` Andy Lutomirski
2015-07-27 22:43   ` David Howells
2015-07-27 23:15     ` Andy Lutomirski
2015-07-28  9:03       ` David Howells [this message]
2015-07-28  9:12     ` David Woodhouse
2015-07-28  9:28       ` David Howells

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=6447.1438074191@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=mcgrof@gmail.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