Skip to content

Conversation

@runcom
Copy link
Member

@runcom runcom commented Sep 3, 2025

The way I interpret https://fidoalliance.org/specs/FDO/FIDO-Device-Onboard-PS-v1.1-20220419/FIDO-Device-Onboard-PS-v1.1-20220419.html#RVInfo is that we should be waiting in a loop and "sleep" if: a) we have a delay in the instruction set before trying the next and b) at the end of the instructions, we'll retry everything but we'll wait for "delay" from the last instruction

@ben-krieger ptal (this is how we mostly done this part in rust as well, just an infinite loop and retries)

@runcom runcom marked this pull request as draft September 3, 2025 15:05
if onboardingPerformed {
break
}
// TODO: if this is the last instruction, set rvEntryDelay to whatever is the last delay, and use it below outside the main for loop

Check notice

Code scanning / devskim

A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note

Suspicious comment
@runcom
Copy link
Member Author

runcom commented Sep 3, 2025

pending clarification from spec @ben-krieger

@ben-krieger
Copy link
Member

pending clarification from spec @ben-krieger

Clarifications will be made to the FDO 2.0 spec. For now, decide on the most logical behavior and this will provide guidance for the spec authors.

runcom added 2 commits October 8, 2025 15:59
Signed-off-by: Antonio Murdaca <[email protected]>
@runcom runcom force-pushed the proper-onboard-loop-delay branch from 7cc0a75 to 1e78775 Compare October 8, 2025 14:01
@runcom runcom marked this pull request as ready for review October 24, 2025 13:16
@runcom runcom added the 1.0.0 label Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants