i TRIED TO SOLVE THIS AND I AM UNABLE TO DO IT.
Totally confused. On Tue, Aug 19, 2014 at 2:54 PM, Paul Bolle <pebo...@tiscali.nl> wrote: > [Send this to the correct list again. What a mess...] > > On Tue, 2014-08-19 at 11:23 +0200, Paul Bolle wrote: > > [Have you've been lectured on top posting already?] > > > > On Tue, 2014-08-19 at 14:30 +0530, Niamathullah sharief wrote: > > > I didnt find the place to enable CONFIG_MODULE_SIG_ALL > > > > > > Its like > > > > > > "ifdef CONFIG_MODULE_SIG_ALL > > > MODSECKEY = ./signing_key.priv > > > MODPUBKEY = ./signing_key.x509 > > > export MODPUBKEY > > > mod_sign_cmd = perl $(srctree)/scripts/sign-file > > > $(CONFIG_MODULE_SIG_HASH) $(MODSECKEY) $(MODPUBKEY) > > > else > > > mod_sign_cmd = true > > > endif > > > export mod_sign_cmd > > > " > > > > Personally I do > > $ git grep -nw MODULE_SIG_ALL > > init/Kconfig:1857:config MODULE_SIG_ALL > > init/Kconfig:1866: depends on MODULE_SIG_FORCE && > !MODULE_SIG_ALL > > > > But you can search for CONFIG_MODULE_SIG_ALL in the interface of "make > > menuconfig" too. > > > > (I noticed I have both signing_key.priv and signing_key.x509 in the root > > of my kernel tree. They appear to be, well, faux: grep for > > slartibartfast@magrathea.h2g2 to see what I mean. These keys are months > > old, and survived numerous invocations of "make clean". I don't remember > > which command generated them, sorry.) > > > > > > Paul Bolle > > >
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
