Wraith Features
This page is currently under development. It was last updated
General
- Bot is written in a C/C++ mix. (slowly merging into a C++ OOP design)
- Code base of Eggdrop 1.6.12 (The code has evolved so much that it can't even be compared to a stock Eggdrop anymore.)
- TCL is not required nor is it supported.
- No module support
- Initially influenced by the ghost botpack
- There is only one version of a binary for each Operating System (i.e. hub and leaf binaries are identical).
- Leaf bots act like dummy drones and save no botnet settings or files locally.
- Only hubs store userfiles and temp data on shell; userfiles are sent to leafs during link and stored in runtime memory (1.3).
- Userfiles store information about channels, users, and settings.
- Binaries store information about bots internally; no config files used.
- One binary stores multiple bots inside it. (Each bot gets its own process id)
- Bots are quick and easy to setup
- A botnet can be easily updated with new binaries from the hub. (see Updating)
- Customizable DCC cmd prefix (i.e. !cmd %cmd *cmd)
- IPv6 support for IRC/botnet
- Asynchronous DNS
Encryption
- All botnet traffic/files are encrypted with AES-256+base64.
- Binaries store an assortment of MD5 checksums internally and verify them upon starting.
- Binaries store data about bots internally with AES-256 encryption.
- Botnet keys are randomly regenerated.
DCC
- Secure login using AuthSystem
- Separation of cmds on hub and leaf bots
- Remote control of leaf bots from hubs
- Users cannot access/view users of higher level (see WhoisRestrictions).
IRC
- Hubs do not connect to IRC.
- Autoaway at random intervals
- Client cloaking (CTCPs / version)
- Mass op/deop protections
- Manual op protections
- Op cookies using custom hash/encryption scheme to protect from network stream hijack.
- Op cookies support opping multiple clients.
- +take channel flag to quickly op botnet and mass deop channel
- No user exemptions with flags or otherwise: I.e. if you manually op in a channel set to +dk, nobody -- including you -- is exempt.
- +bitch channel flag uses multiple methods of protection.
- Pre-defined list of kick reasons
- Auto-limiter algorithm sets channel limit only when needed.
- Configurable auto-voicer
- CIDR ban support
- Bots can dns clients to see if they match users. (+r)
- Bots prefer requesting op from bots on same server or from a list of bots sorted by hops.
- Bots regain nicks
- Home channel support.
Users
- CIDR hostmask support
- Multiple levels of control through flags
- "Perm" owners are statically defined in the binaries.
- Sensitive control is through userflag +a (admin -- shell access, bot configuration, etc.).
- Botnet control is through userflag +n (owner).
- User control is through userflag +m (master).
- Channel control is through userflag +o (op).
Leaf Bots
- Botnet list is not visible.
- Hubs are not visible.
- Hostmask not visible in whois
- Only bots with +c flag will accept /dcc chat or /ctcp CHAT.
- No static telnet access
- Ports opened for /ctcp CHAT are automatically closed after a minute.
- Cloaked responses for /dcc chat and /ctcp CHAT
- Userfile and other settings are not saved locally.
- Bot data (bot.conf) stored internally in binary
- One binary may contain multiple bots..
- One binary may spawn multiple bots..
- Each bot gets its own process. (Not emech style or threaded)
Botnet
- All user/channel settings are shared automatically.
- Users need userflag +j to access leaf bots.
- Users need userflag +i to access hub bots through telnet or .relay.
- Users need userflag +p to speak on partyline.
Removed eggdrop features
- Modules
- TCL
- File area (filesys.mod)
- Greet
- userflag +f (friend)
- userflag +t (botmaster)
- userflag +a (auto-op, replaced by +O)
- Misc. channel flags
- Blowfish
- Assoc.mod
- Seen.mod
