-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add LMS benchmark #8510
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
base: development
Are you sure you want to change the base?
Add LMS benchmark #8510
Conversation
Signed-off-by: Matthias Schulz <mschulz@hilscher.com>
|
Done now. Just kept for reference: Dear reviewers, |
|
Different versions of uncrustify produce different results. You need to use 0.75.1. We wrote that warning message before 0.76 came out. Now that it's out and we know it produces different results in our code base, I guess we should turn the warning into an error. |
|
Could you trigger the CI tests again. They should pass now. |
15448cc to
6a536df
Compare
|
It seems like there is no progress in this PR. Is there anything else you need from me to get the changes merged? |
|
We will be looking at it. |
|
Happy new year. Any chance to get the PR merged soon? |
|
CI failure because of code style with the below error: |
|
Hey @mschulz-at-hilscher , thanks for the contribution. Are you still keen to get this merged? I have some bandwidth to review it so we can get it over the line. You have CI failures coming from our uncrustify automated code style checks. I took a look at it and can see 4 complaints coming from uncrustify; 3 of them look legitimate, but one of them looks like uncrustify has suffered a glitch. In this case the glitch has occurred on I think the easiest way to fix this is to wrap the code that uncrustify flags as a false positive with an Once that is done, just run |
|
Hi Tom, |
|
Hi @mschulz-at-hilscher , is there any interest still from you to fix the code style issue? |
Signed-off-by: Matthias Schulz <mschulz@hilscher.com>
Done. |
Description
Added a benchmark for the LMS post-quantum-safe stateful-hash public-key signature scheme.
As the private key is limited to a number of signing operations resp. number of one-time private keys, the benchmark stops as soon as it runs out of keys.
I also ran scripts/code_style.py to uncrustify the benchmark.c. Those changes are in the second commit, while the new code is in the first commit.
PR checklist
Please tick as appropriate and edit the reasons (e.g.: "backport: not needed because this is a new feature")