-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSSL copyright? #4
Comments
ACK. We'd probably take the (lib)OQS marking route. Looking at that again, though, |
In liboqs for files we created, we did not put individual license information in each file beyond the SPDX-License-Identifier header, but there was a LICENSE.txt at the root which contained that information. I think that would be okay here. |
Resolved with d6223cb |
You missed a spot 😉 oqs-provider/test/oqs_test_groups.c Lines 17 to 24 in d6223cb
|
Thanks for the catch. And it was more than one. Lesson: No change too small to not botch it :-( Hopefully #5 gets this right. I won't bother you to review it (but won't stop you :-) |
[ahem] I might look over your virtual shoulder a little now and then. Just the fact that others are already playing with external provider is exciting |
There are a number of files in oqsprov/ that have the OpenSSL copyright boilerplate, which gives copyright to the OpenSSL Authors, which I understand is historical, since this was previously a patchset for OpenSSL proper.
I don't think that's something you want at this point, and I can't see anything wrong with simply removing that boilerplate. What you still have in there that could remind anyone of the built-in OpenSSL providers, it's mostly bread-and-butter lines that are only vaguely similar.
The text was updated successfully, but these errors were encountered: