I'm Paul Bissex, and e-scribe.com is my consulting business. I build web applications using open source software, especially Django. I teach photographers web design and professional skills. In the '90s I did graphic design for newspapers and magazines. Then I wrote technology commentary and reviews for Wired, Salon.com, Chicago Tribune, and lots of little places you've never heard of. Feel free to email me.
I'm co-author of "Python Web Development with Django", an excellent guide to my favorite web framework. Its strong points include an introduction to Python, and better coverage of Django 1.0 than nearly anybody else. Published by Addison-Wesley, it is available from Amazon and your favorite technical bookstore as well.
Built using Django, served by Apache and mod_wsgi. The database is SQLite. The operating system is FreeBSD, on a VPS hosted at Johncompanies.com. Comment-spam protection by Akismet. Vintage topo imagery from the Maptech archive. The markup engine is Markdown.
Akismet, del.icio.us, Django, dpaste.com, Emacs, FreeBSD, Freenode, jQuery, LaunchBar, MacPorts, Markdown, Mercurial, OS X, Postfix, Python, SQLite, Subversion, TextMate, Trac, Ubuntu Linux, wmii
At least 67564 pieces of comment spam killed since January 2008, mostly via Akismet.
If you tried to reach this blog or anything else on this server this afternoon, you may not have had much luck.
A computer in Korea was hammering my server so hard (aka Denial of Service attack) that my hosting provider temporarily disabled Apache so that my instance didn't bog down the whole VPS. I was busy at work when this happened and am not sure exactly how long it was out, but this was one of the most severe outages I've had in the last three and a half years.
I've blocked the offending IP, and made some other tuning adjustments. Up until now I've had the luxury of relatively low and predictable traffic, but this incident has gotten me a bit more interested in learning how to handle high loads with Apache/mod_python without eating all memory in sight.
Thanks, Cory -- a couple other people have suggested that as well, so I'm looking into it.
So you have identified the attacking IPs. Is it all? No defense against criminals who try to ruin your business ? The attack originators should be penalized by autohorities, or? I was hardly able to find any information on this so any experience woudl be appreciated.
I did send a report to the abuse address associated with the netblock of the attacking IP, but didn't get much of a response.
Thanks for reading! Please note: Your comment will not appear until approved, which may take a few hours or more. Spammers will be torpedoed.
Branching and merging in real life
7 comments
Summer Spam
1 comment
SPF-enabled spam domains
1 comment
Chess via iPod
2 comments
Aesthetics and computation
2 comments
Brett Spurrier
Software for determining image similarity?
23 days ago
nizamfarooq
eBay, fraud, filtering, and Web 2.0
59 days ago
Derek
World's ugliest Django app
90 days ago
sagar
Sort tables with sorttable.js
109 days ago
Paintball Kolbudy
Summer Spam
116 days ago
Copyright 2010
by Paul Bissex
and E-Scribe New Media
You might also consider using `mod_evasive`, an apache module for defending against DoS attacks: <http://www.zdziarski.com/projects/mod_evasive/>