From: Peter Jones <pjones@redhat.com>
To: dhowells@redhat.com
Cc: jwboyer@redhat.com, linux-kernel@vger.kernel.org,
Peter Jones <pjones@redhat.com>
Subject: [PATCH] MODSIGN: Fix documentation of signed-nokey behavior when not enforcing.
Date: Thu, 2 Aug 2012 15:48:30 -0400 [thread overview]
Message-ID: <1343936910-16548-1-git-send-email-pjones@redhat.com> (raw)
jwboyer's previous commit changes the behavior of module signing when
there's a valid signature but we don't know the public key and are in
permissive mode. This updates the documentation to match.
Signed-off-by: Peter Jones <pjones@redhat.com>
Acked-by: Josh Boyer <jwboyer@redhat.com>
---
Documentation/module-signing.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt
index d75d473..8c4bef9 100644
--- a/Documentation/module-signing.txt
+++ b/Documentation/module-signing.txt
@@ -185,7 +185,7 @@ This table indicates the behaviours of the various situations:
MODULE STATE PERMISSIVE MODE ENFORCING MODE
======================================= =============== ===============
Unsigned Ok EKEYREJECTED
- Signed, no public key ENOKEY ENOKEY
+ Signed, no public key Ok ENOKEY
Validly signed, public key Ok Ok
Invalidly signed, public key EKEYREJECTED EKEYREJECTED
Validly signed, expired key EKEYEXPIRED EKEYEXPIRED
--
1.7.11.2
next reply other threads:[~2012-08-02 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:48 Peter Jones [this message]
2012-08-02 22:10 ` [PATCH] MODSIGN: Fix documentation of signed-nokey behavior when not enforcing David Howells
-- strict thread matches above, loose matches on Subject: below --
2012-08-02 19:41 Peter Jones
2012-08-02 19:46 ` Josh Boyer
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=1343936910-16548-1-git-send-email-pjones@redhat.com \
--to=pjones@redhat.com \
--cc=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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