linux-kernel - [RESENT,PATCH 0/5] licenses: Create LICENSES directory

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-next>] [day] [month] [year] [list]

Message-Id: <20171112102729.17163-1-charlemagnelasse@outlook.com>
Date:   Sun, 12 Nov 2017 12:23:43 +0100
From:   Charlemagne Lasse <charlemagnelasse@....de>
To:     linux-kernel@...r.kernel.org
Cc:     greg@...ah.com, Charlemagne Lasse <charlemagnelasse@...il.com>,
        Jonas Oberg <jonas@...e.org>
Subject: [RESENT,PATCH 0/5] licenses: Create LICENSES directory

From: Charlemagne Lasse <charlemagnelasse@...il.com>

Hi,

the FSFE created some best practices for the (re)distribution of open source
software [1]. They partially talk about the the SPDX-License-Identifier tag
which Greg Kroah-Hartman is already using to clarify the copyright status of
some source files. But they also recommend to ship the complete license texts
in a LICENSES directory when they are not already included in the source files.

The Linux kernel itself is licensed under the GPL-2.0 but also references other
licenses in some source files without the complete license text. I went through
the SPDX-License-Identifier tags to find which ones are referenced and should
be included.

This is only a start and I have not yet touched the COPYING file at all. This
file should most likely also be included in the LICENSES/ directory with some
name like GPL-2.0_Linux-syscall-note.txt. Maybe Jonas Oberg could lend me his
expertise again and tell us whether this name would be appropriate and whether
it should contain only the exception (the WITH part of "GPL-2.0 WITH
Linux-syscall-note") or the complete content of the current COPYING file.

Thanks,
Charlemagne Lasse

[1] https://reuse.software/practices/

Charlemagne Lasse (5):
  licenses: Add verbatim LGPL-2.0 license text
  licenses: Add verbatim LGPL-2.1 license text
  licenses: Add verbatim MPL-1.1 license text
  licenses: Add verbatim GPL-1.0 license text
  licenses: Add verbatim GPL-2.0 license text

 LICENSES/GPL-1.0.txt  | 251 +++++++++++++++++++++++++
 LICENSES/GPL-2.0.txt  | 339 ++++++++++++++++++++++++++++++++++
 LICENSES/LGPL-2.0.txt | 481 +++++++++++++++++++++++++++++++++++++++++++++++
 LICENSES/LGPL-2.1.txt | 502 ++++++++++++++++++++++++++++++++++++++++++++++++++
 LICENSES/MPL-1.1.txt  | 469 ++++++++++++++++++++++++++++++++++++++++++++++
 5 files changed, 2042 insertions(+)
 create mode 100644 LICENSES/GPL-1.0.txt
 create mode 100644 LICENSES/GPL-2.0.txt
 create mode 100644 LICENSES/LGPL-2.0.txt
 create mode 100644 LICENSES/LGPL-2.1.txt
 create mode 100644 LICENSES/MPL-1.1.txt

PS: I had to resent this because the LKML seems to have rejected this mail.
Sorry for the other recipients for receiving the mail twice.

-- 
2.11.0