Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

Please clarify licening information #14

Open
xnox opened this issue Feb 28, 2018 · 1 comment
Open

Please clarify licening information #14

xnox opened this issue Feb 28, 2018 · 1 comment

Comments

@xnox
Copy link

xnox commented Feb 28, 2018

Appears to be an empty file, please provide contents or remove this file. If this file was added to simply pacify autotools, maybe using AM_INIT_AUTOMAKE([foreign]) option is a better way to remove the autotools warnings. Ditto other empty files, e.g. NEWS, AUTHORS.

Has an odd copyright statement, and license. My understanding is that the OpenSSL project is not the copyright holder, but IBM is. Also OpenSSL project is undergoing a license transition to Apache v2, thus the OpenSSL license is no longer preferred license for the upstream project. Have you considered relicensing under Apache v2? Is that even possible?

Also I am failing to find any source files, that are supposedly covered by the LICENSE text.

Above files do not appear to have any license mentioned at the top of the file in a comment header. By default, that implies that these are proprietary.

@dodys
Copy link
Contributor

dodys commented Feb 28, 2018

Hi Dimitri,

Thanks for your feedback.

openssl-ibmpkcs11 is a rather old project with OpenSSL license. As you can see the state right now of some files are not as it should. But we didn't touch those files for now since we are moving on to relicensing this code as Apache v2.

We have all the changes you mentioned that are needed (based on relicensing under Apache v2) stored locally but we cannot make it public it as we are still hitting some legal approvals. So this relicensed version won't make into Ubuntu 18.04.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants