linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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: <alpine.LFD.0.98.0706142118410.14121@woody.linux-foundation.org>
Date:	Thu, 14 Jun 2007 21:23:04 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Michael Poole <mdpoole@...ilus.org>
cc:	Daniel Hazelton <dhazelton@...er.net>,
	Alexandre Oliva <aoliva@...hat.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>,
	"david@...g.hm" <david@...g.hm>,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Thu, 14 Jun 2007, Michael Poole wrote:
> 
> If the signature is one that serves to indicate origin, to detect
> tampering, or the other things you mentioned, the program's binary is
> useful when separated from the signature.  My objection arises when a
> functionally equivalent binary -- including advertised functions such
> as "runs on platform XYZ" -- cannot be produced from the distributed
> source code.

Ahh.

Ok, that's a totally different issue, and is one where I heartily agree 
with you. I would actually *love* for the GPL (any version) to have a 
"guarantee of authenticity", where if you distribute a binary, there has 
to be some documented way to get *exactly* that binary out of the source 
code that got distributed.

Of course, SHA1's can be used to verify that, although, quite frankly, I'd 
expect that a simple "cmp" would be the more straightforward approach.

So the "verification" can be used both to lock down a particular binary 
_and_ to authenticate that the binary really came from the source code it 
was claimed to come from.

Of course, in practice, it's actually really nasty to do that 
verification. Many compilers actually do things like insert date-stamps in 
the object files etc. So it's probably not all that practical.

			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/