[IRCServices] Suggestion

[Yusuf Iskenderoglu]

Hello;

On Tue, 20 Mar 2001, Mark Hetherington wrote:

>
> Maybe emulate the system used for Car radios etc. After the first failure of
> 3 "suspend" the nickname for 1 hour, then 2 hours then 4 hours etc until it
> is ultimately locked out entirely and an admin has to take steps to restore
> the nickname to the user after sufficient authentication.

A better way is the introduction of an enforcer, which does not quit after
1 minute. Then people would need to release/ghost with the proper
password, else the enforcer would persist. Still, there is a need of
discovering passwrod crackers.

But suspend is a very militant penalty.

[AUTH System]
>
> Is this or a similar authentication system likely to be in a future version
> of services? It is a system I would like to see since if nothing else it
> reduces the registrations "made on a whim" when the process is more work
> than /ns register pass.
>
> If not, would Yusuf care to share his "patch" with others?

I would share this patch, but you have to keep in mind, that this is not a
small thing. The authentication system I wrote consists of two additional
information for each registered nickname.   Combined with other features
I've added, this information is written to another db, and loaded right
after nick.db. In this case, the other information remains specific to my
network, so you may think to include the auth information in the nick.db.
But then, you will lose compatibility with the current services development,
because Mr.Church does not need to support my extensions. And also, the
mailing services are not added to services, yet.

I would suggest waiting for a solution, must of us will accept. If you are
still interested in my coding, I might provide you privately with the
proper url, but keep in mind, that the source should be considered as
beta.

Regards;
yusuf

Yusuf Iskenderoglu  ***  eMail uhc0 at rz.uni-karlsruhe.de