]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/002948.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 002948.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=Proxy%20scanning%20%28was%20RE%3A%20%5BIRCServices%5D%20Another%20Feature%20Suggestion%29&In-Reply-To=Pine.LNX.4.44.0205310256090.2453-100000%40vector.chocobo.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="002945.html">
11 <LINK REL="Next" HREF="002950.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)</H1>
15 <B>Russell Garrett</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=Proxy%20scanning%20%28was%20RE%3A%20%5BIRCServices%5D%20Another%20Feature%20Suggestion%29&In-Reply-To=Pine.LNX.4.44.0205310256090.2453-100000%40vector.chocobo.org"
17 TITLE="Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)">rg at tcslon.com
18 </A><BR>
19 <I>Fri May 31 12:18:01 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="002945.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
22 </A></li>
23 <LI>Next message: <A HREF="002950.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#2948">[ date ]</a>
27 <a href="thread.html#2948">[ thread ]</a>
28 <a href="subject.html#2948">[ subject ]</a>
29 <a href="author.html#2948">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i> Since Services 5 will (or at very least could, given
35 </I>&gt;<i> coding for a module)
36 </I>&gt;<i> sport global Z: line management, would it make sense to
37 </I>&gt;<i> have it send a
38 </I>&gt;<i> message so that it adds your desired Z: line to Services?
39 </I>&gt;<i> Or should one
40 </I>&gt;<i> collect up the accumulated Z: lines on the respective
41 </I>&gt;<i> servers BOPM is
42 </I>&gt;<i> running on and manually add them later?
43 </I>
44 The only problem with this is the single-point-of-failure problem: If
45 someone DoSes your Services server, or the services hub off, then the
46 point of having a seperate proxy monitor on each server is defeated,
47 as they can't submit their z:lines.
48
49 The most resilient solution, at least with BOPM, is to get each
50 individual BOPM bot to submit by e-mail to blitzednet's DNS blacklist
51 (you have to e-mail them to set this up, but it's very efficient) -
52 all the other BOPM proxy monitors on your network and everywhere else
53 will then pick compromised hosts up almost immediately using the
54 blacklist lookup, without having to scan. This removes the
55 single-point-of-failure problem (well I suppose someone could still
56 DoS the blacklist server, but that would only slow down the k:lining
57 of proxybots - if you're that paranoid you could use your own
58 blacklist server).
59
60 Russ Garrett
61 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">russ at garrett.co.uk</A>
62 www.faereal.net
63
64
65 </PRE>
66
67 <!--endarticle-->
68 <HR>
69 <P><UL>
70 <!--threads-->
71 <LI>Previous message: <A HREF="002945.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
72 </A></li>
73 <LI>Next message: <A HREF="002950.html">Proxy scanning (was RE: [IRCServices] Another Feature Suggestion)
74 </A></li>
75 <LI> <B>Messages sorted by:</B>
76 <a href="date.html#2948">[ date ]</a>
77 <a href="thread.html#2948">[ thread ]</a>
78 <a href="subject.html#2948">[ subject ]</a>
79 <a href="author.html#2948">[ author ]</a>
80 </LI>
81 </UL>
82
83 </body></html>