]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001519.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001519.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Next Services version?
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Next%20Services%20version%3F&In-Reply-To=20010228031019.A53215%40edgemaster.zombie.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001515.html">
11 <LINK REL="Next" HREF="001521.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Next Services version?</H1>
15 <B>Lonewolf</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Next%20Services%20version%3F&In-Reply-To=20010228031019.A53215%40edgemaster.zombie.org"
17 TITLE="[IRCServices] Next Services version?">lonewolf at lagnet.org.za
18 </A><BR>
19 <I>Wed Feb 28 12:29:01 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001515.html">[IRCServices] Next Services version?
22 </A></li>
23 <LI>Next message: <A HREF="001521.html">[IRCServices] Next Services version?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1519">[ date ]</a>
27 <a href="thread.html#1519">[ thread ]</a>
28 <a href="subject.html#1519">[ subject ]</a>
29 <a href="author.html#1519">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>On Wed, Feb 28, 2001 at 03:10:19AM -0600, Sean Kelly wrote:
35 &gt;<i> How feasable would it be to add SOCKS/WinGate checking as an option
36 </I>&gt;<i> to Services? I am aware many ircds support this, but I am of the
37 </I>&gt;<i> feeling that waiting for ident checks takes long enough, and making
38 </I>&gt;<i> clients wait for a SOCKS check takes even longer, especially on
39 </I>&gt;<i> hosts (@Home) which firewall the SOCKS port and fail to return a RST
40 </I>&gt;<i> packet. This would allow the majority of good users to connect
41 </I>&gt;<i> while a SOCKS check would be done in the background.
42 </I>
43 The best way to do this is to have a bot sit on the server and check
44 incoming clients. This means that there's no extra delay for the user
45 connecting.
46
47 If you have a small network, then you could have a separate &quot;socks&quot;
48 checking server.
49
50 Take a look at GeoStats &lt;<A HREF="http://geostats.lite.net/">http://geostats.lite.net/</A>&gt; - it also has an
51 option to check for open proxy/wingate machines as new clients are
52 introduced to the network.
53
54 --
55 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">lonewolf at lagnet.org.za</A>
56
57
58 </PRE>
59
60 <!--endarticle-->
61 <HR>
62 <P><UL>
63 <!--threads-->
64 <LI>Previous message: <A HREF="001515.html">[IRCServices] Next Services version?
65 </A></li>
66 <LI>Next message: <A HREF="001521.html">[IRCServices] Next Services version?
67 </A></li>
68 <LI> <B>Messages sorted by:</B>
69 <a href="date.html#1519">[ date ]</a>
70 <a href="thread.html#1519">[ thread ]</a>
71 <a href="subject.html#1519">[ subject ]</a>
72 <a href="author.html#1519">[ author ]</a>
73 </LI>
74 </UL>
75
76 </body></html>