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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] A discussion on the contents of the todo file
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001636.html">
   <LINK REL="Next"  HREF="001641.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] A discussion on the contents of the todo file</H1>
    <B>Imran Ali Rashid</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&In-Reply-To="
       TITLE="[IRCServices] A discussion on the contents of the todo file">u970042 at giki.edu.pk
       </A><BR>
    <I>Mon Mar 19 06:39:01 PST 2001</I>
    <P><UL>
        <LI>Previous message: <A HREF="001636.html">[IRCServices] A discussion on the contents of the todo file
</A></li>
        <LI>Next message: <A HREF="001641.html">[IRCServices] A discussion on the contents of the todo file
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1640">[ date ]</a>
              <a href="thread.html#1640">[ thread ]</a>
              <a href="subject.html#1640">[ subject ]</a>
              <a href="author.html#1640">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>&gt;<i> As a rumor claims, DALnet once had a log channel for their proxy
</I>&gt;<i> scanners.  It became a liability, as people would attempt to ride in on
</I>&gt;<i> netsplits.  Those who managed to stay for awhile logged the proxies,
</I>&gt;<i> then made good use of them on servers that did not run the scanner (or
</I>&gt;<i> after attacking the scanner into oblivion).
</I>
There are easy work arounds for this. If Services can send to the channel,
it can control it, and hence prevent anyone being in it who isn't a services
admin. And can prevent Services admins from joining without identifying and
so on. I don't know how many ircds support +O but this could also be used
to help against this kind of abuse.

&gt;<i> While that's unconfirmed, it certainly rings true with human behavior. 
</I>&gt;<i> I'd suggest adding in a hostmask-regulated telnet module or similar (I'd
</I>&gt;<i> go for DCC, but that wouldn't allow giving commands to OperServ while
</I>&gt;<i> not on IRC).  Along with live log watching, you could have a parser scan
</I>&gt;<i> the new log files and show you past history on a nick or channel, etc. 
</I>&gt;<i> If thread support is sufficient on the OSes services runs on, such a
</I>&gt;<i> module would be useful as a separate thread: skips around shell process
</I>&gt;<i> restrictions, and no lag on services while crunching logs.
</I>
The purpose of a telnet module to operserv was in case easy access was
not available to irc. Why put in that restriction? If you're on irc anyways,
you don't need the telnet module in the first place.

&gt;<i> 
</I>&gt;<i> -- Quension
</I>&gt;<i> 
</I>
Imran Ali Rashid


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001636.html">[IRCServices] A discussion on the contents of the todo file
</A></li>
	<LI>Next message: <A HREF="001641.html">[IRCServices] A discussion on the contents of the todo file
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1640">[ date ]</a>
              <a href="thread.html#1640">[ thread ]</a>
              <a href="subject.html#1640">[ subject ]</a>
              <a href="author.html#1640">[ 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] A discussion on the contents of the todo file
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&In-Reply-To=">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="001636.html">
	11	<LINK REL="Next" HREF="001641.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] A discussion on the contents of the todo file</H1>
	15	<B>Imran Ali Rashid</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&In-Reply-To="
	17	TITLE="[IRCServices] A discussion on the contents of the todo file">u970042 at giki.edu.pk
	18	</A><BR>
	19	<I>Mon Mar 19 06:39:01 PST 2001</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001636.html">[IRCServices] A discussion on the contents of the todo file
	22	</A></li>
	23	<LI>Next message: <A HREF="001641.html">[IRCServices] A discussion on the contents of the todo file
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1640">[ date ]</a>
	27	<a href="thread.html#1640">[ thread ]</a>
	28	<a href="subject.html#1640">[ subject ]</a>
	29	<a href="author.html#1640">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>><i> As a rumor claims, DALnet once had a log channel for their proxy
	35	</I>><i> scanners. It became a liability, as people would attempt to ride in on
	36	</I>><i> netsplits. Those who managed to stay for awhile logged the proxies,
	37	</I>><i> then made good use of them on servers that did not run the scanner (or
	38	</I>><i> after attacking the scanner into oblivion).
	39	</I>
	40	There are easy work arounds for this. If Services can send to the channel,
	41	it can control it, and hence prevent anyone being in it who isn't a services
	42	admin. And can prevent Services admins from joining without identifying and
	43	so on. I don't know how many ircds support +O but this could also be used
	44	to help against this kind of abuse.
	45
	46	><i> While that's unconfirmed, it certainly rings true with human behavior.
	47	</I>><i> I'd suggest adding in a hostmask-regulated telnet module or similar (I'd
	48	</I>><i> go for DCC, but that wouldn't allow giving commands to OperServ while
	49	</I>><i> not on IRC). Along with live log watching, you could have a parser scan
	50	</I>><i> the new log files and show you past history on a nick or channel, etc.
	51	</I>><i> If thread support is sufficient on the OSes services runs on, such a
	52	</I>><i> module would be useful as a separate thread: skips around shell process
	53	</I>><i> restrictions, and no lag on services while crunching logs.
	54	</I>
	55	The purpose of a telnet module to operserv was in case easy access was
	56	not available to irc. Why put in that restriction? If you're on irc anyways,
	57	you don't need the telnet module in the first place.
	58
	59	><i>
	60	</I>><i> -- Quension
	61	</I>><i>
	62	</I>
	63	Imran Ali Rashid
	64
65
66
67
68	</PRE>
69
70	<!--endarticle-->
71	<HR>
72	<P><UL>
73	<!--threads-->
74	<LI>Previous message: <A HREF="001636.html">[IRCServices] A discussion on the contents of the todo file
75	</A></li>
76	<LI>Next message: <A HREF="001641.html">[IRCServices] A discussion on the contents of the todo file
77	</A></li>
78	<LI> <B>Messages sorted by:</B>
79	<a href="date.html#1640">[ date ]</a>
80	<a href="thread.html#1640">[ thread ]</a>
81	<a href="subject.html#1640">[ subject ]</a>
82	<a href="author.html#1640">[ author ]</a>
83	</LI>
84	</UL>
85
86	</body></html>