[Proftpd-user] MaxConnectionsPerHost either bug or documentation is wrong?

Hello,

I set the following on a server and checked out how it works:

MaxConnectionsPerHost 2 "Sorry, you may not connect more than (%m) times."

Intention: I do not want to have more than 2 trial and error (brute-force) 
connections per host (or client in this case, I'd say).

Documentation says:

MaxConnectionsPerHost -- Limits the unauthenticated connections per client 
machine

I stress the *un*authenticated. If I'm logged in twice (= authenticated!) 
I should still be able to login until I reach the MaxClientsPer* settings 
and then try two more connections that won't be able to login.

e.g.
MaxClientsPerHost 4
MaxClientsPerUser 4
MaxConnectionsPerHost 2
should allow 4 authenticated connections and two unauthenticated at any 
given time.

However, that is not how it works. After two successful logins, when I try 
a third connection I get "Sorry, you may not connect more than (%m) 
times." As it is the only one with this wording (I didn't quote the other 
ones) I can be sure it is the MaxConnectionsPerHost setting which limits 
here.

It rather seems that the documentation should say:
MaxConnectionsPerHost -- Limits the authenticated *and* unauthenticated 
connections per client machine 

however, then it is the same as:
MaxClientsPerHost -- Limits the connections per client machine
unless that should mean "authenticated" only.
or, isn't it?

So, how is this supposed to work?
Is this a bug or wrong documentation or a misunderstanding on my side?

Thanks!


Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html