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

Use seconds precision for entropy timestamp. Use hotspot generated entropy inputs and outputs for beacon verification test #360

Merged
merged 1 commit into from
Feb 14, 2023

Conversation

andymck
Copy link
Contributor

@andymck andymck commented Feb 13, 2023

This addresses a mismatch on the beacon generation on the verifier with that of the beacon generation on hotspots where the resultant generated data payload values did not match.

The root cause of the issue was that the verifier was passing in millisecs precision for its remote entropy timestamp value when generating the beacon to verify whereas the hotspots uses seconds precision.

@andymck andymck force-pushed the andymck/beacon-payload-test-additions branch from d990687 to 76ce123 Compare February 14, 2023 14:25
@andymck andymck changed the title hardcode test with entropy inputs, verify expected outputs Use seconds precision for entropy timestamp. Use hotspot generated entropy inputs and outputs for beacon verification test Feb 14, 2023
iot_verifier/src/poc.rs Outdated Show resolved Hide resolved
@andymck andymck force-pushed the andymck/beacon-payload-test-additions branch from 76ce123 to 40c772f Compare February 14, 2023 14:42
@andymck andymck marked this pull request as ready for review February 14, 2023 14:43
@andymck andymck merged commit c1a6a29 into main Feb 14, 2023
@andymck andymck deleted the andymck/beacon-payload-test-additions branch February 14, 2023 15:30
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

Successfully merging this pull request may close these issues.

3 participants