[License-review] For Approval: The Cryptographic Autonomy License

VanL van.lindberg at gmail.com
Fri May 10 21:19:39 UTC 2019

On Fri, May 10, 2019 at 1:46 PM Bruce Perens <bruce at perens.com> wrote:

> On Fri, May 10, 2019 at 7:59 AM VanL <van.lindberg at gmail.com> wrote:
>> I assume that most of the content of this message is deliberate
>> overstatement in the service of either humor or sarcasm.
> Not at all. It illustrated from the non-programmer, non-lawyer's
> perspective just how impossible compliance is. *They can't do it on their
> own. *The way I wrote that is exactly what they would face.

I am not sure how to respond when the hypothetical is "I am a person
providing a network service, but I have no idea what I am doing, and I
won't ask for help, so I might do something wrong."

I'll reiterate: For the ordinary developer, the CAL means:

If you make CAL-licensed software available in any way to a person, then
you must also provide that person 1) a copy of the license, 2) access to
the software source code, and 3) a copy of any of the data used with
software that the person has given to you, should that data still be


This discussion seems to be going around in circles. You have made a number
of points at various times:

1) You believe that software is not susceptible to public performance, or
if it is, not through the API.
2) You believe an operator's ability to lock down the data they receive
from end users is core to the OSD and to the concept of Free Software.
3) You believe that the CAL is too complicated and won't work.

We fundamentally disagree on these points. We disagree as to whether they
are true in general as well as to their applicability to CAL's submission
to the board.

I have tried to point out what I see as flaws in your analysis, but it
seems that we are really at the point where we are debating beliefs. I have
deep respect for you and your long experience here, and so I am not sure
that further reiteration or rebuttal will bring any more light.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20190510/0d12fba7/attachment.html>

More information about the License-review mailing list