[License-discuss] 3-clause BSD with additional clause forbidding key disclosure

Zluty Sysel zluty.sysel at gmail.com
Thu Feb 5 13:16:06 UTC 2015


Hi there,

On Thu, Feb 5, 2015 at 12:27 PM, Simon Phipps <webmink at opensource.org> wrote:
>
>
> On Wed, Feb 4, 2015 at 12:24 PM, Zluty Sysel <zluty.sysel at gmail.com> wrote:
>>
>>
>> The issue however is that there is a certain reluctance not to include
>> this in the source code license, since one of the .c files contains a
>> very distinct placeholder (set to NULL) for the Private Key in it. The
>> clause in the license would serve as a reminder that those Private
>> Keys (which sometimes are shared across all employees of a single
>> company) are not redistributable even when the source code contains
>> one (albeit a NULL development one). Since Private Keys are
>> distributed in a fashion that makes it difficult for them to be
>> attached to a license, the company wants to include this in each
>> source code file so that users do not inadvertently commit to public
>> repos with the Private Key set.
>
>
> Surely this is a matter to handle via a 1:1 contract with your customer?  I
> have doubts that the additional restriction you are proposing is
> OSD-compliant.

Thanks for the reply.
Yes, and they do have a contract with each customer that receives the
Private Key, along with the source code that goes with it.
Could you however elaborate on why the additional restriction would
not be OSD-compliant? Do you think it could be reworded so that it
does become compliant?

Thanks,

Zluty



More information about the License-discuss mailing list