From: Arjan van de Ven <arjan@linux.intel.com>
To: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
jmorris@namei.org, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org,
dmitry.kasatkin@intel.com, zohar@linux.vnet.ibm.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing
Date: Sat, 10 Dec 2011 10:54:48 -0800 [thread overview]
Message-ID: <4EE3AAF8.4090609@linux.intel.com> (raw)
In-Reply-To: <CA+MtwOEHYu1z8TLXv7jwCKfgavaGX7EWXmxq2xs6b0jbujy35g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/10/2011 3:42 AM, Arkadiusz Miśkiewicz wrote:
> On Wed, Dec 7, 2011 at 3:47 PM, David Howells <dhowells@redhat.com>
> wrote:
>>
>> Hi James,
>>
>> Could you pull my module signing code into the security tree?
>> The patches can be viewed here:
>>
>> http://git.kernel.org/?p=linux/kernel/git/dhowells/linux-modsign.git;a=shortlog;h=refs/heads/devel
>
>>
> If I understand it is not possible to sign modules after they are
> built and load keys without actually rebuilding kernel?
only if the end user chooses to enforce the signature.
>
> For distro kernel the public and secret keys have to be available
> publicly, right? Otherwise people using distro kernels won't be
> able to build own signed modules for use with that distro kernel.
That's a distro choice, but... again:
only if the user chooses to enforce the signature.
Very few people actually build their own modules, and for the people
that don't, they can chose to harden their server by only allowing
signed (eg distro shipped) modules.
For those who prefer to build a few other things and still want
security, they can also rebuild the kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJO46r4AAoJEEHdSxh4DVnE39cIALufzQHXgIycaRnImtEWSPrq
PN5ac052lb59YGEbSsUF/Er/SOLfdwJQbD2Gz2/0QCPWfpb64pozDDwFh1IhvvEp
q4D/1wAJBXOaEj1FESPxHkbwvdYe701pgLq0ERQu4SSx69wNMFXNMmp06Jbxuujp
ZRhQcuJQsd76mJi8MZ2f9qnzR+3MQ9zFGK2alqDfb0WiELBc+Cz1nj2tCXrB5AFa
7osPZJK2iBcD+2sfryMEuJWxOjWxm/ZiEz2oIV0vRtnozVEAIYaeJ2Xe6n72Zj3W
AuAGbnfE9j7yzBVz+9KOZEd2DW7MF7Xns4Vn1/1y6W0h0RsXTq15LIXApJL760I=
=fCSX
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-12-10 18:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 14:47 [GIT PULL] Crypto keys and module signing David Howells
2011-12-09 4:05 ` James Morris
2011-12-09 9:17 ` David Howells
2011-12-09 9:35 ` James Morris
2011-12-09 14:20 ` Arjan van de Ven
2011-12-09 14:31 ` James Morris
2011-12-09 18:06 ` David Howells
2011-12-09 18:18 ` Arjan van de Ven
2011-12-09 18:47 ` David Howells
2011-12-09 18:49 ` Arjan van de Ven
2011-12-09 18:59 ` David Howells
2011-12-09 19:41 ` [Keyrings] " Daniel Kahn Gillmor
2011-12-10 9:49 ` Geert Uytterhoeven
2011-12-10 11:42 ` Arkadiusz Miśkiewicz
2011-12-10 12:50 ` David Howells
2011-12-12 14:12 ` Nick Bowler
2011-12-10 18:54 ` Arjan van de Ven [this message]
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=4EE3AAF8.4090609@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=a.miskiewicz@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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.