Licensing

[sparticvs]

I couldn't find any details about the licensing of the code. I was wondering if you would be able to elaborate or add a license file?

[jbonner6]

Thanks for your interest in this tool! We are happy to license it however you like. LGPL, MIT, BSD - take your pick. We will add details on that soon. Thanks for reminding us.

[sparticvs]

I found there was something of a license in tls_common.h. It looks to be in alignment with a BSD 2-clause license, which I would say is a fine choice.

[kimbo]

bump

[petterreinholdtsen]

Without clear statement on the licensing terms for the code, the fallback is the defaults in copyright law, which will make everyone copying or using this code in breach of copyright. It would thus be good to have license information. Preferable at the top of every source file and with the complete license terms in a separate file in the repository.

If you plan to upstream the code into the Linux kernel, the license need to be compatible with GPL v2. If you plan to submit a proposal for extending POSIX, there might be other requirements for a reference implementation, I do not know.

The lack of clear licensing information will hamper the uptake of this code.