Live data from Hacker News

How I attacked myself using Google and I ramped up a $1000 bandwidth bill

behind-the-enemy-lines.com

151–152 of 152 posts

Re: How I attacked myself using Google and I ramped up a $1000 bandwidth bill

#151

Earlier quoted context omitted.

OK, so now we have DoS and CoS! I dunno though, it's all technically bandwidth flood in the end. The consequences (or goals) of flood may include immediate or eventual denial of service, high cost of service, various security attacks, or probably all at once—further classification surely is complicated. Meanwhile, both terms DoS and CoS are a bit vague, too. Say, turning off a server or forcing providers to alter the…

I wold argue that "DoS" is not vague, just a broad term. Aanyway.. You're right, it boils down to bandwidth flood (or maybe CPU..) in the end. Maybe CoS is not really a technical term, just made more relevant by the technological changes. OP would have been charged much less had he not been using "the cloud". Lets say I have small'ish competitor hosting their app on EC2. Using classical DoS techniques, how much can I…

Maybe Amazon should add smart log mining ?

If it requires a lot of effort to productize, Amazon could potentially offer it as a service $0.5/hr to ensure you are not making major goof ups.

Re: How I attacked myself using Google and I ramped up a $1000 bandwidth bill

#152

Earlier quoted context omitted.

I don't understand the privacy concern - a publicly accessible URL doesn't offer any privacy. It's the same as a transparent proxy.

A password works by there is a piece of text that only you know, and thus, when you give that password to a server, that server knows who you are. can't you also view a url as a password? (If only I know the url, then only I can download the file). I am able to give out a url to someone else, so they can access the file, likewise, I can give out my file server's username and password, and whoever has it can also acce…

Google is already storing urls to those files.
Post reply on HN