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

Contents of /eggdrop1.6/doc/BOTNET

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


Revision 1.9 - (show 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 BOTNET SHARING AND LINKING v2.1 29 Dec 2000
2
3
4
5 INDEX
6
7 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
14
15
16
17
18 I. ABOUT THIS DOCUMENT
19
20 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
23
24 II. TERMS USED
25
26 The following are some common terms used in this document:
27
28
29 Botnet
30 A botnet consists of one or more bots connected together.
31
32
33 Link
34 The term that means the actual linking of a bot
35
36
37 Hub
38 A bot is described as a hub-bot if one or more bots are linked to
39 it.
40
41
42 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
47
48 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
52
53 Share
54 Share is the term used to describe the sharing of user records.
55
56
57 Share Bots
58 A share-bot is a bot which shares user records with one or more
59 linked bots.
60
61
62 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
67
68 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
73 Example bottree:
74
75 BotA
76 |-+BotB
77 `-+BotC
78
79 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
83
84 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
102
103
104 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
109
110 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
116
117 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
122
123 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
128
129
130
131 III. WHAT IS A BOTNET?
132
133 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
137
138 IV. ADDING AND LINKING BOTS
139
140 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
144 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
153 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
158
159
160
161 V. USING BOTFLAGS
162
163 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
168 "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
173
174 "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
179
180 "l" (leaf)
181 This flag, assigned to a link bot, will prevent the link bot from linking
182 other bots to your botnet.
183
184
185 "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
189
190 "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
195
196 "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
201 |s +s bots need this flag for each channel you want to share.
202
203
204 "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
209
210 "g" (global share)
211 This flag allows the sharing of all channels with a link bot.
212
213
214 "0-9" (user-defined)
215 These 10 flags are user-defined can be used by scripters.
216
217
218
219 VI. MAKING BOTS SHARE USER RECORDS
220
221 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
226 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
232 A bot will send userfiles to any bots with the +s botflag.
233
234 A bot will accept userfiles from any bot with the +p botflag.
235
236 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
239 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
242 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
246 Note that by sharing user records, bans, invites, exempts and
247 ignores will automatically be shared. Botflags are *not* shared.
248
249
250
251 Hope that this document helped you in some way...
252
253 The Dev-Team

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23