A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
I always thought it was a bad idea for AWS to make the buckets unique globally. Attach the AWS account Id so it would always be unique, you can name a bucket whatever you want, and this attack vector wouldn't be possible (unless if you are AWS I guess)
Good reminder to remove old DNS records that point to IPs or hostnames you no longer control or service providers you no longer use.
That's the main attack vector here - you delete an S3 bucket but still have a subdomain CNAME'd to it, so anyone could create a new bucket with the same name and serve arbitrary files from your domain.