linux-kernel - Re: [PATCH] MODSIGN: Discard previous signature when signing modules

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] [day] [month] [year] [list]

Message-ID: <515233C8.40205@suse.cz>
Date:	Wed, 27 Mar 2013 00:48:24 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	David Howells <dhowells@...hat.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MODSIGN: Discard previous signature when signing modules

On 27.3.2013 00:34, David Howells wrote:
> Michal Marek <mmarek@...e.cz> wrote:
> 
>> The format only supports one signature, so discard any previous
>> signature before signing the module.
> 
> That's not totally true.  The format does not preclude multiple signatures.
> You can just add another signature block on the end that signs everything
> inside of that, including all previous signatures.  The alteration to the code
> to check all of them would be very small, I think.

The question is if this would be useful and desired, as opposed to
supporting a list of signatures that all sign the *same* message. My bet
is that such chain of signatures is more likely going to indicate error
than intention. But I don't care much, I haven't run into this myself, I
just thought that others migh do.

Michal
--
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/