linux-kernel - Re: RFC: sign the modules at install time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFyVxE-Y66kuvUujD-8Kxef=K-BSsNEStAL-TacPAUVgrQ@mail.gmail.com>
Date:	Wed, 17 Oct 2012 17:06:37 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Josh Boyer <jwboyer@...il.com>
Cc:	David Miller <davem@...emloft.net>,
	Rusty Russell <rusty@...tcorp.com.au>,
	David Howells <dhowells@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: RFC: sign the modules at install time

On Wed, Oct 17, 2012 at 4:44 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I'll send out a fixed patch asap,

Ok, this is not pretty, and I think it generates the .signer and
.keyid files at the wrong time.

I do the kernel build as a regular user, and just "make install" as
root, and now it generates those turds as root-owned files. Ugly.

But I took the code from the parts I had deleted in my over-eager
"delete as much as possible of the strip-and-sign code", and moved it
to the install phase. So this is the obvious quick fix, but I'm sure
there are better solutions.

                    Linus

Download attachment "patch.diff" of type "application/octet-stream" (6049 bytes)