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

[new feature/improvement] new user function iterated as the do_one_computation() but not timed #18

Open
matbok opened this issue Jun 9, 2021 · 2 comments

Comments

@matbok
Copy link

matbok commented Jun 9, 2021

Consider adding a new function (to be developed by the dudect user), similar to the do_one_computation() but to be executed before it and not to be included in the measurement.
I think I'll implement it.
If you want, I could share it.

@oreparaz
Copy link
Owner

oreparaz commented Jun 7, 2023

can you please explain what would be the use of it? normally that computation should be done before the whole batch of measurements (for example, in key scheduling).

@matbok
Copy link
Author

matbok commented Jun 7, 2023

It's been a long time, so I hope to well remember... But consider, for example, that I would like to validate the constant-time-ness of the AEAD auth. tag generation, but before I need to init/append some information that I would not want to consider in the measurement. in that new function I would call the init and append, leaving the tag generation in the do_one_computation() function.
Did I answered to you?

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

No branches or pull requests

2 participants