-
Notifications
You must be signed in to change notification settings - Fork 14
/
sample.conf
111 lines (100 loc) · 2.74 KB
/
sample.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
;
; server connection timeout limit = 60 seconds
;
set ctimeout 60
;
; add some servers to the serverlist
;
; We don't currently support SSL or ipv6 but there's an easy workaround
; see socat.sh
servergroup undernet
server amsterdam.nl.eu.undernet.org 6663
server amsterdam2.nl.eu.undernet.org 6663
server bucharest.ro.eu.undernet.org 6663
server carouge.ch.eu.undernet.org 6663
server ede.nl.eu.undernet.org 6669
server elsene.be.eu.undernet.org 6669
server fulda.de.eu.undernet.org 6663
server geneva.ch.eu.undernet.org 6663
server graz.at.eu.undernet.org 6663
server graz2.at.eu.undernet.org 6663
server helsinki.fi.eu.undernet.org 6669
server lelystad.nl.eu.undernet.org 6668
server london.uk.eu.undernet.org 6666
server london2.uk.eu.undernet.org 6663
server milan.it.eu.undernet.org 6663
server oslo1.no.eu.undernet.org 6663
server oslo2.no.eu.undernet.org 6663
server stockholm.se.eu.undernet.org 6669
server surrey.uk.eu.undernet.org 6669
server zagreb.hr.eu.undernet.org 6666
server panamacity.pa.undernet.org 6663
server ashburn.va.us.undernet.org 6663
server fairfax.va.us.undernet.org 6666
server mesa.az.us.undernet.org 6666
server miami.fl.us.undernet.org 6669
server princeton.nj.us.undernet.org 6663
server sanjose.ca.us.undernet.org 6663
server sterling.va.us.undernet.org 6669
;
; this is sorta how a botnet configuration would look like...
;
set linkport 5000
set linkpass your_lame_password
set autolink 1
;
; what other bots are out there in cyberspace?
;
; link <guid> <password> [host port]
;
; guid the other bots guid
; password the other bots password
; host internet host to connect to when linking the other bot
; port tcp port to connect to on remote host
;
link 2 janes_password janes.host.com 5000 ; Jane Does EnergyMech
link 3 johns_password johns.host.com 5000 ; John Does EnergyMech
;
; we cant connect -to- bot 4, but we can accept connections from it!
;
link 4 ongabonga_pass
;
; thats all the botnet stuff for now
;
;
; create a new bot
;
; 1 the globally uniqe ID (guid), used for botnet linking (0-65536)
; Note: dont use a common number unless you are dead certain that
; your bot will never link to any other. Changing guid can be a mess.
; emech3 the bots nick
;
nick 1 emech3
set altnick myemech3 monkey3 dummy3 fuzzy3
;
; set connection variables for this bot
;
set servergroup undernet
set userfile mech.passwd
set ident robot
set ircname EnergyMech 3: The Next Generation
set umodes +w
set cmdchar .
set modes 6
set cc 1
;
; join a channel
;
join #anychannel
set pub 1
set aop 1
set avoice 1
set prot 4
;
; this is how you'd load a tcl on startup...
;
tclscript does-not-exist.tcl
;
; Can you guess?
;
die You did not edit your configuation file!