[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001659.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] Suggestion
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=000601c0b161%240e4634c0%240deea8c0%40eurodltd.co.uk">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001656.html">
   <LINK REL="Next"  HREF="001672.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] Suggestion</H1>
    <B>Yusuf Iskenderoglu</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=000601c0b161%240e4634c0%240deea8c0%40eurodltd.co.uk"
       TITLE="[IRCServices] Suggestion">uhc0 at rz.uni-karlsruhe.de
       </A><BR>
    <I>Tue Mar 20 20:21:00 PST 2001</I>
    <P><UL>
        <LI>Previous message: <A HREF="001656.html">[IRCServices] Suggestion
</A></li>
        <LI>Next message: <A HREF="001672.html">[IRCServices] Suggestion
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1659">[ date ]</a>
              <a href="thread.html#1659">[ thread ]</a>
              <a href="subject.html#1659">[ subject ]</a>
              <a href="author.html#1659">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Hello;

On Tue, 20 Mar 2001, Mark Hetherington wrote:

&gt;<i>
</I>&gt;<i> Maybe emulate the system used for Car radios etc. After the first failure of
</I>&gt;<i> 3 &quot;suspend&quot; the nickname for 1 hour, then 2 hours then 4 hours etc until it
</I>&gt;<i> is ultimately locked out entirely and an admin has to take steps to restore
</I>&gt;<i> the nickname to the user after sufficient authentication.
</I>
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]
&gt;<i>
</I>&gt;<i> Is this or a similar authentication system likely to be in a future version
</I>&gt;<i> of services? It is a system I would like to see since if nothing else it
</I>&gt;<i> reduces the registrations &quot;made on a whim&quot; when the process is more work
</I>&gt;<i> than /ns register pass.
</I>&gt;<i>
</I>&gt;<i> If not, would Yusuf care to share his &quot;patch&quot; with others?
</I>
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 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de</A>


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001656.html">[IRCServices] Suggestion
</A></li>
	<LI>Next message: <A HREF="001672.html">[IRCServices] Suggestion
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1659">[ date ]</a>
              <a href="thread.html#1659">[ thread ]</a>
              <a href="subject.html#1659">[ subject ]</a>
              <a href="author.html#1659">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices] Suggestion
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=000601c0b161%240e4634c0%240deea8c0%40eurodltd.co.uk">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="001656.html">
	11	<LINK REL="Next" HREF="001672.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] Suggestion</H1>
	15	<B>Yusuf Iskenderoglu</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Suggestion&In-Reply-To=000601c0b161%240e4634c0%240deea8c0%40eurodltd.co.uk"
	17	TITLE="[IRCServices] Suggestion">uhc0 at rz.uni-karlsruhe.de
	18	</A><BR>
	19	<I>Tue Mar 20 20:21:00 PST 2001</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001656.html">[IRCServices] Suggestion
	22	</A></li>
	23	<LI>Next message: <A HREF="001672.html">[IRCServices] Suggestion
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1659">[ date ]</a>
	27	<a href="thread.html#1659">[ thread ]</a>
	28	<a href="subject.html#1659">[ subject ]</a>
	29	<a href="author.html#1659">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Hello;
	35
	36	On Tue, 20 Mar 2001, Mark Hetherington wrote:
	37
	38	><i>
	39	</I>><i> Maybe emulate the system used for Car radios etc. After the first failure of
	40	</I>><i> 3 "suspend" the nickname for 1 hour, then 2 hours then 4 hours etc until it
	41	</I>><i> is ultimately locked out entirely and an admin has to take steps to restore
	42	</I>><i> the nickname to the user after sufficient authentication.
	43	</I>
	44	A better way is the introduction of an enforcer, which does not quit after
	45	1 minute. Then people would need to release/ghost with the proper
	46	password, else the enforcer would persist. Still, there is a need of
	47	discovering passwrod crackers.
	48
	49	But suspend is a very militant penalty.
	50
	51	[AUTH System]
	52	><i>
	53	</I>><i> Is this or a similar authentication system likely to be in a future version
	54	</I>><i> of services? It is a system I would like to see since if nothing else it
	55	</I>><i> reduces the registrations "made on a whim" when the process is more work
	56	</I>><i> than /ns register pass.
	57	</I>><i>
	58	</I>><i> If not, would Yusuf care to share his "patch" with others?
	59	</I>
	60	I would share this patch, but you have to keep in mind, that this is not a
	61	small thing. The authentication system I wrote consists of two additional
	62	information for each registered nickname. Combined with other features
	63	I've added, this information is written to another db, and loaded right
	64	after nick.db. In this case, the other information remains specific to my
65	network, so you may think to include the auth information in the nick.db.
66	But then, you will lose compatibility with the current services development,
67	because Mr.Church does not need to support my extensions. And also, the
68	mailing services are not added to services, yet.
69
70	I would suggest waiting for a solution, must of us will accept. If you are
71	still interested in my coding, I might provide you privately with the
72	proper url, but keep in mind, that the source should be considered as
73	beta.
74
75	Regards;
76	yusuf
77
78	Yusuf Iskenderoglu *** eMail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de</A>
79
80
81
82	</PRE>
83
84	<!--endarticle-->
85	<HR>
86	<P><UL>
87	<!--threads-->
88	<LI>Previous message: <A HREF="001656.html">[IRCServices] Suggestion
89	</A></li>
90	<LI>Next message: <A HREF="001672.html">[IRCServices] Suggestion
91	</A></li>
92	<LI> <B>Messages sorted by:</B>
93	<a href="date.html#1659">[ date ]</a>
94	<a href="thread.html#1659">[ thread ]</a>
95	<a href="subject.html#1659">[ subject ]</a>
96	<a href="author.html#1659">[ author ]</a>
97	</LI>
98	</UL>
99
100	</body></html>