Session Start: Fri Dec 28 19:36:07 2007
Session Ident: #class
[19:36] * Joins #class: Loki^ (loki_cat@lokicat.users.undernet.org)
[19:36] * Topic is 'Undernet User Committee presents: Advanced Users Class (english language). Happy New Year!'
[19:36] * Set by Season`d on Fri Dec 28 19:04:23
[19:36] <+Class> Good Evening. This educational script is brought to you by the Undernet User Committee. Please send your comments, suggestions or ideas to class@undernet.org. Our Webpage is http://www.user-com.undernet.org/class/ - We'd like to welcome you all to the Undernet Advanced User's School. [INT1]
[19:36] <+Class> This class covers the more advanced topics of IRC. It is recommended that you first attend the Undernet Beginner IRC Class before attending this class. The Beginner IRC Class will be held on a rotational basis every three weeks at 7:30PM EDT (Friday 23:30 GMT) and Sundays at 12:30PM EDT (Sun 16:30PM GMT), (http://tycho.usno.navy.mil/zones.html for your time zone) in #class. [INT2]
[19:36] <+Class> If after the class you find you need additional help with IRC, feel free to ask in one of the help channels we mention at the end of class. [INT3]
[19:37] <+Class> Now for the rules of the class. These are for your benefit to prevent disruption. [R1]
[19:37] <+Class> The teaching staff is divided up alphabetically. Each tutor will answer questions for the nickname group they are assigned to: for example, A-G_Tutor handles nicks starting with A through to G, and so on. If your nickname starts with anything else, don't sweat it. Just use the tutor with -A- included in their nickname group. [R2]
[19:37] <+Class> Please ask any questions you have about IRC or this class to your tutor. To do this, type /msg <tutor> <question>. Please do NOT /notice me, your tutor, or the channel. [R3]
[19:38] <+Class> Channel is set +Dm to prevent join/part flood on your screen and people disrupting the class. People joining the channel while this mode is set won't show up in the channel's nicklist. [R4]
[19:38] <+Class> If you leave or disconnect, you can type /join #class to get back in the channel. Please do not ask for invites, it is not necessary. Make a note of your tutor's nickname now. [R5]
[19:38] <+Class> I'd ask that you please do NOT message me. I have the job of keeping the lesson flowing. Pose all questions to your tutor. [R6]
[19:38] <+Class> If you plan to stay for the class, you may wish to log the session - please turn on your logging now (type: /log on ). If you need help with this, please /msg your tutor. [R7]
[19:39] <+Class> The numbers and letters you see at the end of these lines are reference marks. They help me and the tutors to find where we are during the class. You do not need to pay attention to these. [R8]
[19:40] <+Class> Section A - FLOOD PROTECTION: This section explains the different types of floods and how to try to prevent them. [A1]
[19:40] * Joins #class: Saralee (sara@Saralee.users.undernet.org)
[19:40] * X sets mode: +o Saralee
[19:40] <+Class> Floods can happen everywhere you go on IRC. There are simple ways to protect you against them because they can disconnect and annoy you. [A2]
[19:40] <+Class> There are many different kind of floods on IRC. Here are some of the more common types. We'll help you to learn how to prevent and protect yourself from their destructive actions. [A3]
[19:40] <+Class> CHANNEL TEXT FLOODS - Multiple lines of text sent to a channel - usually in random letters. [A4]
[19:41] <+Class> CTCP FLOODS - The flooder sends a CTCP command to you many times, causing your client to respond just as many times, and ending up in a disconnection. [A5]
[19:41] <+Class> DCC FLOODS - A user attempts to hold multiple DCC sessions with you and sends random text to the chat window. [A6]
[19:41] <+Class> The best thing to do in order to combat this type of flood is not to accept any DCC chats from people you don't know and trust. Otherwise, if the DCC is a DCC send, the best thing to do is to close your client, open it again, and set it to auto-ignore DCC Sends until you're sure the flooder stopped. (In mIRC, the command for this is: /sreq ignore.) [A7]
[19:41] <+Class> To combat CTCP and channel text floods, set up an alias key to /silence +*!*@*, which will ignore everyone until you take off the command. To take off the command, type /silence -*!*@* (note the -). For information on setting up aliases, consult your client's documentation. [A8]
[19:42] <+Class> Latest versions of clients like mIRC bring a slight flood protection which you can configure to block most of the channel and CTCP floods. In mIRC press ALT+O, expand IRC section and go to Flood or just type /flood on. Refer to your client's help file for further info about the options for this. [A9]
[19:42] <+Class> FLASH FLOODS - Occurs mainly when someone sends specific control characters to another user who is IRCing via a UNIX machine. The results of the flood cause a slight reset of the client's terminal and renders text unreadable. Mostly this is only seen on school networks using ancient ircii clients. [A10]
[19:42] <+Class> For all UNIX users, simply type - mesg n - (no dashes) at the shell prompt BEFORE using IRC. This command will get rid of the problem. [A11]
[19:42] <+Class> ICMP FLOODS - An ICMP flood occurs when ICMP pings overload a system with so many echo requests that the system spends all its resources responding until it can no longer process valid network traffic. This ends up in a disconnection. [A12]
[19:43] <+Class> While there is no major - full proof - way to suppress ICMP floods, the best defense is to use a good firewall. [A13]
[19:43] <+Class> These are known as firewalls and are usually used at most ISPs. If your ISP doesn't have one, download & install one, like ZoneAlarm, Outpost firewall Pro, Norton Personal firewall, Sygate, BlackIce Defender, or Shields Up! (We will give you the web pages where you can get these and other firewalls later in this class). [A14]
[19:43] <+Class> The latest Windows versions like ME, XP, VISTA, etc. already come with patches that may help you avoid these attacks. Anyway, a good habit should be to keep your Windows as up-to-date as possible. This means to get the latest security patches for your Windows or any operating system you may be using. For Windows updates, visit http://windowsupdate.microsoft.com . [A15]
[19:43] <+Class> LOCAL PORT FLOODS - Unpatched Windows versions have a bug that lets flooders attack your printer and modem ports. So be sure to keep your Windows up-to-date. Also, the latest versions of mIRC have already fixed these bugs in them to avoid these attacks, so keep your mIRC version current as well. It's highly recommended to get the latest patches for your Windows and to use the latest versions of your IRC Client. [A16]
[19:44] <+Class> There is a simple fix for oldest mIRC versions' users. Just type /ignore -p < option >. Where option is, type these commands in separately: com1*!*@*, com2*!*@*, com3*!*@*, com4*!*@*, prn!*@*, and lpt!*@*. Be sure to type them SEPARATELY. E.g. /ignore -ptn com1*!*@*, then /ignore -ptn com2*!*@*, and so on for all of them. [A17]
[19:44] <+Class> FORMAT FLOODS - Format floods are pictures drawn on a client using formatted text and colors. As cute as it sounds, they can flood users off - both accidentally and intentionally. Most IRC clients have options that let you strip these enhanced text formats and avoid being flooded. Refer to your client help file for info about this. [A18]
[19:44] <+Class> Those are all the types, fixes and commands you need to prevent and keep yourself safe from floods. Remember to NEVER retaliate against a flooder, it only makes the situation worse. If a flooder persists to flood you, try contacting an IRCop by typing /who 0 o . [A19]
[19:44] <+Class> For a more in-depth document about flooding and how to combat it, check NudeDude's NoFlood document available at the documents website at http://www.user-com.undernet.org/documents/ . [A20]
[19:45] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. You'll have a chance to ask your tutor questions at the end of each section. [AP]
[19:45] <@I-Q_Tutor> A-H_Tutor got coal for Christmas
[19:45] <@I-Q_Tutor> R-Z_Tutor saw 12 reindeer, you can draw your own conclusions.
[19:45] <+Class> Section B - DoS attacks - Explanation and information on protection against Denial of Service attacks. [B1]
[19:46] <+Class> A Denial of Service is an attack against computers connected over the Internet, especially on IRC. These attacks are illegal in the U.S and many other countries. [B2]
[19:46] <+Class> There are many types of DoS attacks, the most common being nukes, packeting and hacking. [B3]
[19:46] <+Class> A nuke is usually performed by sending specially crafted packet(s) of data to a computer running an unpatched operating system. If, for example, you don't update Windows regularly, you may be vulnerable to a nuke-based attack. Nukes usually use an internal operating system exploit to cause the computer to lock-up (i.e. Blue Screen of Death), forcing you to reboot. [B4]
[19:46] <+Class> There are many types of nukes - SMB bombs, Winnuke, land, Click, Sspin (ping of death) to name just a few, though most of them only affect unpatched versions of Windows 95/NT. There are also many nukes that exploit bugs found in older Linux versions too. [B5]
[19:47] <@A-H_Tutor> I-Q_Tutor: ate up Santa's cookies
[19:47] <+Class> SMB (Server Message Block) is not an attack in itself, but a weakness in the Windows file sharing logic that allows remote attackers to view your files and folders. There are several patches for users, another solution would be to uncheck the Netbios and IPX protocols in your modem connection settings, only leaving tcp/ip in place. [B6]
[19:47] <+Class> Packeting is an entirely different kind of DoS (often Distributed Denial of Service, or DDoS) attack. The objective is no longer to cause the computer to lock-up, but instead prevent any normal data from being sent or received over the Internet by the victim. This is done by flooding the victim with an extraordinary amount of meaningless data, cluttering up any available bandwidth. [B7]
[19:47] <+Class> There are many different kinds of packeting attacks, including smurf, slice, UDP floods and ICMP floods. [B8]
[19:47] <+Class> ICMP is Internet Control Message Protocol, and is very common. Not all ICMP are attacks. If you are attacked with ICMP it affects your modem connection and causes all Internet applications to run very slowly and eventually disconnect from your ISP. Firewalls can help reduce the effectiveness of this type of attack. [B9]
[19:48] <+Class> If an ordinary dial-up user is targeted for a DDoS attack, it will usually lead to being disconnected, however, the dial-up user will likely be able to reconnect and obtain a new IP. [B10]
[19:48] <+Class> On the other hand, if an IRC server, a web server or even an ISP is attacked, there is very little they can do to defend themselves. Packeting has been responsible for the delinking of many IRC servers from Undernet, and has forced many online companies out of business. [B11]
[19:48] <+Class> How can you help this war against cyber-terrorists sending malicious useless and endless packets? Find out in Section F, when we cover Trojans. [B12]
[19:48] <+Class> Hacking is another form of Denial of Service attack. It's important to dispel myths about hacking, since there are many. Hacking can only occur if your system allows it. If you do not run software that has a backdoor or a vulnerability/exploit (such as a virus or a trojan), then you cannot be hacked. [B13]
[19:49] <+Class> DoS attacks are very serious. In some cases, a fix is available, and it is strongly recommended that you get the patch. At the end of this class, URLs will be given for the patches. As with floods, the last thing to do is retaliate. Remember, when you're getting attacked, the first thing you want to know is the IP address so you can report the abuser to the authorities. [B14]
[19:49] <+Class> There are currently many viruses going around IRC. A user with an infected copy of mIRC unknowingly distributes the virus to all users entering a channel in one way or another, sometimes by sending a file, but usually by spamming a website. Please note that at this moment, there are no Linux, UNIX and Mac viruses on IRC. [B15]
[19:49] <+Class> People who accept the DCC-send and then run the infected file have their good files replaced with the infected one, causing many things to go wrong. People who visit the spammed website and don't have a patched Web Browser then become automatically infected through ActiveX/JavaScript exploits (without any notification). [B16]
[19:49] <+Class> Many kinds of IRC viruses exist, many cause everything you type to be echoed into a secret channel created by the abusers, other kinds of viruses will install an infected robot (or drone) that will connect to a predefined IRC server and join a predefined channel, giving abusers full access to your computer, and your bandwidth. They can use this bandwidth to launch DoS attacks on users and other IRC servers (i.e. packeting). [B17]
[19:50] <+Class> The most important thing to remember is to NEVER accept a DCC from someone you don't know and trust, especially if they're trying to send .ini, .vbs, .scr, .dll, .pif, .bat, .exe, .shs, .com, or anything with a double extension, like .jpg.bat, etc. If you do not see file extensions in your Windows client, you may want to set it to show them before ever accepting any file through DCC. And do NOT go to unsolicited web sites. [B18]
[19:50] <+Class> If you are a Windows user, visit http://windowsupdate.microsoft.com/ regularly to secure your system against known vulnerabilities and nukes. By downloading critical patches, you stop over 80% of IRC viruses from having any effect on your computer. For more information on nukes, take a look at http://www.irchelp.org/irchelp/nuke . [B19]
[19:50] <+Class> If you'd like to take the extra step and install a software firewall, make sure you shortlist Norton's Personal Firewall, ZoneAlarm, Outpost firewall Pro, Tiny Personal Firewall, BlackIce Defender, McAfee Personal Firewall, Sygate Personal Firewall etc. URLs for these products will be given at the end of this class. [B20]
[19:51] <+Class> Keep in mind that on Undernet, since the release of the new +x usermode, you can hide your IP address from regular users, so they cannot launch any sort of direct DoS attack on you. They may still flood you via IRC, which leads to disconnection and possibly even channel takeovers (covered in the next sections). [B21]
[19:51] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [BP]
[19:51] <@I-Q_Tutor> Saralee is hosting a New Year's Eve party, clothing is optional. FrenchTutor already has 179 tickets to it.
[19:51] * @R-Z_Tutor wants one
[19:52] <+Class> Section C - ABUSE AND TAKEOVERS: How to prevent and report abuse and channel takeovers. [C1]
[19:52] <+Class> Even if you install all of the patches and take all of the precautions shown in sections A and B, you can still be a victim of a flood or a DoS attack. Knowing where to report them is the next step. [C2]
[19:52] <@FrenchTutor> :d
[19:52] <+Class> The most important thing you can have is a log. Try to have the logs timestamped, so we know the exact time. Also, try to cut out all irrelevant lines in the log. Beside the log, it is requested that you have the attacker's nickname and username and user@host, if possible. [C3]
[19:52] <+Class> Takeovers happen just as much as abuse. Takeovers are when a person comes into a channel and tries to gain ops. Often the abuser will deop and kick/ban the other ops as soon as he gets opped. [C4]
[19:53] <+Class> Takeovers can occur when multiple floodbots are set up to flood everyone in the channel, and backdoored clients can expose X passwords and they can be used to gain ops. [C5]
[19:53] <+Class> If your channel has been taken over, you can go to #nastrand or #zt. Calmly report the incident to the helpers there. [C6]
[19:53] <@A-H_Tutor> i'll bring cookies
[19:53] <+Class> Many users start a channel one day, and come back the next day to see that other people are opped in it. This is certainly not considered abuse because the channel is not registered, and does not belong to any one person. [C7]
[19:53] <+Class> Users gaining ops by changing their user@hosts and pretending to be an op is NOT considered a takeover, but bad channel management. Many IRCops will not aid channels when this occurs. [C8]
[19:54] <+Class> We'll pause briefly in case you have any questions you would like to ask your tutor. [CP]
[19:54] <@I-Q_Tutor> I-Q_Tutor doesn't like black-eyed peas
[19:54] <+Class> Section D - SCRIPTS AND BOTS - Explanation of scripts and online robots. [D1]
[19:55] <+Class> Bots are clients with automated responses to certain commands. These responses can be coded into the client and run on IRC to serve some sort of purpose. [D2]
[19:55] <@A-H_Tutor> nor collards I-Q_Tutor ?
[19:55] <+Class> There are many different kinds of bots - Bar bots, fileserving (f-serve) bots, trivia bots, even casino bots. Each bot is coded to have a specific purpose on IRC. Note - for channel management, maintenance of an oplist and banlist, and to utilize other features that bots can offer, it's best to use CService's X. For more info, join #CService. [D3]
[19:55] <+Class> Warbots are bots that are programmed to take over channels by use of flooding and trying to create a netsplit. Warbots are illegal on Undernet and will get your host/address g-lined, if not k-lined, so it's best NOT to run this type of bots. [D4]
[19:55] <+Class> Unlike scripts, bots are run on a separate client then the one you're using. For example, you would have a second copy of mIRC on your computer. [D5]
[19:56] <+Class> A bot works by using a script, comprised of many 'on' commands. For example, - on *:JOIN:#:whois - would tell you who a person is when they join a channel. [D6]
[19:56] <+Class> An alternative way of running a bot is to obtain an already programmed bot. All you need to do is download the scripts and load it into your client. These bots can be obtained from many popular web sites, but be careful. Make sure you understand the commands it uses before loading them. Often these bots are not friendly and will take over your channel. [D7]
[19:56] <+Class> More advanced scripters usually use Perl, C, Tcl, etc as scripting languages for the clients that support them. To learn how to script in your own client, ask in a scripting/bot channel, look on a bot website, or consult your client's documentation. [D8]
[19:56] <+Class> A good resource for bots is the Undernet Documents Committee's BotDoc. This document has an FAQ and has many resources for creating your own bot, or getting one off of the web. It can be found at the Documents website located at http://www.user-com.undernet.org/documents . [D9]
[19:57] <+Class> Scripts are groups of commands that enhance or automate some features or tasks in your IRC client. [D10]
[19:57] <+Class> Scripts are sometimes used to run bots. With bots, scripts are the files that actually have the 'on' commands. Scripts tell the client what to do when certain cases come about. [D11]
[19:57] <+Class> Some other times, scripts are used for fun. Fun scripts include automatic greetings when a client joins a channel, different responses to different actions, or running f-serves or other services. [D12]
[19:57] <+Class> For example, you can go to your Remotes in mIRC and type an on-join line so that your client automatically sends a greeting to every other client joining the channel(s) you're on. [D13]
[19:58] <+Class> For more information on creating scripts or bots specifically designed for your client, refer to your client's help files, or join a channel specifically for your client eg. #mIRC, #eggdrop, #darkbot, or #emech. [D14]
[19:58] <+Class> Some useful websites for bots are http://www.energymech.net , http://darkbot.sourceforge.net , http://www.eggheads.org or http://www.egghelp.org/ , and the Undernet BotDoc mentioned above. [D15]
[19:58] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [DP]
[19:59] <@I-Q_Tutor> R-Z_Tutor threw a snowball at Santa
[19:59] <+Class> Section E - ADVANCED COMMANDS: A listing of commands to know. [E1]
[19:59] <+Class> LUSERS - Options: none. Syntax: /lusers. Use this command to get network information and status. [E2]
[20:00] <+Class> WALLCHOPS - Options: none. Syntax: /wallchops < #channel > < message >. If you are an op and would like to send a private message ONLY to the other ops on the channel, use this command. [E3]
[20:00] <+Class> WHOWAS - Options: none. Syntax: /whowas < nickname >. Use this command to see if someone was on IRC recently. Useful if you're being flooded and don't know the address of the attacker. Note: this command works for a very short time (usually a few seconds) after the client has left. [E4]
[20:00] <+Class> CTCP - Options: Clientinfo, ping, time, userinfo and version. Syntax: /ctcp < nick > < option >. CTCP (Client To Client Protocol) is used in many different ways, to check lag, to see a persons client version, etc. To see all available ctcp commands use the clientinfo option. [E5]
[20:00] <+Class> USERHOST - Options: none. Syntax: /userhost < nickname >. Finds the user@host for the specified nickname. [E6]
[20:01] <+Class> USERIP - Options: none. Syntax: /userip < nickname >. Similar to Userhost, but this command finds the IP address for the specified nickname. [E7]
[20:01] <+Class> SILENCE - Syntax: /silence +|- nickname or user@host. This command works like ignore, except that it works at the server level, not at the client level. [E8]
[20:01] <+Class> USERMODES - Options: i, w, d, x. Syntax: /mode < your nickname > < + or - (option) >. Use this command to set modes on yourself. Option i makes you invisible, w makes you receive wallops, d makes you deaf to all channel conversation and x hides your real IP/host and shows instead userid@username.users.undernet.org. Example: /mode < nick > +i. Note: you can use either + or - before the option to choose setting. [E9]
[20:01] <+Class> DNS - Options: none. Syntax: /dns < nickname > or < address >. The DNS command is used to find someone's resolved address, or unresolved DNS number. It's useful for finding people with unresolved hostnames. This is a client command, so check if your client supports this command. [E10]
[20:02] <+Class> When typing these commands, omit the parentheses. For more advanced commands, consult your client's help files. Because each client is different, giving more advanced commands would be confusing. [E11]
[20:02] <+Class> For more help with any IRC command, try reading the IRC Command Cosmos Tutorial at http://www.irchelp.org/irchelp/misc/ccosmos.html . [E12]
[20:02] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [EP]
[20:02] <@I-Q_Tutor> Saralee makes Frito pie with Dorritos
[20:03] <@Saralee> haha, stop giving away my secrets!
[20:03] <+Class> Section F - TROJANS: An explanation of Trojans and their fixes. [F1]
[20:03] <+Class> IRC is heaven for hackers and virus writers because it is unmoderated and fairly anonymous. Consequently, there have been outbreaks of Trojans being sent to unsuspecting users quite regularly. [F2]
[20:04] <+Class> These Trojans are passed around in disguise as games, enhancements to IRC clients, in warez and pornographic files with any extensions such as .exe, .jpg, .bat, .pif, .ini, .html, .shs, .com and so on. [F3]
[20:04] <+Class> Additionally, viruses can be spread via IRC by exploiting an ActiveX/JavaScript vulnerability in unpatched versions of Internet Explorer. The hacker creates a website, then spams (advertises) it to users who visit the site, and the visitor automatically becomes infected and continues to spread the virus. Never click on a spammed website, especially the ones promising pornography, even if you think you have all the Windows updates. [F3a]
[20:04] <+Class> The result of accepting a file sent from anyone or visiting a spammed website could be the compromise of your computer to the writer/owner of the Trojans. [F4]
[20:04] <+Class> What does this compromise mean? Well, it ranges from allowing access to your computer when you are online to permitting the Trojan writer/owner to get your IP, e-mail address(es), passwords and any personal information that might be on your machine. [F5]
[20:04] <+Class> This allows the Trojan writer/owner to use YOUR machine for Denial Of Service attacks, which for example in the United States of America is a felony. [F6]
[20:05] <+Class> The only way this risk can be minimized is by YOU, the user, by NOT accepting ANY file from anyone, for any reason, keeping your operating system updated (if you're running Windows, get your updates via http://windowsupdate.microsoft.com/ ) and running an up-to-date antivirus software. [F7]
[20:05] <+Class> YOU are protecting yourself when you decline a file sent from someone, should they ask why, tell them why!!!! You shouldn't be ashamed to tell someone that you don't accept file sends. You can also set file types to ignore in your mIRC DCC options. [F8]
[20:05] <+Class> The best way to prevent getting infected with a virus or a Trojan is to never accept files from people you do not know and trust. Also be sure that Auto Accept is OFF for DCC, you can do this by typing /sreq ask. After typing this, you should see this line: *** DCC Send requests pop up a dialog ***, that means that anyone who tries to send you files needs your permission to do so. [F8a]
[20:06] <+Class> Regular use of an anti-virus program is the best solution, there are just too many exploits/Trojans/viruses for any one person or channel to be good at helping with all of them. Professional anti-virus software is your best prevention. [F9]
[20:06] <+Class> When researching for antivirus software, make sure your shortlist these products: PC-cillin, Kaspersky (formerly AVP), Norman Virus Control, Norton Antivirus, AVG, among others. Check the URLs for these products and others at the end of this class. [F10]
[20:06] <+Class> Users may also try to say they are sending you a 'fix' for these Trojans, they may also be the Trojans themselves, so do not accept these either unless they are an operator in a reputable virus removal channel, such as #vh, #dmsetup or #nohack. [F11]
[20:06] <+Class> To download a cleaner that will check for and clean Trojans go http://www.moosoft.com/ and download the latest version of The Cleaner. Make sure you visit http://hackfix.org/software/configure/cleaner.html for proper configuration and running instructions. [F12]
[20:06] <+Class> It is recommended that you visit #vh, #nohack, or #dmsetup first to get the proper information. [F13]
[20:07] <+Class> If you do come across a user who is spamming a website, don't assume he/she is a hacker. Chances are, he/she has fallen victim of the virus and doesn't know what to do. Try to contact the operators of the channel the user is in and get them to guide him/her to one of the above mentioned virus removal channels. [F14]
[20:07] <+Class> CAUTION: mIRC versions between 6.0 and 6.12 have an exploit which could get it to "crash" if someone intends to. [F15]
[20:07] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [FP]
[20:08] <@I-Q_Tutor> A-H_Tutor submitted her cookies to Betty Crocker, she won the Crock.
[20:08] <+Class> Section G - UNDERNET ADMINISTRATION: How the Undernet network functions. [G1]
[20:08] <@Saralee> ;p
[20:08] <+Class> Undernet may seem very simple to the common user, but behind the scenes there are many people working hard for the users. Many people devote their time to perform many necessary tasks for maintaining the Undernet. [G2]
[20:08] <@A-H_Tutor> hahaha
[20:09] <+Class> Undernet is comprised of many different committees and subcommittees. Each committee tries to work with one another to create a better network and to maintain network stability. [G3]
[20:09] <+Class> There are a total of five committees and seven subcommittees. [G4]
[20:09] <+Class> 1.- Channel Service Committee (CService) - Provides an easy method to register usernames and channels in order to have op access, maintain channel stability, to prevent takeovers and to manage banlists and userlists. CService has 3 groups - registrations, abuse, and help channel. [G5]
[20:09] <+Class> The CService home page is located at http://cservice.undernet.org . CService's main e-mail address is cservice@undernet.org . [G5a]
[20:10] <+Class> 2.- Coder Committee - Concentrates on the continued development of the IRC protocol with the goal of making Undernet a more efficient chat network. [G6]
[20:10] <+Class> The Coder Committee home page is at http://coder-com.undernet.org/ . Their e-mail address is coder-com@undernet.org. [G6a]
[20:10] <+Class> 3.- Undernet User Committee (User-Com) - Provides Undernet users a place to give their thoughts. This committee has seven subcommittees - UserGuide, Webmasters, Documents, Promotions, Newsletter, Class and Translators. [G7]
[20:10] <+Class> The User-Com home page is located at http://www.user-com.undernet.org . The committee's main e-mail address is user-com@undernet.org. [G7a]
[20:11] <+Class> 4.- Routing Committee - Views current IRC Servers and evaluates new applications for servers. The goal of the committee is to link only the most qualified servers. [G8]
[20:11] <+Class> Routing Committee's home page is located at http://www.routing-com.undernet.org . Their e-mail address is routing-com@undernet.org. [G9]
[20:11] <+Class> Undernet also consists of volunteers known as IRCops. These people, picked by server administrators, have the job of maintaining the network. To find an IRCop for assistance, type /who 0 o or /quote who 0 o for UNIX clients. Remember they are busy people so don't get mad if they don't respond at first. [G10]
[20:11] <+Class> The Undernet FTP site, ftp.undernet.org , is a great place to find more information about Undernet. Included in this site are IRC documents, servers, scripts, clients for different operating systems, pictures, mailing list archives and miscellaneous utilities. [G11]
[20:12] <+Class> We'll now pause briefly in case you have any questions that you need to ask your tutor. [GP]
[20:12] <@I-Q_Tutor> R-Z_Tutor runs a committee of one, and still the votes are generally tied.
[20:12] <+Class> Section H - UNDERNET DOCUMENTATION: How to retrieve important and useful documents. [H1]
[20:13] <+Class> As an Undernet user, you have access to a number of documents helping you have an excellent experience online. There are two main sources of documents, UserGuide on IRC, and the Documents Project. [H2]
[20:13] <+Class> When you are in your web browser, you can go to the Documents Project Web page. This page is very useful in finding what you need, whether it be the Undernet FAQ, or the History of the Undernet. [H3]
[20:13] <+Class> The Undernet Documents Project can be e-mailed also. E-Mail them if you have any ideas for documents or if you have any comments or suggestions for them. Their address is documents@undernet.org. [H4]
[20:13] <+Class> Their web page is located at http://www.undernet.org/user-com/documents/ . At this address, you can find various documents including beginner, advanced, technical, and historical documents. [H5]
[20:14] <+Class> You're strongly encouraged to visit all the User-Com pages since they contain very helpful and interesting information at your disposal. The Usercom webpage is at http://www.undernet.org/user-com . [H6]
[20:14] <+Class> If you don't want to go to the WWW, there is a bot online on the Undernet, called UserGuide. [H7]
[20:14] <+Class> UserGuide has many uses. It holds many help topics for you. [H8]
[20:14] <+Class> To use Userguide, type /msg UserGuide genhelp . This will give you a list of help topics to read. [H9]
[20:15] <+Class> Just a gentle reminder: because the Undernet is run strictly by volunteers working in their spare time, please read all of the appropriate documentation before asking for help from any of the committees. [H10]
[20:15] <+Class> We'll pause briefly in case you have any questions that you need to ask your tutor. [HP]
[20:15] <@I-Q_Tutor> Saralee listens to vinyl LPs, FrenchTutor has never seen one, A-H_Tutor serves brownies on them.
[20:16] <+Class> Section I - OTHER REFERENCES: There are many help channels on Undernet. There are also many knowledgeable people to help you out with any problems you may have. Here are some places on Undernet where you can go for help: [I1]
[20:16] <+Class> #UserGuide - Undernet User-Com's help channel, for all general help. [I2]
[20:16] <+Class> #user-com - Undernet User Committee's home channel, always staffed with helpful people. [I3]
[20:16] <+Class> #vh - One of Undernet's most reputable virus removal channels. [I4]
[20:17] <+Class> #zt - Help for Channels & Guests from IRC Operators & Selectively Trained volunteers. [I5]
[20:17] <+Class> #nastrand - Channel-takeover and network abuse assistance channel. [I6]
[20:17] <+Class> #report-abuse - Assistance with making reports of flood bots and other abuses, logs are required. http://www.report-abuse.net/ [I7]
[20:17] <+Class> #cservice - Undernet Channel Service. [I8]
[20:18] <+Class> #help - General help available for more experienced users, along with newbies. [I9]
[20:18] <+Class> #opschool - A CService Class similar to this. Check the channel topic for the next class scheduled or go to http://cservice.undernet.org/main/opschool/index.html for a complete schedule. [I10]
[20:18] <+Class> Undernet also provides e-mail addresses where you can get help. Here are a few which you should know. [I11]
[20:19] <+Class> cservice@undernet.org - Channel Service mailing list. [I12]
[20:19] <+Class> opschool@undernet.org - OpSchool mailing list. [I13]
[20:19] <+Class> abuse@undernet.org - Abuse or misuse of power, e.g. IRC operators, NOT channel affairs or abuse-exploits@undernet.org that deal with bots, proxies, drones. [I14]
[20:19] <+Class> help@undernet.org - For more experienced users along with newbie help. [I15]
[20:20] <+Class> user-com@undernet.org - User Committee mailing list. [I16]
[20:20] <+Class> Like explained before, if absolutely necessary, you can get an IRC Op to assist you. Also, Undernet has a homepage with useful resources at http://www.undernet.org . [I17]
[20:20] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [IP]
[20:20] <@I-Q_Tutor> Don't you wish you had a patent on the @ symbol?
[20:20] <@R-Z_Tutor> i actually do
[20:21] <@I-Q_Tutor> heh
[20:21] <+Class> Section J - HELP AND PLACES MENTIONED: Where to find the places mentioned in this class. [J1]
[20:21] <+Class> Besides using #UserGuide and the Documents Committee, we mentioned earlier just a few places where you can get help from, but there are a lot more. Many resources are available such as IRC channels, Web sites and e-mail addresses. [J2]
[20:21] <+Class> SECTION A - Floods - NoFlood Document - Available at Documents Project web site - http://www.undernet.org/user-com/documents . [J3]
[20:22] <+Class> Firewalls - BlackIce Defender: http://blackice.iss.net . ZoneAlarm: http://www.zonelabs.com . Shields Up!: http://www.grc.com . [J4]
[20:22] <+Class> Windows Updates - http://windowsupdate.microsoft.com . [J5]
[20:22] <+Class> SECTION B - DoS Attacks - For Information - http://www.irchelp.org/irchelp/nuke/ . [J6]
[20:22] <+Class> McAfee Firewall - http://www.mcafee-at-home.com/default.asp - Norton Personal Firewall - http://www.symantec.com - Tiny Personal Firewall - http://www.tinysoftware.com , Outpost Firewall Pro - http://www.agnitum.com/products/outpost . [J7]
[20:23] <+Class> Firewalls FAQs and HOWTOs for Linux users - http://www.firewallguide.com/linux.htm - Iptables info - http://iptables-tutorial.frozentux.net/iptables-tutorial.html [J8]
[20:23] <+Class> SECTION D - Scripts and Bots - Eggdrop - channel #eggdrop - URLs: http://www.eggheads.org or http://www.egghelp.org/ [J9]
[20:23] <+Class> Darkbot - http://darkbot.sourceforge.net/ -- Emech - http://www.energymech.net . [J10]
[20:23] <+Class> mIRC scripts and bots - channel #mircscripting - URL - http://www.mircscripts.org/ . [J11]
[20:24] <+Class> BotDoc - http://www.user-com.undernet.org/documents/botdocs.php - the Documents Project - http://www.undernet.org/user-com/documents . [J12]
[20:24] <+Class> SECTION E - Advanced Commands - IRC Command Cosmos - http://www.irchelp.org/irchelp/misc/ccosmos.html . [J13]
[20:24] <+Class> SECTION F - Trojans - Channels - #vh, #nohack, #dmsetup - URLs - http://nai.com/us/security/home.asp - http://www.nohack.net - http://www.hackfix.org/ [J14]
[20:24] <+Class> The Cleaner - http://www.moosoft.com/thecleaner - Configuration of the Cleaner - http://hackfix.org/software/configure/cleaner.html . [J15]
[20:25] <+Class> PC-Cillin antivirus - http://us.trendmicro.com/us/products/personal/antivirus-plus-anti-spyware/index.html -- Trend Micro Free Online Virus Scan - http://housecall.trendmicro.com/ [J16]
[20:25] <+Class> Kaspersky antivirus - http://www.kaspersky.com -- Norman Antivirus - http://www.norman.com -- Norton antivirus - http://www.symantec.com -- McAfee antivirus - http://www.mcafee.com/ . [J17]
[20:25] <+Class> SECTION G - Undernet Administration - CService - Channel Service Committee - CService@undernet.org - http://cservice.undernet.org -- Coder-Com - Coding Committee - coder-com@undernet.org - http://www.coder-com.undernet.org . [J18]
[20:25] <+Class> User-Com - User Committee - user-com@undernet.org - http://www.user-com.undernet.org -- Routing-Com - Routing Committee - routing-com@undernet.org - http://www.routing-com.undernet.org . [J19]
[20:26] <+Class> Undernet FTP site - http://ftp.undernet.org . [J20]
[20:26] <+Class> SECTION H - Documentation - Documents Project - http://www.user-com.undernet.org/documents - Userguide - /msg Userguide genhelp - Misc Help Channels - #UserGuide, #help, #mIRC, #CService, #newbies - For various documents and help, check out Undernet's FTP site at http://ftp.undernet.org . Also for general IRC help, take a look at www.irchelp.org . [J21]
[20:26] <+Class> We'll pause briefly in case you have any questions that you would like to ask your tutor. [JP]
[20:26] <@I-Q_Tutor> A-H_Tutor once confused a script for a recipe and baked a potato in her cd-rom drive, which was still ok, until she added sourcreme to her keyboard.
[20:27] <+Class> Section K - CLOSING: #Class is held every Friday at 7:30 pm EDT (Friday 23:30GMT) and Sunday at 12:30PM EDT (Sun 16:30PM GMT). [K1]
[20:27] <+Class> It has been a pleasure to teach the class today, and we all hope you learned something new. [K2]
[20:27] <+Class> IRC is a fun and exciting way to communicate with others. We hope you enjoy your experience online, and hope that you come back to Undernet often. [K3]
[20:28] <+Class> We'd like to thank the the people who made this script possible: Many additions and changes have been made and therefore many people have been involved, I can't mention all the names, but to those who helped, THANK YOU very much. [K4]
[20:28] <+Class> We'd also like to thank all the tutors who take their time to help you every week. [K5]
[20:28] <+Class> Additionally we'd like to thank everyone who helps in all of the help channels for their time and effort in making IRC a better place. [K6]
[20:28] <+Class> Don't forget to check out our web page at http://www.user-com.undernet.org/class/ . [K7]
[20:29] <+Class> For a log of this Advanced or the Beginner User Class, check out our web page or e-mail us at class@undernet.org. [K8]
[20:29] <+Class> Thank you all for attending, and we wish you a pleasant chat on Undernet! [END]
[20:29] * R-Z_Tutor is now known as ffss
[20:29] * I-Q_Tutor sets mode: -mD+d
[20:29] * I-Q_Tutor is now known as Season`d
[20:29] <@Season`d> you can now chat normall in the channel
[20:29] <@Season`d> normally even