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  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:   Fri, 10 Nov 2017 21:10:28 +0000
From:   Alan Cox <gnomes@...rguk.ukuu.org.uk>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Dave Chinner <david@...morbit.com>,
        "Darrick J. Wong" <darrick.wong@...cle.com>,
        Christoph Hellwig <hch@...radead.org>,
        Eric Sandeen <sandeen@...hat.com>,
        xfs <linux-xfs@...r.kernel.org>, linux-kernel@...r.kernel.org
Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license
 identifier to files with no license

> When a file does not have a license, again, all lawyers I have worked
> with said it is implicitly GPLv2

I am surprised that they did not immediately see the fact that since the
code contributor was not neccessarily the rights holder you could make no
assumption as to the actual licencing beyond it being GPL compatible (or
having a right to sue whoever put it there).

Did you explain the contribution process sufficiently clearly ?

> Again, no, the copyright was not changed.  Whom ever held the original
> copyright still holds it today.

On the contrary if it was implicitly LGPL you've just exercised the right
to make it GPL and messed it up for others. In the other cases your error
is probably legally actionable in certain jurisdictions if someone was so
unpleasantly minded.

Alan

Powered by blists - more mailing lists