Groups | Blog | Home
all groups > iis ftp > september 2004 >

iis ftp : Preventing multiple downloads


Jeffrey Hayes
9/20/2004 6:41:56 AM
I have a problem with users initiating multiple FTP downloads of the
same huge file, or several huge files, at the same time. I would like
to restrict the number of times a single user can log in via FTP (to
prevent users from monopolizing the bandwidth) without necessarily
restricting the overall number of users.

How would I do this with IIS? I have IIS 6.0, Windows Server 2003
(Enterprise).


_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>
Bernard
9/20/2004 2:59:43 PM
You are referring openning multiple connections to download rather than
multiple login from the same user. Unfortunely, this is features is not
available in IIS FTP.

--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/



[quoted text, click to view]
____________________________________________________________________________
___
[quoted text, click to view]

Alun Jones [MSFT]
9/21/2004 2:38:43 PM
[quoted text, click to view]

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.

Jeffrey Hayes
9/21/2004 9:28:29 PM
On Mon, 20 Sep 2004 14:59:43 +0800, "Bernard"
[quoted text, click to view]

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).

Meanwhile, I think I will try Filezilla instead and see if that does
it.

_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>
jeff.nospam NO[at]SPAM zina.com
9/22/2004 2:28:09 AM
On Tue, 21 Sep 2004 14:38:43 -0700, "Alun Jones [MSFT]"
[quoted text, click to view]

Damn! [ Scratching crotch area ] I'm only able to make five
connections! :)

Worse than denying connections from multiple systems behind the same
proxy would be queing them up. Could write a heck of a DOS attack
with that configuration.

Alun Jones [MSFT]
9/22/2004 1:04:13 PM
[quoted text, click to view]

How would that work for anonymous use? Surely you're expecting large
numbers of accesses from that user.

[quoted text, click to view]

There's no guarantee that IP address and user are exchangeable commodities.
[What of the user that has more than one IP address at his/her disposal?]

[quoted text, click to view]

What you're looking for is a specific fix that takes into account your
assumptions; what we're looking for is the ability to create a
general-purpose FTP server. Unfortunately, at the moment, I can't predict
what the future intersection of those two goals will be; for right now,
though, it looks like you're doing all that you can.

Perhaps you'd find a market for writing a third-party tool that analyses log
files for such obstreperous behaviour, and adds the banning for you?

Alun.
~~~~

Jeffrey Hayes
9/22/2004 7:46:09 PM
On Tue, 21 Sep 2004 14:38:43 -0700, "Alun Jones [MSFT]"
[quoted text, click to view]

Well, trying other servers, there seem to be two options. (1) If a
user logs in m times within n seconds, then ban him for p minutes. Or
(2) limit the number of connections from a given user to q. In both
cases, an anonymous user is identified by his IP address, as you said.

People with proxies should have caching proxies. Stopping DoS attacks
is more important (to me) than people from large companies sometimes
getting blocked, and for 99.9% of small sites, this will never be an
issue because the traffic will never be that high - unless there is an
attack underway.

_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>
jeff.nospam NO[at]SPAM zina.com
9/22/2004 9:26:34 PM
On 22 Sep 2004 19:46:09 GMT, Jeffrey Hayes <tvdog@sbcglobal.net>
[quoted text, click to view]

So what you want is an FTP server written for the needs of operators
like you, running small sites with no traffic? What about the rest of
Microsoft's customers?

If you don't like the product, try an alternative. Or write your own,
get hired by Microsoft and change their ways. :)

AddThis Social Bookmark Button