Add a test about a constant time equal function #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I tried to use your framework to assert that a function is constant-time. The goal of this PR is not to add something new into this repository but to have some explanation - may be, I misunderstand something. Here we have a "constant-time"
memcmp
function (available here) and I tried to run your framework on it.However, with
dudect_simple_O0
, I reached the point where the program tell me:The situation differs when we increase the number of samples with
MEASUREMENTS_PER_CHUNK
. In this situation, evenmemcmp
never reaches theProbably not constant time
. By this way, I can not really reproduce what you were saying in our paper locally - I currently test that on a bare-metal server, an Intel Xeon CPU D-1531 @ 2.20Ghz.May be I do something wrong or I misinterpret results 😕 . Thanks!