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:35:03 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Zachary Amsden <zach@...are.com>
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

Zachary Amsden wrote:

> And by NO circumstances, is it required to be a CLOSED source binary
> blob. In fact, why can't it be open?  In the event of a firmware bug,
> in fact, it is very desirable to have this software be open so that
> it can be fixed

You're making a very good argument as to why we should probably
require that the code linking against such an interface, if we
decide we want one, should be required to be open source.

> I think you will see why our VMI layer is quite similar to a
> traditional ROM, and very dissimilar to an evil GPL-circumvention
> device.

> (?) There are only two reasonable objections I can see to open
> sourcing the binary layer. 

Since none of the vendors that might use such a paravirtualized
ROM for Linux actually have one of these reasons for keeping their
paravirtualized ROM blob closed source, I say we might as well
require that it be open source.

As for the evilness of a binary interface - the interface between
kernel and userland is a stable binary interface and is decidedly
non-evil.  I could see a similar use for a stable paravirtualization
interface, to make compatibility between Linux and various hypervisor
versions easier.

As long as it's open source so the thing can be debugged :)

-- 
All Rights Reversed
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ