-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
name stored attestations by digest instead of UUID #769
Conversation
Signed-off-by: Bob Callaway <bcallaway@google.com>
Codecov Report
@@ Coverage Diff @@
## main #769 +/- ##
==========================================
- Coverage 46.56% 46.42% -0.15%
==========================================
Files 60 60
Lines 5094 5116 +22
==========================================
+ Hits 2372 2375 +3
- Misses 2447 2467 +20
+ Partials 275 274 -1
Continue to review full report at Codecov.
|
Does this mean we'll lose access to all the existing attestations unless we migrate their names to the new format? |
I think a mass migration would make sense after this PR is in, since those attestations are still open to modification without detection? |
Yeah makes sense. |
🤦 no, I missed something here. Never mind. |
Signed-off-by: Bob Callaway <bcallaway@google.com>
Signed-off-by: Bob Callaway <bcallaway@google.com>
This changes the way attestations are named within the storage mechanism; previously, the attestations were stored with a filename of the Merkle leaf hash (aka
uuid
); however, with the sharding work now merged, there is a risk of conflict since there may be duplicate entries across multiple shards.Note: this also changes the encoding of persisted data in the attestation store from base64-encoded base64-encoded strings (yes, not a typo) to the actual decoded data. This may require clients to update their parsing logic.
before:
after:
Signed-off-by: Bob Callaway bcallaway@google.com