Static nested auto distance measurement for nonces #2586
Merged
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.
The distance between nonces was hardcoded in the static nested attack, but in that way the attack failed against cards with a different distance between nonces (other than 160 or 0). Now we measure the distance before making the attack, we do a first auth, then a nested auth on the same sector and finally another nested auth on the same sector. In this way we can calculate the distances (nt2 - nt1) and (nt3 - nt1) and use them to make the attack. It was successfully tested on both cards with 160 and 0 distance and it takes the same amount of time as before, so we can conclude that the attack should now work even against cards (present or future ones) with different distances