Re:Ptar: Replacing .tgz for petabyte-scale S3 archives
by SteveNuts on Tuesday July 08, 2025 @10:13PM
(#44505759)
Yes, I am paranoid of S3. Not only could a once in a lifetime event happen, an attacker could get in and delete all my data. Data could be accidentally deleted. Corrupted data could be written...
[ Parent
| on HN ]
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives
by nemothekid on Tuesday July 08, 2025 @10:29PM
(#44505825)
>Data could be accidentally deleted. Corrupted data could be written...
You guys should really have versioning enabled. Now if someone deleted your data and all the versions, that could be possible, but that would take real effort and would like be malicious.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives
by imglorp on Tuesday July 08, 2025 @10:34PM
(#44505850)
Nobody mentioned the case where you get locked out of your cloud provider with no humans to speak to, or your account gets deleted by the algorithm. Both happen routinely and we only hear about it when the victim takes to the socials.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives
by burnt-resistor on Tuesday July 08, 2025 @10:18PM
(#44505784)
Then 3 steps.
1. Use tarsnap so there's an encryption and a management layer.
2. Use a second service so there's redundancy and no SPoF.
3. Keep cryptographic signatures (not hashes) of each backup job in something like a WORM blockchain KVS.