3 ms·
> Amazon S3 buckets that had previously been used across commercial and open source software products, governments, and infrastructure deployment/update pipelin
by hypeatei 2y ago
> Amazon S3 buckets that had previously been used across commercial and open source software products, governments, and infrastructure deployment/update pipelines—and then abandoned.
Couldn't this happen with a domain too? e.g. you stop paying and someone else takes it over but your app is still pinging it.
I don't see how AWS is really special here to be honest. If you can't guarantee you'll always have <thing that provides updates> then you should probably add in a signing mechanism to your software to verify it's coming from the original devs.
- Shank 2y ago> Couldn't this happen with a domain too? Yes, and you really hope someone implemented certificate pinning for this exact reason, but it often is not the case.
- smileybarry 2y agoProbably better to just do update signing, certificates rotate frequently and at some point you’re bound to run into an enterprise customer with a MITM / caching proxy.
- smileybarry 2y agoI guess the worse part about S3 buckets vs domains is that it’s bound to AWS (would you maintain a dead AWS account with an empty bucket forever after you switched to GCP?), and potentially more expensive than domain upkeep. (Not really but there’s always the worry of keeping a cloud account with resources left unmonitored) At least with a domain you can park it somewhere and pay a yearly renewal fee without worrying.