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
@segiddins has pointed out that some Rekor log entry/bundle fields have malleable formats, e.g. anything that uses Base64 (or PEM). We should probably have some tests that confirm that clients perform comparisons on the underlying contents, not the malleable containers themselves.
The text was updated successfully, but these errors were encountered:
I have a doc about this topic I can share. Ideally we solve this in Rekor by canonicalizing to a specific format, but it’s a hard problem just due to how many transformations are possible.
From a client perspective, they should verify using the canonicalized structure returned by the log.
From a monitor perspective, the risk is low, just that someone could reupload a malleable entry.
Thanks @haydentherapper! Yeah, I agree the risk is low here -- I think having these will help prevent more false negatives in clients (e.g. around slightly different PEM serializations) than anything else 🙂
@segiddins has pointed out that some Rekor log entry/bundle fields have malleable formats, e.g. anything that uses Base64 (or PEM). We should probably have some tests that confirm that clients perform comparisons on the underlying contents, not the malleable containers themselves.
The text was updated successfully, but these errors were encountered: