From: Rusty Russell <rusty@rustcorp.com.au>
To: Josh Boyer <jwboyer@redhat.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MODSIGN: Add modules_sign make target
Date: Fri, 02 Nov 2012 13:49:14 +1030 [thread overview]
Message-ID: <87ip9o4rpp.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20121101112535.GL6627@hansolo.jdub.homelinux.org>
Josh Boyer <jwboyer@redhat.com> writes:
> On Thu, Nov 01, 2012 at 06:03:18PM +1030, Rusty Russell wrote:
>> Josh Boyer <jwboyer@redhat.com> writes:
>>
>> > If CONFIG_MODULE_SIG is set, and 'make modules_sign' is called then this
>> > patch will cause the modules to get a signature appended. The make target
>> > is intended to be run after 'make modules_install', and will modify the
>> > modules in-place in the installed location. It can be used to produce
>> > signed modules after they have been processed by distribution build
>> > scripts.
>> >
>> > Signed-off-by: Josh Boyer <jwboyer@redhat.com>
>>
>> It's a bit of a niche case, but applied.
>
> Thanks. Whether you consider RPM built kernels niche or not doesn't
> matter to me. Having this upstream is one less patch we have to carry
> so I appreciate it a lot.
My comment was more that this relies on eu-strip, because we always
sign modules on installation, so you need eu-strip to *unsign* them
(strip won't do it, BTW).
More general would be a modules_install_unsigned target to match this,
but since noone would use it, let's not write it :)
Cheers,
Rusty.
next prev parent reply other threads:[~2012-11-02 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 13:56 [PATCH v2] MODSIGN: Add modules_sign make target Josh Boyer
2012-11-01 7:33 ` Rusty Russell
2012-11-01 11:25 ` Josh Boyer
2012-11-02 3:19 ` Rusty Russell [this message]
2012-11-02 12:48 ` Josh Boyer
2012-11-05 2:11 ` Rusty Russell
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=87ip9o4rpp.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.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