From: David Woodhouse <dwmw2@infradead.org>
To: David Howells <dhowells@redhat.com>, Andy Lutomirski <luto@kernel.org>
Cc: jmorris@namei.org, mcgrof@gmail.com, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] MODSIGN: Use PKCS#7 for module signatures
Date: Tue, 28 Jul 2015 10:12:21 +0100 [thread overview]
Message-ID: <1438074741.26913.96.camel@infradead.org> (raw)
In-Reply-To: <17310.1438036987@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On Mon, 2015-07-27 at 23:43 +0100, David Howells wrote:
>
> PKCS#7: Require authenticated attributes
>
> Require there to be authenticated attributes in the PKCS#7/CMS message so
> that an attacker can't drop them to provide greater opportunity for
> manipulating the message.
There doesn't seem to be a lot of point in this part. If the
authenticated attribute isn't being *checked*, then the attacker
doesn't need to drop it at all. There's no point in merely requiring
its *existence*.
As part of the firmware signatures, if we are asked to check the
filename then yes we should require it to be present *and* match. But
if we aren't checking (which we can't for modules since we don't know
what's being loaded), why require it to be present at all?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-07-28 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 19:33 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
2015-07-28 9:12 ` David Woodhouse [this message]
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=1438074741.26913.96.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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
all inboxes | Powered by JetHome®