/[cvs]/eggdrop1.6/doc/BOTNET
ViewVC logotype

Annotation of /eggdrop1.6/doc/BOTNET

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.9 - (hide annotations) (download)
Sat Dec 29 21:46:29 2001 UTC (19 years, 3 months ago) by guppy
Branch: MAIN
Changes since 1.8: +155 -254 lines
added Wcc's patch to update some more docs

1 guppy 1.9 BOTNET SHARING AND LINKING v2.1 29 Dec 2000
2 segfault 1.1
3    
4    
5     INDEX
6    
7 guppy 1.9 I. ABOUT THIS DOCUMENT
8     II. TERMS USED
9     III. WHAT IS A BOTNET?
10     IV. ADDING AND LINKING BOTS
11     V. USING BOTFLAGS
12     VI. MAKING BOTS SHARE USER RECORDS
13 segfault 1.1
14    
15    
16    
17    
18     I. ABOUT THIS DOCUMENT
19    
20 guppy 1.9 The purpose of this document is to show you what a botnet is and how
21     it could be useful to you. It also covers botflags userfile sharing.
22 segfault 1.1
23    
24     II. TERMS USED
25    
26 guppy 1.9 The following are some common terms used in this document:
27 segfault 1.1
28    
29 guppy 1.9 Botnet
30     A botnet consists of one or more bots connected together.
31 segfault 1.1
32    
33 guppy 1.9 Link
34     The term that means the actual linking of a bot
35 segfault 1.1
36    
37 guppy 1.9 Hub
38     A bot is described as a hub-bot if one or more bots are linked to
39     it.
40 segfault 1.1
41    
42 guppy 1.9 Leaf
43     A leaf is a non-hub bot connecting to a hub-bot. A leaf has only
44     one other bot connected to it, its hub. Leaf bots can be assigned
45     the "l" botattr flag to prevent other bots from linking to them.
46 segfault 1.1
47    
48 guppy 1.9 Link Bot
49     A link-bot is a bot that is linked to another bot. It may or may not
50     be a hub-bot.
51 segfault 1.1
52    
53 guppy 1.9 Share
54     Share is the term used to describe the sharing of user records.
55 segfault 1.1
56    
57 guppy 1.9 Share Bots
58     A share-bot is a bot which shares user records with one or more
59     linked bots.
60 segfault 1.1
61    
62 guppy 1.9 Aggressive Share
63     Aggressive share is a term used to describe the direction of sharing
64     user-files. Aggressive share bots will SEND userfiles to another passive
65     bot.
66 segfault 1.1
67    
68 guppy 1.9 Passive Share
69     Passive share is a term used to describe the direction of sharing
70     user-files. Passive share bots will accept userfiles from an aggressive
71     share bot.
72 segfault 1.1
73 guppy 1.9 Example bottree:
74 segfault 1.1
75 guppy 1.9 BotA
76     |-+BotB
77     `-+BotC
78 segfault 1.1
79 guppy 1.9 BotB is linked to a master sharebot, BotA, and a slave sharebot, BotC.
80     BotB shares passively with [receives from] BotA and shares aggressive
81     with [sends to] BotC.
82 segfault 1.1
83 fabian 1.3
84 guppy 1.9 Bot Flags
85     Flags are attributes that determine what a bot can or is allowed to do.
86     Flags can be either global (such as +s) or channel specific (such as
87     |+s #lamest). See '.help botattr' for help with setting these flags.
88    
89     The following is a list of valid bot flags:
90    
91     s share aggressively (SEND userfile to a passive bot)
92     p share passively (ACCEPT userfile from an aggressive bot)
93     g global share (share all channels)
94     h hub (automatically link to this bot)
95     a alternate (automatically link to this bot if the hub bot can't be
96     linked)
97     l leaf (bot is not allowed to link in other bots)
98     r reject (bot will not be allowed to link)
99     i isolate (isolate the party line across a bot link)
100     0-9 user defined flags
101 segfault 1.1
102    
103    
104 guppy 1.9 Address
105     The physical address, containing the address and port of the bot.
106     For example: lame.org:3333. You can change a bot's address with
107     ".chaddr <botname> <hostaddress:botport[/userport]>".
108 segfault 1.1
109    
110 guppy 1.9 Relay
111     The relay port number of the bot is defined in the config file.
112     Note that you can define one port for bots and another for user
113     connections. You can use ".relay <botname>" to relay to another
114     bot.
115 segfault 1.1
116    
117 guppy 1.9 Relay Connection
118     A relay connection is used to relay (jump) to another bot via telnet
119     or DCC chat. You can relay to another bot even if the remote bot is
120     not linked. You can use ".relay <botname>" to relay to another bot.
121 segfault 1.1
122    
123 guppy 1.9 Port
124     The telnet port is used by the bot to communicate with other bots
125     and/or users. Note that you can define separate ports for user and bot
126     connections.
127 segfault 1.1
128    
129    
130    
131 guppy 1.9 III. WHAT IS A BOTNET?
132 segfault 1.1
133 guppy 1.9 A botnet consists of one or more bots linked together. This can allow bots
134     to op each other securely, control floods efficiently, and share user lists,
135     ban lists, exempt/invite lists, and ignore lists (if sharing is enabled).
136 segfault 1.1
137    
138     IV. ADDING AND LINKING BOTS
139    
140 guppy 1.9 With the common terms out of the way, we can start with the process of
141     linking two bots. Before you start, you need to know the address and
142     port of each bot you wish to link.
143 segfault 1.1
144 guppy 1.9 Here is an example senario:
145    
146     BotA is on lame.org listening on port 3333, and BotB is on irc.org
147     listening on port 4444. First, you have to add each Bot to the other's
148     userfile. On BotA, you would type '.+bot BotB irc.org:4444'. If BotB is
149     on a common channel with BotA, BotB's hostmask is automatically added.
150     Otherwise, you have to add the hostmask manually with the '.+host'
151     command. On BotB, you would type '.+bot BotA lame.org:3333'.
152 segfault 1.1
153 guppy 1.9 At this point, you can link the two bots by typing '.link BotA' on BotB (or
154     '.link BotB' on BotA). The bots will now give themselves random passwords
155     which are *not* stored encrypted in the userfile. Note that you can link as
156     many bots as you wish to your botnet.
157 segfault 1.1
158    
159    
160    
161 guppy 1.9 V. USING BOTFLAGS
162 segfault 1.1
163 guppy 1.9 Botflags are needed to assign special functions and tasks to your bots.
164     Bot flags are set with the '.botattr' command. See '.help botattr' for
165     help with this command. The following is a list of botflags and their
166     functions:
167 segfault 1.1
168 guppy 1.9 "h" (hub)
169     If you want your bot(s) to automatically link/relink, you can assign
170     the +h botflag each bot's hub. Note that if you set multiple bots +h,
171     the bot only attempts to link to one.
172 segfault 1.1
173    
174 guppy 1.9 "a" (alternate)
175     If your bots are, for some reason, unable to link to their hub, they
176     will attempt to connect to an alternate hub. You can assign a bot as
177     an alternate hub by giving it the +a botflag.
178 segfault 1.1
179    
180 guppy 1.9 "l" (leaf)
181     This flag, assigned to a link bot, will prevent the link bot from linking
182     other bots to your botnet.
183 segfault 1.1
184    
185 guppy 1.9 "r" (reject)
186     If you assign this flag to a link bot, the link bot will not be allowed
187     to link to the botnet.
188 segfault 1.1
189    
190 guppy 1.9 "i" (isolate)
191     This flag isolates a link bot's partyline from the rest of the botnet.
192     Anything said on the link bot's partyline won't appear on the rest of
193     the botnet.
194 segfault 1.1
195    
196 guppy 1.9 "s" (SEND userfile to)
197     +s Giving a link bot this flag will make the bot share aggressively
198     with the link bot. See 'Aggressive Share' in section II of this
199     document for more information on aggressive sharing.
200 segfault 1.1
201 guppy 1.9 |s +s bots need this flag for each channel you want to share.
202 segfault 1.1
203    
204 guppy 1.9 "p" (ACCEPT userfile from)
205     Giving a link bot this flag will make the bot share passively
206     with the link bot. See 'Passive Share' in section II of this
207     document for more information on passive sharing.
208 segfault 1.1
209    
210 guppy 1.9 "g" (global share)
211     This flag allows the sharing of all channels with a link bot.
212 segfault 1.1
213    
214 guppy 1.9 "0-9" (user-defined)
215     These 10 flags are user-defined can be used by scripters.
216 segfault 1.1
217    
218    
219 guppy 1.9 VI. MAKING BOTS SHARE USER RECORDS
220 segfault 1.1
221 guppy 1.9 Before you start preparing your bots for sharing, make sure that
222     you've loaded the transfer and share modules. You also have to ensure
223     that each channel you wish to share is set +shared (see '.help chanset'
224     and '.help chaninfo').
225 segfault 1.1
226 guppy 1.9 By using specific botflags, you can cause your bot to share aggressively
227     with some link bots, and passively with others. For sharing to work, flags
228     must be set properly on both the passive and the aggressive bots. An aggressive
229     bot will not share userfiles with another aggressive bot; a passive bot will
230     not share userfiles with another passive bot.
231 segfault 1.1
232 guppy 1.9 A bot will send userfiles to any bots with the +s botflag.
233 segfault 1.1
234 guppy 1.9 A bot will accept userfiles from any bot with the +p botflag.
235 segfault 1.1
236 guppy 1.9 Giving BotB the +s botflag on BotA will not make BotB accept BotA's userfile.
237     It will only make BotA attempt to send its userfile to BotB.
238 segfault 1.1
239 guppy 1.9 Giving BotA the +p botflag on BotB will not make BotA send its userfile
240     to BotB. It will only give BotA permission to send BotB a userfile.
241 segfault 1.1
242 guppy 1.9 If the flags on both bots do not create a +s+p pair, the bots will link but
243     will not share. If the +s+p pair is set properly, but the userfile transfer
244     fails for some reason, the bots will unlink.
245 segfault 1.1
246 guppy 1.9 Note that by sharing user records, bans, invites, exempts and
247     ignores will automatically be shared. Botflags are *not* shared.
248 segfault 1.1
249    
250    
251     Hope that this document helped you in some way...
252    
253 guppy 1.9 The Dev-Team

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23