News for hackers. Stuff that matters.
Re:How a bug in VS2015 exposed my source code on GitHub and ... by vacri on Monday August 31, 2015 @06:01PM (#10149346)
AWS do do things. They have service limits and routinely waive charges from abuse events like this.

I do wonder if GitHub's events firehose has benefits that outweigh all the compromised credentials, though. Not just limited to AWS keys.

Re:How a bug in VS2015 exposed my source code on GitHub and ... by Analemma_ on Monday August 31, 2015 @06:09PM (#10149388)
> They have service limits and routinely waive charges from abuse events like this.

That's almost worse though. Maybe I'm being unfair here, but the fact that they will waive charges immediately if you ask, but don't just block them pre-emptively, tells me that they're hoping at least some customers (with deep pockets and automated billing that no one pays attention to) will just pay the bill and never notice. Maybe they're making more money from that than they're losing by waiving charges on compromised accounts for customers who ask.

Re:How a bug in VS2015 exposed my source code on GitHub and ... by slg on Monday August 31, 2015 @06:25PM (#10149484)
Devils advocate, wouldn't you rather have illegitimate charges waived after the fact that legitimate charges declined because their algorithm threw up a red flag? Something like being posted to HN could cause a huge spike in charges for your account in a similar way as leaking your keys and it would be beyond frustrating to see that opportunity disappear because Amazon saw your bill spike.
Re:How a bug in VS2015 exposed my source code on GitHub and ... by inopinatus on Monday August 31, 2015 @06:45PM (#10149583)
Don't be ridiculous. AWS want legitimate revenue, not brand damage.