From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Open bug analysis
Date: Mon, 17 Feb 2014 18:36:06 +0100 [thread overview]
Message-ID: <53024886.1030902@mind.be> (raw)
In-Reply-To: <20140213195254.0b17b5bf@skate>
On 13/02/14 19:52, Thomas Petazzoni wrote:
>> Support for kernel signed modules
>> > https://bugs.busybox.net/show_bug.cgi?id=6764
>> > This bug report has a patch attached, and both Yann and me asked the
>> > submitter to send it to the list, but without response. It's still
>> > pretty recent though, so hopefully the submitter comes back to us. If
>> > not, someone could adopt it and resend to the list.
> Yes, I remember looking at this patch, and looking a bit inside the
> kernel for some details about why signed modules cannot be stripped. If
> I remember correctly, it is indeed true that they cannot be stripped.
> It's a bit annoying if they are built with debugging symbols...
>
This is something that can only be solved on the kernel side, I think -
modules have to be stripped before signing. Up to now, the kernel didn't
need support for that because stripping was done by the packagers. But
now that module signing has been added, the kernel will have to do the
stripping.
So I'd suggest to point the bug reporter to the maintainers of MODULES_SIG.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-02-17 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 15:30 [Buildroot] Open bug analysis Thomas De Schampheleire
2014-02-13 18:52 ` Thomas Petazzoni
2014-02-14 20:39 ` Thomas De Schampheleire
2014-02-17 17:46 ` Arnout Vandecappelle
2014-02-19 16:02 ` Thomas De Schampheleire
2014-02-19 21:16 ` Arnout Vandecappelle
2014-02-17 17:36 ` Arnout Vandecappelle [this message]
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=53024886.1030902@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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