digitally sign acro outputs
jim-smith opened this issue · comments
very much a 'simple thing that could be done if TREs are worried that some users might edit acro outputs after we have checked them and said they are ok.
Won't in the MOSCoW category for SACRO
At DAREUK mid-projects meeting.
We should add this asap to because people running TREs trust researchers less than we might think. Takes us to similar levels of security to aisdc.
shar512 checksum seems to be preferred method for TRE-FX
@rpreen This has become more urgent since we removed the timestamp from the filenames - which some TRE staff had said they particularly liked during evaluation.
Can we add timestamp as a field?
The timestamp is still there as a field.
Cool.
I wonder if we should ask @benbc whether they could flag in their code that the file had been changed since the timestamp?
What are we trying to guard against here? It seems difficult to stop researchers from deliberately modifying the output post-check. They could always change the JSON timestamp too. (And update any checksum we include.)
Inadvertent bad practice/ mistakes.
Quite agree that we can't possibly be secure against everything.