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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFzv=Kaa7e2jReyuJq-X7BTpSjS8V2D02y5exc_r2ZM_3w@mail.gmail.com>
Date:	Wed, 17 Oct 2012 16:44:54 -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:25 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> It really should work fine with the much simplified module-signing
> rules too.

Actually, my "much simplified modules-install" is a bit broken.

It worked for me last time (I'm running that kernel and modules now),
but I  just triggered a

  INSTALL Documentation/connector/cn_test.ko
  Can't read Signer name

error.

My patch is broken, and I simplified a bit *too* much. In particular
the .signer and .keyid logic got thrown out with the bathwater.

I just hadn't noticed until I did a "git clean", because the old
signer/keyid files had stayed around, hiding the breakage.

I'll send out a fixed patch asap,

            Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/