linux-kernel - Re: [RFC] fiemap tester

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: <20090511193036.GE21518@mit.edu>
Date:	Mon, 11 May 2009 15:30:36 -0400
From:	Theodore Tso <tytso@....edu>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Josef Bacik <josef@...hat.com>, linux-fsdevel@...r.kernel.org,
	sandeen@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC] fiemap tester

On Mon, May 11, 2009 at 10:54:50AM -0700, Randy Dunlap wrote:
> 
> Given that we are not lawyers:
> 
> The current kernel tree contains >3500 files that contain the phrase
> "All Rights Reserved".  Are they a problem?

Yes, but how many of them are followed with a GPL licensing statement?
And presumably we have a signed-off-by chain that which includes
someone asserting that they have followed the Developer's
Certification of Origin rules.  (That being said, it's usually better
if the All Rights Reserved is removed, after getting explicit
permission from the original copyright owner to make it available
under a GPLv2 license.)

The issue with the xfstests tree is the *only* copyright permission
statement is "All Rights Reserved", and while there is an oral
assertion from SGI that it was supposed to be released under an open
source license, there is nothing in writing or in the source
distribution indicating this, and it wasn't clear to me whether this
oral assurance happened before or after SGI was purchased by
Rackspace.

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