storj/storagenode/gracefulexit
paul cannon 7395dd1e6e storagenode/gracefulexit: revalidate existing pieces
..before they are transferred to another node and submitted to the
satellite as successful piece transfers, because if we submit an invalid
signature, the node will be marked as a cheater and disqualified
immediately.

These signatures should have been validated when the piece was
originally stored, but bitrot does happen and needn't be cause for an
immediate DQ.

Change-Id: I8b0ebd5812ea8a2e60766005b7251fbb74ef7857
2020-05-28 09:50:14 -05:00
..
chore_test.go private/testplanet: expose storagenode and satellite Config 2020-03-27 17:01:25 +02:00
chore.go storagenode/gracefulexit: revalidate existing pieces 2020-05-28 09:50:14 -05:00
common.go all: use monkit v3 2020-02-05 23:53:17 +00:00
db_test.go satellite: remove some unnecessary UTC() calls 2020-03-13 13:49:44 +00:00
endpoint_test.go satellite: remove some unnecessary UTC() calls 2020-03-13 13:49:44 +00:00
endpoint.go storagenode/trust: refactor GetAddress to GetNodeURL 2020-05-20 11:05:15 +00:00
worker_test.go storagenode/gracefulexit: revalidate existing pieces 2020-05-28 09:50:14 -05:00
worker.go storagenode/gracefulexit: revalidate existing pieces 2020-05-28 09:50:14 -05:00