[quoted text, click to view] "Jeffrey Hayes" <tvdog@sbcglobal.net> wrote in message
news:m371l0hqeqgcnmh4cl5jpk4al6upkmrgnh@4ax.com...
> Thanks for your reply. Maybe it would be good, though, if Microsoft
> added some security to IIS. I had a guy who ran a script to connect 5
> times every 15 seconds and open a new connection to download the same
> file. Should be a way to stop that automatically (I added an entry to
> ban his entire ISP in IIS).
There's always a behaviour that people think "should be stopped".
Scratching yourself in public, saying naughty words, connecting multiple
times to download files.
Sadly, the solutions are rarely better than the problems they present, and
here's why:
You are using anonymous access(*).
What you're saying there is that you are opening up your server to downloads
to anyone and everyone that can find your server. In essence, that's the
problem - you can't block the user without finding a way to identify the
user. What can you use to identify the user? You can't use his name,
because he'll fake that. Can you use his IP address? Well, sure, except
that also blocks legitimate accesses by users of time-sharing operating
systems, or corporate users behind proxies (me, for instance, sitting here
behind a Microsoft proxy) or NATs.
But, perhaps you have an idea that we haven't considered - how would _you_
go about automatically stopping such errant behaviour? Bear in mind that
the idea you come up with would have to be widely implemented, and so
couldn't have any nasty repercussions.
Alun.
~~~~
(*) How do I know this? Simple - if you'd given this user a user name and
password, you would have been able to stop him simply by revoking his
account or changing his password.