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: <c8140ea3-8731-8084-47dd-8819b4b4df6a@gmail.com>
Date:   Wed, 7 Oct 2020 16:53:54 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Bob Ham <rah@...trans.net>, Stefan Agner <stefan@...er.ch>,
        Peter Geis <pgwipeout@...il.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Thierry Reding <thierry.reding@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Matt Merhar <mattmerhar@...tonmail.com>,
        Stephen Warren <swarren@...dotorg.org>,
        Leonardo Bras <leobras.c@...il.com>,
        Michael Brougham <jusplainmike@...il.com>,
        linux-tegra@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Lukas Rusak <lorusak@...il.com>
Subject: Re: [PATCH v3 0/3] Support NVIDIA Tegra-based Ouya game console

07.10.2020 16:36, Bob Ham пишет:
> Hi all,
> 
> The Bluetooth controller driver sent to linux-input by Lukas Rusak
> (CC'd) is a bit of a concern.  Here is the original driver:
> 
> https://github.com/ouya/ouya_1_1-kernel/blob/master/drivers/hid/hid-ouya.c
> 
> and you can see that there is no SPDX header, no license information and
> no MODULE_LICENSE declaration.  I'd previously noticed this as a
> possible cause for concern in upstreaming the driver.
> 
> Meanwhile, Lukas's driver is clearly derived from the Ouya Inc. driver
> and even retains the Ouya Inc. copyright notice line.  However, Lukas's
> driver now has a MODULE_LICENSE("GPL") declaration added.
> 
> Lukas, did you get clear permission to license the driver as GPL?
> 
> Alternatively, kernel developers with greater legal or Ouya knowledge,
> is this actually a concern or is it nothing to worry about?

Hello Bob,

That can't be a problem because:

1. Ouya Inc. doesn't exists anymore.

2. If code was officially published, then this implies that it can be
derived.

3. Ouya's driver uses kernel symbols that are explicitly marked as
GPL-only, see hid_open_report for example. Hence Ouya's driver inherents
the GPL license.

4. Lukas's patch doesn't remind the original code at all.

5. In practice nobody cares about legal much if money aren't involved.
Even if it happened that driver was 100% violating some copyrights, then
it either won't be accepted to upstream or will be removed by request
from the copyrights holder.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ