From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Compilation Error
Date: Tue, 19 Aug 2014 11:24:58 +0200 [thread overview]
Message-ID: <1408440298.21896.22.camel@x220> (raw)
In-Reply-To: <1408440180.21896.20.camel@x220>
[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 at 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
next prev parent reply other threads:[~2014-08-19 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 6:33 Kernel Compilation Error Niamathullah sharief
2014-08-19 7:21 ` Pramod Gurav
[not found] ` <1408434539.21896.7.camel@x220>
2014-08-19 7:52 ` Paul Bolle
[not found] ` <CAMf-jSkwpSGnFEfyKJyZgdNpZHdjcTcHwoegRFbUnW-F7gsz4A@mail.gmail.com>
[not found] ` <CACZhsRiwAbaQYKYE918spfv6R_e3F=+sYMxMXHg5MOwrU9FLYg@mail.gmail.com>
[not found] ` <1408440180.21896.20.camel@x220>
2014-08-19 9:24 ` Paul Bolle [this message]
2014-08-20 4:03 ` Niamathullah sharief
2014-08-20 7:48 ` Paul Bolle
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=1408440298.21896.22.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).