All Activity

This stream auto-updates     

  1. Last week
  2. BlackToolS 2.5.2

    Ultima versiune a scriptului BlackToolS este v2.5.2, pe care o puteti descarca de mai jos. Pentru mai multe info consultati manualul tcl-ului (vedeti comanda .man). Minimum requirements: o Eggdrop 1.8.x o Tcl 8.5 or higher. The major changes in the release include: - CIDR support - dnslookup support - webirc hosts support - securemode: multiple random code messages - antijoinflood: combined antijoinflood + antijoinpartquit - owner notes: turn ON/OFF - silence: eggdrop botnet personal protection - banlist cleaner: remove N bans on full banlist - global ban disctinction: (global) - consecutive chars: new protection - badchan: fixed ipv6 issue - badnick: extra option badnick-bmethod - idle: minor bugs fixed - add: combined add + adduser - userlist: minor bugs fixed - inviteban: exception for Undernet Official Bot *X* - major coding changes for better and faster performance We offer a lot of support for BlackTools scripts, however you can also support us: Donations will help me to keep working on this project.
  3. Version 2.5.2

    6 downloads

    ============================================================================================ -= BLaCkShaDoW Production Presents =- BlackTools - The Ultimate Channel Control Script One TCL. One smart Eggdrop ============================================================================================ BlackTools is the most complete channel management script who can manage channels from all the IRC networks, although some modules are specifically designed only for Undernet network. ----------------------- Minimum requirements: o Eggdrop 1.8.x o Tcl 8.5 or higher. Most important features: 2.5.2 Most important changes (summary) **** GENERAL CHANGES - Major coding changes for better and faster performance. -- Added a helpful information system to show, after each info request from BlackTools manual, some important TIPS about how to use this script. --- All major protections supports now addition of exceptions and customization of the ban method on each word. ----- The bot now understands some CIDR notation and dnslookup bans. ------ All protections and ban methods recognize webirc hostmask like: mibbit.com, kiwiirc.com, irccloud.com. **** IDLE - Code fixes and enhancements. -- Minor bugs fixed. **** SECUREMODE - Added multiple random code messages for a better security. **** ANTIJOINFLOOD - Recoded and combined antijoinflood with antijoinpartquit in only one protection. **** TOPWORDS - Upgraded to show more statistical informations about: smiles, actions, questions, etc. **** NOTES - Automated abuse system to report directly to the BOSS OWNER. -- Possibility for owners to decide whether they want to receive notes or not. **** SILENCE - Added a personal protection for the bot against ctcp, notice, msg & ctcr using the server silence command. **** AWAYACTION - warn-ban-kick -- Changed the output method of showing the adverts. **** BANLIST CLEANER - Implementated an automatic banlist clean system to remove a certain number of bans when the channel banlist is full. **** BANS DISTICTIONS - Added (global) to distinguish local bans from global ones. **** CONSECUTIVE LETTERS PROTECT - Added a new protection againts chars/consecutive repeated letters. **** REPORT SYSTEM - Added a flood protection settings against those who abuse the use of command. -- Added the possibility that the report to be sent in eggdrop's PRIVMSG. **** BADCHAN - Code fixes and enhancements. -- Added extra option ShowBadChan-bwait and words to be exempted. --- Minor bugs fixed. **** BADNICK - Added extra an option badnick-bmethod. -- You can now add words to be exempted. **** BADIDENT - Added possibility of being able to modify the banmask method. --- You can now add words to be exempted. **** INVITEBAN - Added exception for Undernet Official Bot *X*. **** QUOTE - Minor text fixes: spelling and grammar mistakes. -- Minor bugs fixed. **** CP SYSTEM - Some major bugs fixed. **** SEEN - Minor bugs fixed. **** XTOOLS - Minor bugs fixed. **** LINK SYSTEM - Minor bugs fixed. **** BADREALNAME - Minor bugs fixed. **** ADD/ADDUSER/USERLIST - Minor bugs fixed. -- Removed the adduser command and included all it's functions to the add command. **** COUNT - Reintroduced count module, but only as informative thing and how to use it. **** ANTISPAM - Added exception from on-join message for all users with access. **** ANTISPAM - Minor bugs fixed. **** STATS - Reintroduced the statistics for ban commands used by each user with access. * Read BlackTools MANUAL for more info about how to use it. ** Read INSTALL file to know how to install it. *** Read FAQ file for the most frequently asked questions. We offer a lot of support for BlackTools - however you can also support us: Donations will help us to keep working on this project.

    Free

  4. Earlier
  5. 10 Years of BT, new version release

    This week the BlackTools TCL project celebrates its 10th anniversary. Back in 2008, Daniel V. (aka BLaCkShaDoW), an enthusiastic student of computers and programming, revealed his intentions to write a manipulation tcl script which in its structure to contain all the necessary functionalities in managing IRC channels and giving it free to use to the eggdrops lovers. The script had to be developed in such a way that people no longer needed to use any other tcl scripts for different functionalities. And so, on February 15th, 10 years ago today, BLaCkShaDoW announced the availability of the 1st version of “BlackTools” script on Undernet IRC Network (later on, the tcl to becomes "a very popular one"). Since its public release the project has been evolving in many ways, being tested and used by a lot of people. Their new ideas and suggestions were so many, that he needed assistence in adding new features to the script architecture. That's why, between 2009 and 2012, BLaCkShaDoW collaborated with Time2Go to define the script new vision and improve users experience. Thanks to this collaboration BT’s has become more conventional for users, and various functions have become more efficient to manage channels and easy to use. But more importantly, they got a much better idea how people want this script to be 'designed'. Over the years, BlackToos amassed a huge amount of new features designed for all kinds of users and practical commands (general channel management, channel protections, etc.) based on users feedback. In the past two years BLaCkShaDoW and Florian been working hard on making BlackTools a complete channel management script. The new 2.5.x series made us rewrite or at least tweak pretty much every part of BT’s source code. Fortunately, this work is nearing completion, and you’ll soon be able to benefit from all the changes that it’s bringing. To celebrate the 10th anniversary, we release one last update to end the 2.5.x series of BlackTools. Newly released BT 2.5.2 includes some much needed improvements, fixes for bans support in CIDR, various user commands improvements, BUGs build system fixes, translation updates and many more changes. At the end of 2017, thanks to all recent updates and various re-delelopments, BlackTools has become the most popular and most-used tcl script. With this last release, we shall complete the BlackTools TCL Project for public audience. When it’s done and out, we shall finally be able to get started on some very exciting and private solutions. Please read this link for more details. For more info about updates, read release notes. ------------------ Kind regards, TCLscripts Team E-mail info [at] tclscripts [dot] net with any suggestions or comments TCLscripts URL: http://www.tclscripts.net BlackTools URL: http://blacktools.tclscripts.net
  6. ($) Tcl Scripting

    You want a customised TCL Script for your eggdrop? Easy-peasy, just tell us what you need! We can create almost anything in TCL based on your ideas and donations. Email blackshadow@tclscripts.net or info@tclscripts.net with your request informations and we'll contact you as soon as possible. * Your donations to this work will be welcome and much appreciated, so that we can continue to serve the development of BlackTools script and for helping our website stay active and stable. ----------------- Vrei un TCL script personalizat pentru eggdropul tau? Nimic mai simplu, doar spune-ne ce ai dori! Putem crea aproape orice TCL pe baza ideilor si donatiilor tale. Email blackshadow@tclscripts.net or info@tclscripts.net cu informatiile solicitate si va vom contacta cat mai curand posibil. * Donatiile pentru aceste lucrari vor fi binevenite si foarte apreciate, astfel incat sa putem continua dezvoltarea scriptului BlackTools si pentru a ajuta siteul nostru sa ramana activ si stabil.
  7. 1. Commands for +P users (partyline access) .addlog <text> Allows you to add a message to the eggdrops log if something needs explaining, such as an eggdrop conflict. It will include your handle. .away <message> Set you away on the party line only. .back Back from away on the partyline only. .botinfo Returns a line for each eggdrop on the botnet with version, uptime, etc. .bots Returns a list of eggdrops on the botnet. .bottree Returns a list of eggdrops whcih are linked (if there are any linked eggdrops). .channel <#channel> Returns a list of the users on that channel. .console <#channel> <+|-modes> Changes your console modes for that channel. .dob <your date of birth> Sets your birthday in your whois in the eggdrop. .echo <off|on> Turns the repeat of what you say in the party line to others as off/on. .email <your email addy> Sets an email addy in your whois on the eggdrop. .email none Removes your listed email in the eggdrop. .help Returns a list of commands. .help all Returns a longer list of commends. .help whois Returns a lengthy defined list of user/eggdrop flags. .help <command> Returns the explanation on the specified command. .info <#channel> <infoline> Sets your infoline in the whois in the eggdrop. .irl <name> Sets your real name in the whois in the eggdrop. .match <+|-flags> <#channel> Finds what matches your search on the eggdrop. .motd Returns the MOTD that you saw when you first connected in DCC with the eggdrop. .newpass <new password> Changes your password on the eggdrop. .nick <newnick> Changes your nickname in the eggdrop only. .notes erase <index|all> Deletes the specified notes. .notes index Returns a list of notes left on the eggdrop for you. .note <handle> <message> Leaves a note for that user. .notes read <index|all> Returns a list of notes. .quit [message] Disconnects you on the partyline only. .strip <modes> Allows you to strip certain modes in the partyline, such as ASCII, bold, color, underline, etc. .su <handle> Allows you to change your nickname in the partyline to one that is on the eggdrops access list, if you know their password. .trace <botnick> Returns a list of eggdrops between the one you are on and the one you traced, if you have eggdrops that are linked. .url <your URL> Sets a URL in your whois in the eggdrop. .url none Removes your URL in the eggdrop. .vbottree Returns a list of eggdrops which are linked (if there are any linked eggdrops) along with their version of eggdrop. .who Returns a list of users on that eggdrop. .whom Returns a list of users on the botnet (if the eggdrops are linked). .whois <handle> Returns the users flags and added hostmasks. 2. Commands for +O users (channel ops) .act [#channel] <action> Allows you to send an action (like the /me smiles command) to a channel as if the eggdrop performed the action. .+ban <hostmask> [#channel] [time] [reason] Sets a ban on that hostmask. .-ban <hostmask|index> Deletes a ban from the eggdrop banlist. .bans <#channel|*|all> Returns a list of bans on the eggdrop. .deop <nickname> [#channel] Deops (-o) the specified user, only if they do not have a +o on that channel in the eggdrops access list. .devoice <nickname> [#channel] Devoices (-v) the specified user, only if they do not have a +v on that channel in the eggdrops access list. .+exempt <hostmask> [#channel] [time] [reason] Exempts a user from kicks/bans .-exempt <hostmask|index> Removes a user from the exempt list. .exempt <channel|*|all> Returns a list of all who are exempt from kicks/bans. .+invites <hostmask> [#channel] [time] [reason] Invites are set the same way as bans above. .-invite <hostmask|index> Deletes a user from the invite list. .invites <#channel|*|all> Returns a list of users on the invite list. .invite <nickname> [#channel] Invites the specified user to the specified channel. .kick <nickname> [#channel] [reason] Kicks the specified user off of the channel. If no reason is given the default is 'requested'. .kickban <nickname> [#channel] [reason] Kicks and bans the user off the channel. If no reason is given the default is 'requested'. .msg <handle> <text> Allows a global +o/op (not a channel +o/op) to send private messages/queries through the eggdrop to users, as if the eggdrop sent the message. .op <nickname> [#channel] Gives the specified user temporary +o/op status in the channel specified. .resetbans <#channel> Resets the ban list so that any bans not in the eggdrops permanent ban list will be removed. .resetexempts <#channel> Resets the exempt list so that any bans not in the eggdrops permanent exempt list will be removed. .resetinvites <#channel> Resets the invites list so that any bans not in the eggdrops permanent invites list will be removed. .say [#channel] <message> Allows you to say something through the eggdrop to the channel. .stick <ban|exempt|invite> <hostmask|index> Adds the ban or exempt or invite permanently to the specified list. .topic <message> Changes the topic. .unstick <ban|exempt|invite> <hostmask|index> Removes the permanent status of the ban or exempt or invite and it then reverts to the time set in the eggdrops config-file. .voice <nickname> [#channel] Gives the specified user temporary +v/voice status in the channel specified. 3. Commands for +M users (channel masters) .adduser <handle|nickname> Creates a record for the specified added user. .chaninfo <#channel> Returns a list of all the channels modes set through the eggdrop. Most can be changed in DCC rather than in the eggdrops config-file. .chinfo <handle> <#channel> <info-line> Sets an info-line for that user. .+chrec <handle> [#channel] Adds an empty channel so that laston and userlines can be stored. .-chrec <handle> [#channel] Removes the stored channel record, which includes laston, userlines and flags. .deluser <handle> Deletes the specified user from the eggdrops records. 4. Commands for +N users (channel owners) .chanload Allows you to fix something you may have changed. It goes back to the file that was last saved. .chansave Saves the channel modes to a file when the eggdrop is rehashed or restarted. .chanset <#channel> <settings> Allows you to change most channel modes and settings. i.e. +nt or +seen +chan <#channel> Adds a channel to the list of channels the eggdrop will guard. .-chan <#channel> Removes a channel from the eggdrops channel list. .chpass <handle> <password> Changes the specified users password on the eggdrop. .die Kills the eggdrops connection and logs who performed this command. :( .jump <server> [port] The eggdrop parts the present server and joins the server that was specified. .loadmod <modulename> Loads a module. .module <modulename> Finds the module and returns stats on the requested module. .module <botnick> Returns a list of modules running on the specified eggdrop. .rehelp The eggdrop looks for new help commands and adds them. .servers Returns a list of servers in the eggdrops config-file that it uses to join the server. .set <variable> <value> Changes the variables that were set in the config-file. .set ban-time <#channel> Set the duration in for the ban in minutes before it is deleted. .unloadmod <modulename> Unloads a module. 5. Commands for +M users (global/botnet masters) .backup Creates a backup of the userlist, to the shell. .banner <message> Sends a message across the botnet. .binds <type|all> Displays a list of binds, with usage, that are being used by the eggdrops added tcl scripts. .boot <handle|botnick> Kicks someone off the partyline. Bot owners cannot be kicked :P .+bot <botnick> <IP:bot-listening-port> Adds an eggdrop to another eggdrops record. .-bot <botnick> Removes an eggdrop from another eggdrops record. .botattr <botnick> <+|-flag(s)> [#channel] Adds bot flags to another eggdrops record. .chaddr <botnick> <IP:bot-listening-port> Changes the info that was given in the .+bot info. .chattr <handle|botname> <+|-flag(s)> [blank for global|#channel] Adds/removes flags from a users record. .clearqueue <mode|server|help|all> Deletes information in the specified queue. .comment <handle> <comment> Adds a comment for the user that only botmasters and owners can view. .dccstat Returns a list of all connected to the eggdrop you are in, with some details attached. .debug Returns a list of memory allocations. Used only to find leaks in the eggdrop. .+host <handle|botnick> <hostmask> Adds a hostmask for the specified user. .-host <handle|botnick> Removes a hostmask for the specified user. .+ignore <hostmask> [reason] Adds that hostmask to the eggdrops ignore list so that anything sent to the eggdrops is simply ignored. .-ignore <hostmask|index> Removes that hostmask from the eggdrops records. .ignores * Searches the eggdrops records for all ignored users. .link <botnick> Links two eggdrops, so they have someone to chat with :) .relay <botnick> Changes your DCC chat to the one with the specified eggdrop. .rehash Reloads the config-file if you have changed a setting. .reload Reloads the last userlist if there was no .save done and ignores the changes if any were made since the last .save. .reset <#channel> Removes all the channel modes so that you can start over from the server records. .restart Restarts the eggdrop so that changes you may have made in the config-file will take affect. Works better than a .rehash. .save Saves the added/removed information to the shell. .status Returns the status of the channel and eggdrop. .stats all Returns a lengthy description of your eggdrops status. .unlink <botnick> Unlinks the eggdrop from the one specified. .+user <handle> <hostmask> Adds a user to the eggdrop record with one hostmask and no flags. .uptime Returns the duration the eggdrop has been online. .-user <handle> Removes a user from the eggdrops records.
  8. Eggdrop Few Tricks

    Some little tricks that you may or may not know about: 1. You can "lock" a user's info line by putting a '@' as the first letter. They won't be able to change it any more. 2. '.status all' will dump out virtually everything you have configured on your bot. 3. You can automagically make a ban sticky by adding a '*' as the first character in the ban reason. 4. You can modify Eggdrop's output in partyline and messages by editing core.english.lang in the language directory. 5. You can unlink all bots and clear out the botnet info from memory by using '.unlink *'. It erases all channel assocs and everything. 6. Tcl has a command 'info body <proc>' that will list the contents of a proc and 'info args <proc>' shows what you have defined as the parameters for the proc. 7. If you don't want your logfiles to be deleted after two days and don't want the bot to create a new logfile each new day, then set 'keep-all-logs' to 0 and 'switch-logfiles-at' to 2500 in your eggdrop config file to make it keeping one logfile all the time. REMEMBER: this is not recommended on high traffic channels. 8. You can use variables in your config file, since it's really just a normal Tcl file. For example, you can set 'userfile' and 'chanfile' to "yourbot.user" and "yourbot.chan" using the following method: set myvar "yourbot" set userfile "$myvar.user" set chanfile "$myvar.chan" 9. You can export parts of your config file to separate files. For example, if you have several config files which differ from themselves only by the nickname and the used servers, you can export them to an own file and link it with the 'source' Tcl command, similar to a script. The advantage of this is that you have to edit/upload only the small file instead of the big one. This technique is also useful if you want to maintain the same channel settings, etc across your botnet. 10. You can rename a builtin command by binding over it. To rename '.status' to '.report', you'd do: unbind dcc - status *dcc:status bind dcc m report *dcc:status The first line removes the builtin binding on '.status' and the second line binds '.report' to the builtin status function.
  9. ADDUSER - creates a new user record for a user on the channel, using their current hostname (with no password and the default flags). DCC SYNTAX: adduser [!]<nickname> [handle] If the user is using a different nickname than the bot normally knows her by, you can specify their "handle" (the nickname that the bot remembers). If the bot already knows someone by that nickname, and the user on the channel doesn't have a bot record, then it does the equivalent of an 'ident' for that user - except that, again, no information is sent to the user telling them that anything was done. # Add a user using the standard hostmask <zeke> .adduser nick <bot> Added [nick] *! ident@*.host.com with no password. You can add a user with a static hostmask when using '.adduser' by prefixing their nick by '!'. # Add a user using a static hostmask, prefix their nick with a '!' <zeke> .adduser !nick <bot> Added [nick] *!ident@some.host.com with no password. Have fun.
  10. Fixed Bot not join channels added after restart

    As I guessed from the very beginning, the problem had nothing to do with the BlackTools script. After examination, it resulted that the right permissions on the directories where eggdrop should save files were not set properly.
  11. Fixed Bot not join channels added after restart

    I don't think that has something to do with BlackTools tcl script. Anyway, I will update the topic here once I get more informations.
  12. Editing the botchk file

    Editing the botchk file to automatically restart your eggdrop The botchk script and crontab are used to automatically restart the eggdrop if the shell/vps it's on reboots or if the eggdrop process is killed for some other reason. You can find the botchk file in the scripts directory (in the directory you installed the eggdrop). Newer versions of Eggdrop (from 1.3.24i) have a script included that automatically configures botchk and crontab for you. In telnet, simply switch to the scripts directory and type chmod 700 autobotchk then ./autobotchk <config> -dir /home/your_eggdrop_dir -noemail, where /home/your_eggdrop_dir is the directory you installed the eggdrop to and <config> is the name you chose for your config file. Otherwise, you can edit the botchk file and insert the required crontab entry manually. There are only four things you need to set in the botchk file, all of which are pretty self explanatory. Once you've edited the botchk file, you need to add an entry to your crontab. Here's the best method: 1) Your crontab line should look like: 0,10,20,30,40,50 * * * * /home/your_eggdrop_dir/scripts/botchk >/dev/null 2>&1 This will run the botchk script every 10 minutes, which checks that the eggdrop is running and restarts it if it isn't. You just need to change the /home/your_eggdrop_dir part to the correct path to the eggdrop on your shell/vps (type pwd to show this). Save the line in Notepad or some place where you can highlight and copy it from. 2) Type crontab -e. This should bring up the shell/vps editor (it will appear as a bunch of lines starting with the ~ character). 3) For vi, do the following - hit Ctrl-L, hit i, paste the crontab line you created earlier, hit Esc, type :wq! then hit Enter (if you make a mistake doing this, just hit Esc and start over). 4) For pico, do the following - paste the crontab line you created earlier, hit ctrl-X, hit Y when prompted to save, hit Enter when prompted for a filename. You can view your current crontab entries by typing crontab -l. To clear your crontab, use crontab -r (may be crontab -d on some shells/vps).
  13. Eggdrop Protection and Security The Eggdrop bot has many potential vulnerabilities that can be exploited if you don't secure your eggdrop properly. Below are some tips to help you make your Eggdrop more secure. Disable learn-users Allowing users to add themselves to the eggdrop may be convenient, but since it allows anyone to add themselves to the eggdrop it is not very secure (especially if the user gets partyline access when they introduce themselves). And the last thing you want is to find someone has msg flooded your eggdrop and added 1,000 new users. You should consider disabling learn-users and instead add users to the eggdrop manually using the .adduser and .+user commands. If you really want to allow users to introduce themselves to the eggdrop, you should change the command to something other than the default 'hello'. Choose owners carefully Be very careful about giving out global owner (+n) status on your eggdrop. You should consider not giving out +n status to other users at all, otherwise make sure you only give it to people you've known on IRC for quite a while and who can be trusted. Owner status allows a user to do practically anything with your eggdrop - the last thing you need is for a renegade +n to use your eggdrop for abusive purposes and get you kicked off the shell/vps. Don't use auto-op Unless your Eggdrop is on a small, private channel which does not get many visitors you do not know, using auto-op greatly increases the risk of channel takeover. This is because, in order to get ops, a person only needs to match a hostmask of a user, and idents/hostnames can often be faked on IRC. It is best to make sure that users can only get ops after giving their password to the eggdrop, typically by sending a /msg to the eggdrop to request ops. A more secure, though less convenient, way is to log into the eggdrop via DCC and use the .op command (though there is a risk here that the user could accidentally type in the wrong nick to op if they're not using their usual nick). Password security Don't choose an easily guessable password - make it a random combination of upper and lower case letters and numbers, or two words combined with a number - anything but an actual word. Also make sure when sending a msg to the eggdrop containing your password (e.g. /msg botnick op <password>) that you don't do the /msg in a channel window - I've lost count of the number of times I've seen people msg their eggdrop password to a whole channel because they accidentally left off the slash or something. Rebind or disable the ident and addhost commands It's a good idea to use msg commands other than 'ident' and 'addhost' for making the eggdrop recognise a new hostmask. Change these commands to something else. For even better security, you may wish to disable the commands without rebinding them, although this requires masters and owners to add new hosts for users manually. Use specific hostmasks If your hostname is, for example cool@modem36.ppp.yourisp.net, eggdrop will make your hostmask *!cool@*.yourisp.net. If you are a eggdrop owner or master, it's important to further restrict access by making more specific hostmasks - e.g. *!cool@*.ppp.yourisp.net or perhaps *!cool@modem*.ppp.yourisp.net. Enable protect-telnet By default, anyone can telnet to your eggdrop and attempt to guess a user's password at the login prompt. Enabling protect-telnet in the config file will allow you to restrict telnet access to particular hosts. To give a user telnet access with protect-telnet enabled, you add a special telnet hostmask to the user record, in the format -telnet!*@their.hostname.com. Example - if the user's hostmask is *!cool@*.dudes.net, you would add -telnet!*@*.dudes.net to their list of hostmasks. This allows the *.dudes.net domain to telnet to the eggdrop and attempt to login as the user. The protect-telnet feature also applies to eggdrops linking in, so on a hub eggdrop you would need to add the approriate telnet hosts for each leaf eggdrop, in the same way you would for users. Note that by default, eggdrop gives the owner the -telnet!*@* hostmask, allowing any host to telnet in. You should make sure you remove this hostmask, and add a more specific one (e.g. -telnet!*@*.ppp.yourisp.net). Also note that in versions of eggdrop prior to 1.6, telnet!*@* (without a dash) is used instead of -telnet!*@*. Allow only users to telnet to leaf eggdrops The listen command in your eggdrop's config file usually looks something like listen 54321 all, the "all" meaning connection attempts from both eggdrops and users are allowed. In most cases, leaves should not accept link attempts from other eggdrops, and changing "all" to "users", i.e. listen 54321 users, will ensure such attempts are rejected. Note that a user .relay from other eggdrops will still be accepted as it's classed as a user connection. An even more secure option is to disable the listen port completely on leaf eggdrops by commenting out the listen line with a hash (#) character and restarting the eggdrop. Having no listen port also means the eggdrop won't be vulnerable to telnet-based attacks. The downside is that the only way you'll be able to get on the eggdrop's console is by initiating a DCC session with the eggdrop on IRC. In most cases, disabling the listen port shouldn't be necessary and using protect-telnet as described above is adequate. Disable the tcl, set, and binds commands Using the .tcl and .set DCC commands, anyone with global owner status on your eggdrop can access your shell account through the eggdrop. Obviously, this is a bad thing, so you should make sure these commands are unbound in the config file. The .binds command is also used maliciously in many cases, and should be disabled if you don't use it. Use tcl scripts you really need Using Tcl (pronounced 'tickle') scripts is the easiest way to add extra features to your Eggdrop. There are hundreds of Tcl scripts out there that add all sorts of interesting capabilities. Use tcl scripts with features you really need on your eggdrop. All the nice & funny scripts you find around may be buggy and unsecure. Look for functionality instead of fun in your eggdrop. Disable the chanset command A vulnerability in eggdrop versions prior to 1.3.25 allows users to utilise the .chanset command to make the eggdrop perform virtually any function. You should either disable the .chanset command, or upgrade to 1.8.x and make sure must-be-owner is enabled. Enable must-be-owner This feature only exists in 1.3.24 and later versions. It allows only permanent owners (as set in the 'owner' setting in the config file) to use the .tcl and .set commands (assuming you have them enabled). In 1.3.25 and later, it also enhances the security of the .chanset command, and from 1.3.26 you can set must-be-owner to 2 to also allow only permanent owners to use the .dump command. Use private-user If you have a botnet with eggdrops sharing userfiles, you should consider using the private-user feature. This can significantly increase the security of your botnet, but all user changes (e.g. user additions, ident/addhost, password and flag changes, etc.) will need to be made via the hub eggdrop. Note that only 1.3.27 and later have a properly working private-user - it is not effective on earlier versions - so if you want to take advantage of private-user your hub eggdrop must be 1.3.27 or later. Use good flood protection Most people expect eggdrops to be bullet-proof, but the reality is that, by default, they're quite vulnerable to basic types of flooding. Vulnerabilities to such things as CTCP floods, avalanche floods and users with bogus usernames are fixed from 1.3 versions - but you have to use the right settings. 1.3.21 and later have the kick-bogus option which should be set to 0 to prevent kick floods on bogus usernames, while 1.3.24 and later have the kick-fun flag which should be set to 0 to eliminate vulnerabilities to avalanche floods. From 1.3.26 and later versions have the ctcp-mode setting, which you should set to 2, using an appropriate global-flood-ctcp setting such as the default 5:30. For better flood protection, you should consider using a flood protection script. In addition, a channel userlimiter is recommended to prevent hundreds of flooders joining simultaneously. Keep an eye on things While you're online, you should open a DCC chat session with your eggdrop and sit in the console. Make sure console modes m, b, s, c, o, and x are enabled (type .console +mcobxs), so you can see everything that's going on with your eggdrop. You may wish to remove the j and k console flags as these can clutter things. You may also wish to have your eggdrop's log from yesterday e-mailed to you, allowing you to review all activity that occurred on the eggdrop. To do this, you need to add a line to your crontab. To have your eggdrop mail you yesterday's log at 5:30am, you would put the line: 30 5 * * * mail your@email.address.com < /home/username/eggdropdir/eggdroplog.log.yesterday Note that the above should be pasted as one line. Also substitute the e-mail address and path to the eggdrop's log with your own. Use services, but don't give your eggdrop full access If your preferred IRC network has nickname and/or channel services and they are available to you, use them. DoS attacks and shell/vps security become less of an issue, taking a lot of the worry out of running a channel and freeing up your eggdrop to perform other useful tasks. Make sure, however, that you do not give your eggdrops any sort of "founder" status. Eggdrops should only have enough access to get ops and perform their required function. Never store a services password on your eggdrop (or in its scripts) that would allow someone to gain enough status to change ownership of the channel if they cracked the eggdrop's shell. DoS attacks Denial of Service attacks are directed at the shell the eggdrop is on. Such an attack is typically a flood of some sort that causes the shell to become extremely lagged and eventually your eggdrop may disconnect from IRC. Unfortunately, there is little you can do to protect your eggdrop from serious DoS attacks, as it is dependent on on the ability of the shell to withstand such attacks. Choosing a shell/vps account with a high bandwidth connection and good firewall systems can help prevent less serious attacks from having any significant effects on your eggdrop, but there are few shells that are totally invulnerable. DoS attacks, such as the notorious 'smurf' attack, are the main reason why many IRC channels have a large number of eggdrops on different shells/vps to help protect the channel from takeover as a result of such an attack. Shell security Because of the seemingly endless number of new security holes and exploits appearing in components of the various flavours of Linux and FreeBSD and the services that are run on them, the Unix shell box of a commercial shell provider is always at significant risk of being 'cracked'. Because of the 'public' nature of commercial shell accounts - virtually anyone with a few spare dollars or someone else's credit card number can get an account, and there may be careless users who give out their account password to malicious hackers (crackers) - there may occasionally be a few bad eggdrops on the system who will attempt to compromise the security of the shell and gain control of all the accounts. In some cases, the shell/vps may even be compromised remotely by a user without an account. If this happens, the user can then gain control of your eggdrop (and possibly all of the eggdrops on the botnet, depending on how you have them set up) and take over any channels the eggdrop is in. Unfortunately, once the shell/vps is cracked, there is little you can do to save your eggdrop and channels. Private shells are generally less vulnerable to being cracked, but unless you have friends with their own Unix shell boxes you'll have no option but to use a commercial shell provider. So, when choosing a shell provider, make sure you choose one with a reputation for good security and monitoring policies. A common misconception is that if the eggdrop that gets cracked is a leaf eggdrop, then you'll be safe since the hub overwrites the leaf eggdrop's userfile. In reality, the user will still be able to control the leaf eggdrop, and if you're using a typical sharing setup, the user can gain control of all sharebots on the botnet. Furthermore, if you have the .tcl, .set or .chanset commands enabled on these eggdrops, the user can then access all your shells through the eggdrops and make a big mess. Using private-user can help prevent a botnet from being compromised in this way.
  14. The bot does not rejoin the channels that I added when I restart it. I use the command !save before restart. I have several bots and everyone is the same. Running eggdrop v1.8.2 & BlackToolS 2.5.1.
  15. IPStatus.tcl

  16. IPStatus.tcl

    Version 1.1

    32 downloads

    IPStatus 1.1 - pings a given destination (IPv4, IPv6 or website) and replies ping time and if is up or down. ATTENTION!!! IPv6 reply works only for those who have IPv6 active on their machine!! USAGE: !iping <ip> / <host> / <website> UPDATES/CHANGES: - Supports IPv6 (only for those who have ipv6 active on their machine!!) - Multi-language support To chose a different language .set ipslang <RO> / <EN> / <IT>

    Free

  17. BlackToolS 2.5.1

    Hidden content??
  18. A New home for Tcl Scripts Archive Read the news about the changes here. The new site is located at http://www.tclarchive.org, hosts the old tcl scripts from egghelp.org and is accepting new tcl scripts submissions. Good news, considering that slennox @ egghelp.org hasn't been active for quite some time and tcl scripts submissions were closed. The egghelp.org tcl archive was one of the web's premier repositories of Tcl scripts for Eggdrop, allowing you to search or browse hundreds of scripts that enhanced your bot's functionality. At last update 7 October 2014 it reached over 1743 hosted tcl scripts by 939 authors.
  19. Bit of a late notice but we're currently in the process of updating the forum to 4.2 version and will be adding/removing plugins/apps as well as tweaking existing configurations. If you notice something missing, not working right, or just want to offer a suggestion, feel free to use: Forum Bugs, Forum Suggestions Also keep an eye on our BlackTools History page for updates as we move forward with the releases. ___ O notificare putin cam tarzie, dar in prezent ne aflam in proces de actualizare a forumului la versiunea 4.2 si urmeaza a se adauga/elimina pluginuri/aplicatii, precum si modificarea configuratiilor deja existente. Daca observati ceva care lipseste, sau poate nu functioneaza corect sau doar aveti o sugestie, nu ezitati sa folositi: Buguri Forum, Sugestii Forum De asemenea stati cu ochii pe pagina Istorie BlackTools pentru actualizari pe masura ce o sa avansam cu lansarile.
  20. Blacktools 2.5.2

    FEATURES (summary) ================================================================================== BlackTools - The Ultimate Channel Control Script One TCL. One smart Eggdrop ================================================================================== **** GENERAL CHANGES - Major coding changes for better and faster performance. -- Added a helpful information system to show, after each info request from BlackTools manual, some important TIPS about how to use this script. --- All major protections supports now addition of exceptions and customization of the ban method on each word. ----- The bot now understands some CIDR notation and dnslookup bans. ------ All protections and ban methods recognize webirc hostmask like: mibbit.com, kiwiirc.com, irccloud.com. **** IDLE - Code fixes and enhancements. -- Minor bugs fixed. **** SECUREMODE - Added multiple random code messages for a better security. **** ANTIJOINFLOOD - Recoded and combined antijoinflood with antijoinpartquit in only one protection. **** TOPWORDS - Upgraded to show more statistical informations about: smiles, actions, questions, etc. **** NOTES - Automated abuse system to report directly to the BOSS OWNER. -- Possibility for owners to decide whether they want to receive notes or not. **** SILENCE - Added a personal protection for the bot against ctcp, notice, msg & ctcr using the server silence command. **** AWAYACTION - warn-ban-kick -- Changed the output method of showing the adverts. **** BANLIST CLEANER - Implementated an automatic banlist clean system to remove a certain number of bans when the channel banlist is full. **** BANS DISTICTIONS - Added (global) to distinguish local bans from global ones. **** CONSECUTIVE LETTERS PROTECT - Added a new protection againts chars/consecutive repeated letters. **** REPORT SYSTEM - Added a flood protection settings against those who abuse the use of command. -- Added the possibility that the report to be sent in eggdrop's PRIVMSG. **** BADCHAN - Code fixes and enhancements. -- Added extra option ShowBadChan-bwait and words to be exempted. --- Minor bugs fixed. **** BADNICK - Added extra an option badnick-bmethod. -- You can now add words to be exempted. **** BADIDENT - Added possibility of being able to modify the banmask method. --- You can now add words to be exempted. **** INVITEBAN - Added exception for Undernet Official Bot *X*. **** QUOTE - Minor text fixes: spelling and grammar mistakes. -- Minor bugs fixed. **** CP SYSTEM - Some major bugs fixed. **** SEEN - Minor bugs fixed. **** XTOOLS - Minor bugs fixed. **** LINK SYSTEM - Minor bugs fixed. **** BADREALNAME - Minor bugs fixed. **** ADD/ADDUSER/USERLIST - Minor bugs fixed. -- Removed the adduser command and included all it's functions to the add command. **** COUNT - Reintroduced count module, but only as informative thing and how to use it. **** ANTISPAM - Added exception from on-join message for all users with access. **** ANTISPAM - Minor bugs fixed. **** STATS - Reintroduced the statistics for ban commands used by each user with access. ------------------------------------------------------------------------------------------------------------------------------------------------- BlackTools - The Ultimate Channel Control Script. Copyright (c) 2008-2018 Daniel Voipan (aka BLaCkShaDoW). ------------------------------------------------------------------------------------------------------------------------------------------------- DOWNLOADS The following downloads are currently available: BlackTools 2.5.2 SUPPORT Are you having problems with installing or running BlackToolS tcl script? In case you have not found a solution in the FAQ file which is contained in the BlackTools2.5.2.tar.gz you can try the following support methods: Wiki: - Our wiki provides information about setting up BlackTools and frequently asked questions. IRC: #TCL-HELP @ irc.undernet.org - There's usually someone available at our IRC channel who can help you with your questions. BUGs TRACKER We offer a lot of support for BlackTools script - however you can also support us: Donations will help us to keep working on this project.
  21. UrlTitle tcl

    Thanks very very match
  22. BlackToolS 2.5.1

    Versiunea v2.5.1 scriptului BlackToolS o puteti descarca de mai jos. Pentru mai multe info consultati manualul tcl-ului (vedeti comanda .man). We offer a lot of support for BlackTools scripts, however you can also support us: Donations will help me to keep working on this project.
  23. BlackTools2.5.1.tar.gz

    Buna treaba baieti! Ultima versiune e ce trebuie
  24. Version 2.5.1

    144 downloads

    ============================================================================================ -= BLaCkShaDoW Production Presents =- BlackTools - The Ultimate Channel Control Script One TCL. One smart Eggdrop ============================================================================================ BlackTools is the most complete channel management script who can manage channels from all the IRC networks, although some modules are specifically designed only for Undernet network. ----------------------- Minimum requirements: o Eggdrop 1.6.x o Tcl 8.4 or higher. Most important features: 2.5.1 Most important changes (summary) **** SMALL FIXES -- Fixed some differences of eggdrop bantimes. -- All options/settings are now case sensitive. **** ANUNT --- Changed the output method of showing the adverts. **** BACKCHAN -- Minor text fixes: spelling and grammar mistakes and some differences of bantimes. --- Removed nextback-chan option. **** BADCHAN -- Added extra option 'ShowBadChan' - who sends a message to all users with OP (@/&) about the banned user and the forbidden channels on which that was found. **** BADIDENT -- Added possibility of being able to modify the banmask method. **** IDLE -- Added anti-idle option for halfop users. **** INVITEBAN -- Added exception for Undernet Official Bot *X*. **** LIMIT -- Fixed some error regarding the way on how the eggdrop sets the channel limit. **** OMSG -- This is a new command that will allow you to send specified messages to all users with OP (@/&) from a channel.. **** QUOTE -- Minor text fixes: spelling and grammar mistakes. --- Changed the output method of showing the quotes. **** TROLL -- Minor text fixes: spelling and grammar mistakes. --- Added extra option 'ShowTroll' - once activated, makes the eggdrop to display a notice message list of current trolls of the day, when users with access joins the channel (the list is reset everyday at midnight). **** VOICEME -- Added extra option 'NoLogged' - once activated, will allow the command /msg botnick voiceme <#chan> to be used and by users without a CService Username. **** MUCH MORE -- possibility for every user to set his own cmdar ( ! ) as they wish. ---- repaired a few bugs... ----- And lots of cool features for your eggdrop * Read BlackTools MANUAL for more info about how to use it. ** Read INSTALL file to know how to install it. *** Read FAQ file for the most frequently asked questions. We offer a lot of support for BlackTools - however you can also support us: Donations will help us to keep working on this project.

    Free

  25. Blacktools 2.5.1

    FEATURES (summary) ================================================================================== BlackTools - The Ultimate Channel Control Script One TCL. One smart Eggdrop ================================================================================== **** SMALL FIXES -- Fixed some differences of eggdrop bantimes. -- All options/settings are now case sensitive. **** ANUNT --- Changed the output method of showing the adverts. **** BACKCHAN -- Minor text fixes: spelling and grammar mistakes and some differences of bantimes. --- Removed nextback-chan option. **** BADCHAN -- Added extra option 'ShowBadChan' - who sends a message to all users with OP (@/&) about the banned user and the forbidden channels on which that was found. **** BADIDENT -- Added possibility of being able to modify the banmask method. **** IDLE -- Added anti-idle option for halfop users. **** INVITEBAN -- Added exception for Undernet Official Bot *X*. **** LIMIT -- Fixed some error regarding the way on how the eggdrop sets the channel limit. **** OMSG -- This is a new command that will allow you to send specified messages to all users with OP (@/&) from a channel.. **** QUOTE -- Minor text fixes: spelling and grammar mistakes. --- Changed the output method of showing the quotes. **** TROLL -- Minor text fixes: spelling and grammar mistakes. --- Added extra option 'ShowTroll' - once activated, makes the eggdrop to display a notice message list of current trolls of the day, when users with access joins the channel (the list is reset everyday at midnight). **** VOICEME -- Added extra option 'NoLogged' - once activated, will allow the command /msg botnick voiceme <#chan> to be used and by users without a CService Username. **** MUCH MORE -- possibility for every user to set his own cmdar ( ! ) as they wish. ---- repaired a few bugs... ------------------------------------------------------------------------------------------------------------------------------------------------- BlackTools - The Ultimate Channel Control Script. Copyright (c) 2008-2017 Daniel Voipan (aka BLaCkShaDoW). ------------------------------------------------------------------------------------------------------------------------------------------------- DOWNLOADS The following downloads are currently available: BlackTools 2.5.1 SUPPORT Are you having problems with installing or running BlackToolS tcl script? In case you have not found a solution in the FAQ file which is contained in the BlackTools2.5.1.tar.gz you can try the following support methods: Wiki: - Our wiki provides information about setting up BlackTools and frequently asked questions. IRC: #TCL-HELP @ irc.undernet.org - There's usually someone available at our IRC channel who can help you with your questions. BUGs TRACKER We offer a lot of support for BlackTools script - however you can also support us: Donations will help us to keep working on this project.
  26. Salut BlackShadow, ti am dat pe canalu de pe under statslave.tcl pentru rang pe main, ai rezolvat ceva cu el sau ai uitat?  si respect pentru tot ce faci :)

    statslev.tcl

    1. BLaCkShaDoW

      BLaCkShaDoW

      din pacate am uitat, am fost ocupat cu 2.5. Mai multe detalii ar fi de ajutor in legatura cu ceea ce face scriptul si ceea ce vrei sa faca. Multumesc.

    2. MANNY

      MANNY

      salut, am vazut acest tcl pe un chat, unde lumea da !rang pe #romania si spune ce rang are la cat de mult a tastat pe canal  ( exemplu: nick are rangu de  Vorbarila ) asta inseamna la cat a tastat pe #romania, arata si in tcl . iti mulrumesc

  1. Load more activity