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
Make public SM2 functions libcrypto private #5670
Labels
branch: 1.1.1
Merge to OpenSSL_1_1_1-stable branch
Milestone
Comments
2 tasks
I can address this but probably will not have time to create a PR until Friday or Saturday. |
Thanks @randombit , @levitte ! |
Hi @randombit - any update on this? |
@mattcaswell Sorry for the holdup, should be able to look at this tomorrow |
@mattcaswell @levitte Fixed in PR #5895 |
randombit
pushed a commit
to randombit/openssl
that referenced
this issue
May 16, 2018
Address issue openssl#5670
mattcaswell
pushed a commit
to mattcaswell/openssl
that referenced
this issue
May 31, 2018
Address issue openssl#5670
Since #5895 was closed, closing this. |
Thank you @levitte @randombit @mattcaswell @richsalz ! 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#4793 added a few public SM2 function that really shouldn't be, They're only used by the EC code and the SM2 functionality should only be reachable through the EVP API.
As a consequence, the two test programs
test/sm2crypttest.c
andtest/sm2sigtest.c
should be viewed as internal and allowed to access those SM2 functions. SM2 through the EVP API is already tested with added data intest/recipes/30-test_evp_data/evppkey.txt
The text was updated successfully, but these errors were encountered: