uptane / uptane.github.io

UPTANE web site
https://uptane.org
Apache License 2.0
35 stars 26 forks source link

Handling failure to verify latest time #189

Open lorchrob opened 10 months ago

lorchrob commented 10 months ago

To my reading, sections 3.1.1.1 and 3.1.1.3 seem to offer diverging advice as to how a primary ECU should handle a failure to verify the latest time from an external time source. In 3.1.1.1, it says “If it [primary ECU] fails to meet this [verification] criteria, discard the response and continue the procedure without an updated time”. However, 3.1.1.3 says “If any check fails, the ECU SHOULD NOT overwrite its current attested time, but SHOULD jump to the last step …”.

To make things consistent, any of the following changes could be made:

Any thoughts?

mnm678 commented 10 months ago

Thanks for the question!

Based on discussion in the Uptane Standards meeting, as the time source is not specified by Uptane, we will leave the choice of what counts as a "fatal" error" of the time source up to the implementation. This can be based on knowledge about the time source (such as reliability, whether there is a backup source of time, etc). We will update this in the text to clarify that if such a fatal error occurs, the update should not continue.

New text ideas:

lorchrob commented 10 months ago

Hi, thanks for the response! I agree that a change in this direction would help disambiguate things. Regarding textual updates, is there anything you need from my end, i.e. drafts of changes? If so, just let me know, otherwise I'm happy to let you guys take it from here 😀

mnm678 commented 8 months ago

If you are able to draft some text or open a pull request, that'll help this move faster. Thanks!

tkfu commented 8 months ago

I'm transferring this here, as we will archive the separate deployment-considerations repo soon.