Michael Eischer 1d3e99f475 azure: check upload using md5 content hash ... For files below 256MB this uses the md5 hash calculated while assembling the pack file. For larger files the hash for each 100MB part is calculated on the fly. That hash is also reused as temporary filename. As restic only uploads encrypted data which includes among others a random initialization vector, the file hash shouldn't be susceptible to md5 collision attacks (even though the algorithm is broken).		2021-08-04 22:17:46 +02:00
..
azure_test.go	Add plumbing to calculate backend specific file hash for upload	2021-08-04 22:17:46 +02:00
azure.go	azure: check upload using md5 content hash	2021-08-04 22:17:46 +02:00
config_test.go	Add Azure Blob Storage as backend	2017-08-06 21:47:04 +02:00
config.go	azure/gs: Fix default value in connections help text	2021-05-17 20:56:51 +02:00