[IRCServices] A big problem - services being flooded

[Andrew Church]

>I had thought of this while starting the todo discussion, but forgot about it till now.
>
>Is there any form of flood protection in services?

     There is, but I'm not sure it works properly at the moment.  One of my
goals for 5.0 is to get it working better.

>Oh and in case you were wondering, If you keep on identifying once every second,
>since a line is 110 characters long, it will take you approximately 110 days to fill up
>1 GB. I know how impossible this is, hence it is not my main concern, so please don't
>flame on this. My main point is the cluttering of the log file and services lag.
>
>For Example. As a friend so happily demostrated for me, he logged on and kept on
>identifying once or twice every second. Services didn't react, obviously, since there
>is no flood protection in it.

     Services won't protect against this; as you yourself point out above, at this
rate it would take forever to fill up your hard disk.  I do, however, see how this
could get to be a problem if 100 clones do it at the same time, so I'll see about
disabling logging for users who are already identified.

     However, the main purpose of ignore is to prevent users lagging Services (by
sending commands that take a long time), not to prevent the log filling up your
disk space, which you can check for outside of Services using cron and ls, among
others.  As such, IDENTIFY is insignificant, and things like LIST *a*b*c*d* are
more of a concern.  I do agree that repeat commands are a problem, but for the
time being you should be able to take care of this with ircd flood control.

  --Andrew Church
    achurch at achurch.org | New address - please note.
    http://achurch.org/ | メールアドレスが変わりました。