We’ve moved the Sphere blog. You can also reach it through the navigation on our homepage. We won’t be posting anything new here going forward so come visit our new home….
Comment by b9mh — November 5, 2009 @ 11:20 pm
I miss sphere.
Comment by Chester — February 11, 2010 @ 1:48 pm
Nice post, thanks for sharing!
Comment by Steven — May 26, 2011 @ 9:21 am
Helpfull aticle, thanks for posted
Comment by Classified — September 2, 2013 @ 4:00 pm
I’m surprised that you describe this as a vulnerability of Amazon’s S3. This has really nothing at all to do with Amazon S3 or even with any particular class of web services. This denial-of-service attack is entirely created and caused by a badly engineered, oversensitive intrusion-detection-system with overzealous automated response (namely blocking an IP address forever) on your computer, in your particular example Norton Internet Worm Protection. Amazon’s S3 became merely by accident the service that you happend to be playing with when you first stumbled across how dangerous it can be to install too aggressive intrusion-detection systems on your PC. They far too easily become the problem rather than a solution and ultimately increase the attackable surface of your PC by adding lots of badly thought through functionality to your local network stack. I would never want to buy or install any product that destroys the binary transparency of my network connections. Click http://link.mx/hool08200
Comment by bucknerbowen34906 — April 8, 2016 @ 12:11 pm
RSS feed for comments on this post. TrackBack URI
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of new comments via email.
Blog at WordPress.com.
Get every new post delivered to your Inbox.