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
* Clean verified time handling
Try to handle TSA timestamps and rekor v1 integrated time in a sensible
manner:
* no special cases for when TSA timestamps are present
* require one verified time by default
* Only allow integrated time to be a verified time if entry is from rekor v1
* VERIFY_TIMESTAMP_THRESHOLD now refers to "number of verified times",
not just TSA timestamps
* Tests use a rekor v1 bundle but expect it to be invalid if the
timestamp is invalid -- but the integrated time is
enough. Fix this by monkeypatching VERIFY_TIMESTAMP_THRESHOLD
Signed-off-by: Jussi Kukkonen <[email protected]>
* verify: Rename VERIFY_TIMESTAMP_THRESHOLD
VERIFIED_TIME_THRESHOLD makes more sense since integrated time is also
in this threshold.
Strictly speaking this is an API change but since the meaning
has (slightly) changed already that makes sense.
Signed-off-by: Jussi Kukkonen <[email protected]>
---------
Signed-off-by: Jussi Kukkonen <[email protected]>
0 commit comments