linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Message-ID: <20171113082855.GA22719@kroah.com>
Date:   Mon, 13 Nov 2017 09:28:55 +0100
From:   Greg KH <greg@...ah.com>
To:     Charlemagne Lasse <charlemagnelasse@....de>
Cc:     linux-kernel@...r.kernel.org,
        Charlemagne Lasse <charlemagnelasse@...il.com>,
        Jonas Oberg <jonas@...e.org>
Subject: Re: [RESENT,PATCH 0/5] licenses: Create LICENSES directory

On Sun, Nov 12, 2017 at 12:23:43PM +0100, Charlemagne Lasse wrote:
> 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.

<snip>

Nice, idea, we were wanting to do this as well, see this patch series
from Thomas that does much the same, but also helps explain the SPDX
tags we have been putting in the kernel source tree:
	https://lkml.org/lkml/2017/11/12/110

thanks,

greg k-h