From 061078928593a1377f6b9e591c1957f405eaaf7c Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 13 May 2019 22:03:38 +0000 Subject: [PATCH] Added a comment: checksums of remote data --- .../comment_4_cd5974b989f0a75a8d441d6c3eff4807._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/checksum_verification_on_transfer/comment_4_cd5974b989f0a75a8d441d6c3eff4807._comment diff --git a/doc/todo/checksum_verification_on_transfer/comment_4_cd5974b989f0a75a8d441d6c3eff4807._comment b/doc/todo/checksum_verification_on_transfer/comment_4_cd5974b989f0a75a8d441d6c3eff4807._comment new file mode 100644 index 0000000000..42167f134a --- /dev/null +++ b/doc/todo/checksum_verification_on_transfer/comment_4_cd5974b989f0a75a8d441d6c3eff4807._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="checksums of remote data" + date="2019-05-13T22:03:38Z" + content=""" +\"I don't see any way to do checksum verification on upload to a special remote, without it somehow having a way to verify an arbitrary checksum method of data stored in it, which nothing supports\" -- arbitrary checksum no, but some remotes do support verifying MD5 checksums specifically. E.g. DNAnexus can tell you the MD5 of each uploaded part of a multi-part file; Google Cloud Storage can tell you the MD5 for a non-composite file, and CRC32 for composite files. Maybe, the [[external special remote protocol|design/external_special_remote_protocol]] could be extended with optional requests/replies to expose these capabilities? +"""]]