On Wed, Feb 4, 2015 at 12:24 PM, Zluty Sysel <[email protected]> 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. S.
_______________________________________________ License-discuss mailing list [email protected] http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss
