[License-discuss] Fwd: Intimacy in open source (SSPL and AGPL)

Bruce Perens bruce at perens.com
Fri Jan 18 22:41:29 UTC 2019

---------- Forwarded message ---------
From: Bruce Perens <bruce at perens.com>
Date: Fri, Jan 18, 2019 at 2:41 PM
Subject: Re: Intimacy in open source (SSPL and AGPL)
To: Lawrence Rosen <lrosen at rosenlaw.com>
Cc: Legal Network <ln at lists.fsfe.org>, John Cowan <cowan at ccil.org>,
Lawrence Rosen <lrosen at rosenlaw.com>

As far as I can tell, CCS (Complete and Corresponding Source code, the
nomenclature used by SFC in enforcement) depends on the terms of the
license rather than being something the community can define for all
licenses. The FSF definition appears to be all that you need to build,
install, and run the program as it is intended to be run by the provider of
the binary, with all device capabilities enabled (if this is an embedded
device). This thus can include a cryptographic key, although SFC seems to
have acknowledged that key and device capability requirements can be
enforced for if GPL3 is involved, and not GPL2.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20190118/eb03eced/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1393 bytes
Desc: not available
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20190118/eb03eced/attachment.png>

More information about the License-discuss mailing list