linux-kernel - Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

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.DEB.2.20.1712301155260.1899@nanos>
Date:   Sat, 30 Dec 2017 12:02:45 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Theodore Ts'o <tytso@....edu>
cc:     Joe Perches <joe@...ches.com>,
        Philippe Ombredanne <pombredanne@...b.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        Jonathan Corbet <corbet@....net>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@....de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <rob.herring@...aro.org>,
        Jonas Oberg <jonas@...e.org>, xfs <linux-xfs@...r.kernel.org>,
        Charlemagne Lasse <charlemagnelasse@...il.com>,
        Carmen Bianca Bakker <carmenbianca@...e.org>,
        "Darrick J. Wong" <darrick.wong@...cle.com>,
        Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe
 how to properly identify file licenses

On Fri, 29 Dec 2017, Theodore Ts'o wrote:
> On Fri, Dec 29, 2017 at 08:19:59AM -0800, Joe Perches wrote:
> > 
> > Has it been legally reviewed and accepted that removal
> > of the BSD license text from individual source files is
> > appropriate and meets the legal requirements of
> > following the BSD license on a per-file basis?
> > 
> > And if so, who did this review?
> > 
> > Is there any license that does not allow removal of the
> > license text and does not allow simple substitution of
> > the SPDX license identifier in each individual file?
> 
> The work to use SPDX lines instead of individual licenses was done by
> Greg K-H in close consultation with Linux Foundation counsels, so I
> would assume that they did look at that particular issue.
> 
> IANAL, but I've talked to lawyers about this issue, and in my
> experience if you talk to three lawyers you will easily get six
> opinions.  As far as I know, none of the licenses explicitly say
> copyright license must be on each file.  Just that the distribution of
> source must include the copyright and license statement.  Exactly how
> that is done is not explicitly specified.

Aside of that we are not removing anything, except the obvious one liners
like

	This file is licensed under GPLV2

	For licensing see COPYING

and similar constructs. Replacing the full boilerplate text is done by
talking to the respective copyright holders, which usually involves lawyers
when the copyright holder is a corporate. See for example:

commit 987b154983f0e70b02edf6fc75fcc2f6e6d670b9
Author: Martin Schwidefsky <schwidefsky@...ibm.com>
Date:   Mon Dec 4 10:57:02 2017 +0100

    s390: Remove redudant license text

where the removal has been done by IBM in files copyrighted by IBM.

Thanks,

	tglx