theupdateframework / theupdateframework/python-tuf
compatibility: bottlerocket metadata uses microseconds in expiry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 304
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
Description
We have recently started to not accept microseconds in the expiry in an effort to be spec compliant.
Testing ngclient against bottlerocket metadata fails because they use microseconds:
https://updates.bottlerocket.aws/2020-07-07/aws-k8s-1.16/x86_64/timestamp.json
- could file an issue in awslabs (though I'm not sure if this is their problem or not)
- Maybe reconsider if we are too strict and should accept this input in deserialization (even if not when expiry is set in code)?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ngclient failure with the Bottlerocket timestamp.json example and trace expiry handling during deserialization. Review the compatibility question against the stated specification requirements. Done means reaching a decided behavior for microsecond expiry values and confirming it with the relevant metadata input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100