Skip to content
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

Benchmark, SM3: fix full hash testing #7493

Merged
merged 4 commits into from
May 13, 2024

Conversation

SparkiDev
Copy link
Contributor

Description

Test now has an array of hashes.
Use only first hash when testing full digest operation.

Testing

Install SM code.
./configure --enable-sm3
make

Checklist

  • added tests
  • updated/added doxygen
  • updated appropriate READMEs
  • Updated manual and documentation

Test now has an array of hashes.
Use only first hash when testing full digest operation.
@SparkiDev SparkiDev self-assigned this Apr 30, 2024
@SparkiDev
Copy link
Contributor Author

retest this please

@SparkiDev SparkiDev assigned wolfSSL-Bot and unassigned SparkiDev May 1, 2024
@SparkiDev SparkiDev requested a review from wolfSSL-Bot May 1, 2024 01:46
Variables may not be initialized in benchmark test when building for
small stack.
Set the curve explicitly if it is SM2.
Set the key type to signature algorithm to handle SM2.
@SparkiDev
Copy link
Contributor Author

retest this please

1 similar comment
@SparkiDev
Copy link
Contributor Author

retest this please

Copy link
Contributor

@douzzer douzzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks fine, but I can't get a proper read on whether it works because of preexisting defects in the wolfsm code.

I've implemented several tests for it in the usual way, and the initial report is
65a2e5265c-multi-test-log.html.gz

From the looks of it, most of the fixes will be to the wolfsm repo. Assign the wolfsm fixit PR(s) to me when they're ready.

@douzzer douzzer assigned SparkiDev and unassigned wolfSSL-Bot May 9, 2024
Pass around the algorithm id from the private key so that the WOLFSSL or
WOLFSSL_CTX get the correct key format set.
Use different verification context when self-signed certificate with SM2
and SM3 signature but public key OID is ECC.
@SparkiDev
Copy link
Contributor Author

retest this please

@SparkiDev SparkiDev assigned douzzer and wolfSSL-Bot and unassigned SparkiDev May 10, 2024
@SparkiDev
Copy link
Contributor Author

Let me know if there are further clang-tidy fixes required.

@douzzer douzzer merged commit 009ea66 into wolfSSL:master May 13, 2024
115 checks passed
jefferyq2 pushed a commit to jefferyq2/wolfssl that referenced this pull request Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants