linux-kernel - Re: A proposal

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]

Date:	Thu, 03 Aug 2006 11:08:04 -0700
From:	Zachary Amsden <zach@...are.com>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>, greg@...ah.com,
	Andrew Morton <akpm@...l.org>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Jack Lo <jlo@...are.com>
Subject: Re: A proposal - binary

Arjan van de Ven wrote:
> Hi,
>
> you use a lot of words for saying something self contradictory. It's
> very simple; based on your mail, there's no reason the VMI gateway page
> can't be (also) GPL licensed (you're more than free obviously to dual,
> tripple or quadruple license it). Once your gateway thing is gpl
> licensed, your entire proposal is moot in the sense that there is no
> issue on the license front. See: it can be very easy. Much easier than
> trying to get a license exception (which is very unlikely you'll get)...
>
>
> Now you can argue for hours about if such an interface is desirable or
> not, but I didn't think your email was about that.
>   

Arjan, thank you for reading my prolific manifesto.  I am not arguing 
for the interface being desirable, and I don't think I'm being self 
contradictory.  There was some confusion over technical details of the 
VMI gateway page that I wanted to make explicit.  Hopefully I have fully 
explained those.  I'm not trying to get a license exemption, I'm trying 
to come up with a model that current and future hardware vendors can 
follow when faced with the same set of circumstances.

It was not 100% clear based on conversations at OLS that open-sourcing 
the VMI layer met the letter and intent of the kernel license model.  
There were some arguments that not having the source integrated into the 
kernel violated the spirit of the GPL by not allowing one to distribute 
a fully working kernel.  I wanted to show that is not true, and the 
situation is actually quite unique.  Perhaps we can use this to 
encourage open sourced firmware layers, instead of trying to ban drivers 
which rely on firmware from the kernel.

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