Re: building and signing modules

[Andrew Szymkowiak]

Adam,    Thanks for your reply, although it isn't relevant.  Although I do know how to make RPM packages, that isn't the GPG key I meant - I'm not trying to forge SL RPMs.  There is a key pair that is used to crytographically verify loadable modules.  In the  RedHat source tree, these come as kernel.pub and kernel.sec , and the public key is also in C include source form in crypto/signature/key.h.   I was looking for the versions of those files used during the building of the SL kernels.  In the meantime, although not my first choice, I'm trying to locally build the kernel with my own keypair (the build scripts generate a new pair when started), and am currently running into build errors during build of fs/cifs/cifs.o and drivers/ata/sata_sil.c, which I have yet to figure out how to get by... Thanks,     Andy S Adam Miller wrote: On Tue, Mar 29, 2011 at 04:40:11PM -0400, Andrew Szymkowiak wrote: (sorry if this is already widely known - I did Google and search the mailing list archives first, but without success...) I need to build some modules for my (spanking-new) SL6.0 installation. But I don't seem to be able to build with the proper GPG module signing key. Is there some package I can fetch which will supply them? I thought they would be in "kernel-devel", but I don't seem to see it there. I fetched the vendor's kernel source package, but that, as you may imagine, has a RedHat key, and my kernel refuses to load modules built against that tree, even with the SL .config ... Thanks, Andy S. I'm going to go out on a limb and pretend that you know how to build RPM packages and therefore won't address that too closely, though if you aren't familiar then I recommend GURU Labs rpm guide[0] If you need to sign custom built rpms then you can follow this short how-to[1] but if you are trying to sign your packages with the actual Red Hat signing key (I could have read what you wrote incorrectly, if so then disregard) then that's just not going to happen. Its a secret key for a reason. What you need to do is import the appropriate public keys into rpm for your system (yum can automate some of this, but its not a difficult process.). Hope this helps, -AdamM [0] http://www.gurulabs.com/downloads/GURULABS-RPM-LAB/GURULABS-RPM-GUIDE-v1.0.PDF [1] http://fedoranews.org/tchung/gpg/