You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a counter sync token which counter is more than 30 behind the highest entered counter of token get accepted. The problem is in the check in IsCountValid function. Wrong limits are used, the MAX_TOKEN_JUMP define is used but that is 64 and not 30.
Regards Jonas
The text was updated successfully, but these errors were encountered:
JoLo33
added a commit
to JoLo33/OpenPAYGO-HW
that referenced
this issue
Aug 29, 2022
changed: CHECK_BIT macro, return only 0 or 1
changed: for loop in MarkCountAsUsed, so that the correct counts are marked
changed: IsCountValid, so that the limits are correct as explained in general documentation
yes it is then wrong in the documentation. in the general_documentation.pdf on Page 10 in chapter "Counter Synchronisation feature" you will find "If the token matches and the count is either 0 or between last count - 30 and last count + 100, it will set the internal token count to that count."
Hey,
a counter sync token which counter is more than 30 behind the highest entered counter of token get accepted. The problem is in the check in IsCountValid function. Wrong limits are used, the MAX_TOKEN_JUMP define is used but that is 64 and not 30.
Regards Jonas
The text was updated successfully, but these errors were encountered: