From: Ben Mezger <su@seds.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel module signature now shown on modinfo
Date: Sun, 15 Apr 2018 20:46:57 -0300 [thread overview]
Message-ID: <CANLyGzafq9abCVMnr9CEg+L6PqNVj+EvQLpgtiy3LC2WzGHD4w@mail.gmail.com> (raw)
In-Reply-To: <2917991.7uevoeRHck@dell_xps>
Thanks for the link. It seems that the sign-file utility from the
kernel (scripts/sign-file) has been converted to a .c file and somehow
it produces a different output.
I think if you really want to make sure the module is signed is by
doing a hexdump and perhaps strip the signature out and try to load
it.
Regards,
On 13 April 2018 at 15:32, Mick <michaelkintzios@gmail.com> wrote:
> On Thursday, 12 April 2018 22:47:31 BST Dave Trombley wrote:
>> This has been broken for almost two years; the signature format switched to
>> PKCS#7 and modinfo doesn't support it. It's not as simple as just
>> patching kmod because evidently the kernel change regressed or disrespected
>> the relevent structure in the modules in a way that makes it impossible for
>> kmod to even make sense of. Details here:
>> https://github.com/coreos/bugs/issues/1054
>>
>> -David
>
> Thanks David, I had come across an older bug somewhere, but there was no
> detailed explanation.
>
> --
> Regards,
> Mick
--
Kind regards,
Met een vriendelijke groet,
Ben Mezger
https://seds.nl
PGP: C473 DDC9 D1B1 40AF 2051 1CF6 18C4 6052 1688 92F7
next prev parent reply other threads:[~2018-04-15 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 20:39 [gentoo-user] Kernel module signature now shown on modinfo Ben Mezger
2018-04-12 21:47 ` Dave Trombley
2018-04-13 18:32 ` Mick
2018-04-15 23:46 ` Ben Mezger [this message]
2018-04-13 15:13 ` Mick
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=CANLyGzafq9abCVMnr9CEg+L6PqNVj+EvQLpgtiy3LC2WzGHD4w@mail.gmail.com \
--to=su@seds.nl \
--cc=gentoo-user@lists.gentoo.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