Duke-GCB / Duke-GCB/D4S2

Support verification of s3 delivered files

Open
#154 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

We need a method to verify that the files that have been delivered and stored in s3 have not been modified. This should include issues with a bad actor modifying the files in the bucket.
It would also be nice if the verification could take place even without access to the D4S2 database.

We have discussed adding a MD5 check sum to the metadata and/or adding a digital signature.
There is a chicken and egg problem with creating a digital signature based on the metadata, and storing that signature in the metadata.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.