Changes between Version 32 and Version 33 of Features


Ignore:
Timestamp:
May 4, 2013, 3:22:08 PM (5 years ago)
Author:
bryan
Comment:

Move to github

Legend:

Unmodified
Added
Removed
Modified
  • Features

    v32 v33  
    11= Wraith Features =
    22
    3 This page is currently under development. It was last updated [[LastModified()]]
    4 
    5 
    6 [[PageOutline(2,,inline)]]
    7 
    8 == General ==
    9  * Bot is written in a C/C++ mix. (slowly merging into a C++ OOP design)
    10  * Code base of [http://www.eggheads.org Eggdrop] 1.6.12 (The code has evolved so much that it can't even be compared to a stock Eggdrop anymore.)
    11  * TCL is '''not''' required nor is it supported.
    12  * No module support
    13  * Initially influenced by the [http://ghost.botpack.net ghost botpack]
    14  * There is only one version of a binary for each Operating System (i.e. hub and leaf binaries are identical).
    15  * Leaf bots act like dummy drones and save no botnet settings or files locally.
    16  * Only hubs store userfiles and temp data on shell; userfiles are sent to leafs during link and stored in runtime memory (1.3).
    17  * Userfiles store information about channels, users, and settings.
    18  * Binaries store information about bots [wiki:BotConfig internally]; no config files used.
    19  * One binary [wiki:BotConfig stores multiple bots inside it]. (Each bot gets its own process id)
    20  * Bots are quick and easy to [wiki:BotnetSetup setup]
    21  * A botnet can be '''easily''' updated with new binaries from the hub. (see [wiki:Updating])
    22  * Customizable DCC cmd prefix (i.e. !cmd %cmd *cmd)
    23  * IPv6 support for IRC/botnet
    24  * Asynchronous DNS
    25  * Easy default channel setting modifying with pseudo channel 'default'
    26  * No extra ports needed for userfile sharing, only the HUB port needs to be opened.
    27  * Passwords are stored in a SaltedSHA1 format.
    28 
    29 == Encryption ==
    30  * All botnet traffic/files are encrypted with [http://en.wikipedia.org/wiki/Advanced_Encryption_Standard AES-256]+base64.
    31  * Binaries store an assortment of MD5 checksums internally and verify them upon starting.
    32  * Binaries store data about bots internally with AES-256 encryption.
    33  * Botnet keys are randomly regenerated.
    34  * Preliminary support for [http://fish.secure.la/ FiSH]
    35 
    36 == DCC ==
    37  * Secure login using AuthSystem
    38  * Separation of cmds on hub and leaf bots
    39  * Remote control of leaf bots from hubs
    40  * Users cannot access/view users of higher level (see WhoisRestrictions).
    41  * Encrypted .relay between bots
    42  
    43 == IRC ==
    44  * Hubs do not connect to IRC.
    45  * Autoaway at random intervals
    46  * Client cloaking (CTCPs / version)
    47  * Mass op/deop protections
    48  * Manual op protections
    49  * [wiki:CookieOps Op cookies] using custom hash/encryption scheme to protect from network stream hijack.
    50  * [wiki:CookieOps Op cookies] support opping multiple clients.
    51  * +take channel flag to quickly op botnet and mass deop channel
    52  * No user exemptions with flags or otherwise: I.e. if you manually op in a channel set to +dk, nobody -- including you -- is exempt.
    53  * +bitch channel flag uses multiple methods of protection.
    54  * Pre-defined list of kick reasons
    55  * Auto-limiter algorithm sets channel limit only when needed.
    56  * Configurable auto-voicer
    57  * [http://svn.ratbox.org/svnroot/ircd-ratbox/trunk/doc/CIDR.txt CIDR] ban support
    58  * Bots DNS clients to see if they match users/bans. (+r)
    59  * Bots prefer requesting op from bots on same server or from a list of bots sorted by hops.
    60  * Bots regain nicks automatically.
    61   * Jupenick is used for regaining your own nick, without the bot alternating on that nick.
    62  * [wiki:Homechan Home channel] support.
    63  * RBL banning support.
    64  * In-channel control of bots via AuthSystem.
    65  * Native support for floodless ilines.
    66  * Bot is optimized for [http://www.ircd-ratbox.org/ Ratbox] and [http://www.efnet.org EFNet], but should work on most IRCDs fine.
    67  * [http://www.irc.org/tech_docs/005.html 005 numeric] support. All on by default, if supported:
    68   * [http://svn.ratbox.org/svnroot/ircd-ratbox/trunk/doc/modeg.txt CALLERID] support. Users are automatically accepted.
    69   * DEAF support. No channel text is sent to bot unless it has [wiki:AuthSystem authed] users on it.
    70   * [http://svn.ratbox.org/svnroot/ircd-ratbox/trunk/doc/monitor.txt MONITOR] support.
    71   * KNOCK support.
    72   * [http://ircu.sourceforge.net/release.2.10.02-cprivmsg.html CPRIVMSG/CNOTICE] support.
    73   * [http://ircu.sourceforge.net/release.2.10.01-who.html WHOX] support. (Can help the bot know the IPs of clients without DNSing them)
    74  * Easy nickname release commands for regaining your nickname from a bot.
    75  * Voicebitch support for enforcing only certain users/hostmasks being voiced.
    76  * Protection from MAX SendQ from WHO requests replies.
    77 
    78 == Users ==
    79  * [http://svn.ratbox.org/svnroot/ircd-ratbox/trunk/doc/CIDR.txt CIDR] hostmask support
    80  * Multiple levels of control through flags
    81  * "Perm" owners are statically defined in the binaries.
    82  * Sensitive control is through userflag +a (admin -- shell access, bot configuration, etc.).
    83  * Botnet control is through userflag +n (owner).
    84  * User control is through userflag +m (master).
    85  * Channel control is through userflag +o (op).
    86 
    87 
    88 == Leaf Bots ==
    89  * Botnet list is not visible.
    90  * Hubs are not visible.
    91  * Hostmask not visible in whois
    92  * Only bots with +c flag will accept /dcc chat or /ctcp CHAT.
    93  * No static telnet access
    94  * Ports opened for /ctcp CHAT are automatically closed after a minute.
    95  * Cloaked responses for /dcc chat and /ctcp CHAT
    96  * Userfile and other settings are not saved locally.
    97  * Bot data (bot.conf) stored [wiki:BotConfig internally in binary]
    98  * One binary may contain multiple bots..
    99  * One binary may spawn multiple bots..
    100  * Each bot gets its own process. (Not emech style or threaded)
    101 
    102 == Shells ==
    103  * Bot config is password protected.
    104  * Bot automatically sets up a crontab entry.
    105  * All bots on the shell go into 1 binary. Each bots spawns its own process.
    106  * Bots on the same shell will link to the first bot in the binary (the localhub). The only the localhub links to the actual hubs.
    107 
    108 == Botnet ==
    109  * All user/channel settings are shared automatically.
    110  * Users need userflag +j to access leaf bots.
    111  * Users need userflag +i to access hub bots through telnet or .relay.
    112  * Users need userflag +p to speak on partyline.
    113 
    114 == Removed eggdrop features ==
    115  * Modules
    116  * TCL
    117  * File area (filesys.mod)
    118  * Greet
    119  * userflag +f (friend)
    120  * userflag +t (botmaster)
    121  * userflag +a (auto-op, replaced by +O)
    122  * Misc. channel flags
    123  * Blowfish
    124  * Assoc.mod
    125  * Seen.mod
    126 
    127  
    128 [[Poll(Was this article helpful?; Yes; No)]]
    129 
    130 [[TagIt()]]
    131 
     3See http://github.com/wraith/wraith/blob/master/FEATURES.md