[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EE2191E.8070107@linux.intel.com>
Date: Fri, 09 Dec 2011 06:20:14 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: David Howells <dhowells@...hat.com>
CC: James Morris <jmorris@...ei.org>,
linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
linux-kernel@...r.kernel.org, dmitry.kasatkin@...el.com,
zohar@...ux.vnet.ibm.com, alan@...rguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/9/2011 1:17 AM, David Howells wrote:
> James Morris <jmorris@...ei.org> wrote:
>
>>> Could you pull my module signing code into the security tree?
>>> The patches can be viewed here:
>>
>> I'm getting this build error:
>>
>> make[1]: *** No rule to make target `kernel.pub', needed by
>> `kernel/modsign-pubkey.o'. Stop.
>
> If you turn module signing on, you have to supply keys for it to
> sign things with and to later verify the signature...
>
> I wonder what the best way to deal with that is... I guess make
> allyesconfig and make allmodconfig are going to break otherwise.
the best way to deal is to have KBUILD generate a key on demand ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJO4hkeAAoJEEHdSxh4DVnEWZoIAIJ8MvXcW6B7MbO5V8J7RjDc
h04/xt6UXdg/IZqOFNvVSxNHgfNR2PeRHpNH6kbi8ftX4rp18U7n1y6+WHoMPEHQ
s7+NZQGzhh6TZeVzzAKIKLASnbDIysf8N6eKt0wRRygg3ipj891kMDCLKrkPY3sj
9NL6xOp7uo6p0C9V70UXmO2tqwvtlKnIcD+DcCalnJN+9/pBbhnm13vGFIbTJYsr
uB38DHG4klJceRX+S3CUjFIub1YzW72TevBsenSLdCLBXOHKI/YXqX5uDZyl9pal
nguULAR4Blmv61xN7XJyIJLUmjjy4K7ppR1zxePGVGIalaDqs60PDKJ6ipHoL6o=
=gfR7
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists