diff --git a/.gitattributes b/.gitattributes index 8e948c5..39d732b 100644 --- a/.gitattributes +++ b/.gitattributes @@ -1 +1,15 @@ * text=auto !eol +/ChangeLog -text +/LICENSE -text +/Makefile.in -text +/README.blsb -text +/RELNOTES -text +/aclocal.m4 -text +/blsb.c -text +/blsb.h -text +/blsb_help.c -text +/configure -text +/configure.in -text +/install-sh -text +/modconfig.h.in -text +/modconfigwin32.h -text diff --git a/ChangeLog b/ChangeLog new file mode 100644 index 0000000..645f9ed --- /dev/null +++ b/ChangeLog @@ -0,0 +1,4 @@ +Black List Scanning Bot Module for NeoStats Changelog. +============================================================================== +1.0 - Fish (M) + - Initial Version diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..5131b99 --- /dev/null +++ b/LICENSE @@ -0,0 +1,341 @@ +# $Id: LICENSE,v 1.1 2002/09/04 08:52:34 fishwaldo Exp $ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/Makefile.in b/Makefile.in new file mode 100644 index 0000000..3daeed5 --- /dev/null +++ b/Makefile.in @@ -0,0 +1,60 @@ +#Neostats Module Makefile +CC = @CC@ +CFLAGS = @CFLAGS@ +LDFLAGS = @LIBS@ +INSTALL = @INSTALL@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_DATA = @INSTALL_DATA@ +DIRECTORY = @DIRINST@/modules/ +INCLUDES = -I@DIRINST@/include/ -I. + +SRCS = blsb.c blsb_help.c +OBJS = ${SRCS:.c=.o} +TARGET = blsb.so +DOCS = README.blsb +DATA = +SCRIPTS = +DISTFILES = $(SRCS) $(DOCS) modconfig.h.in configure install-sh ChangeLog Makefile.in blsb.h LICENSE RELNOTES modconfigwin32.h +DISTDIR = @PACKAGE@-@VERSION@ + +all: module + @echo "Compilation complete." + @echo "Run 'make install' (or 'gmake install' on some systems) to install." + @echo "If you require support, see the README file." + +# include dependency info +@MAKEDEPENDENCIES@ + +.c.o: + $(CC) -c $(CFLAGS) $(INCLUDES) $< + $(CC) -MM $(INCLUDES) -c $< > $*.d + + +module: $(OBJS) + $(LD) -shared -o $(TARGET) $(LDFLAGS) $(OBJS) + +clean: + /bin/rm -rf $(TARGET) *.o Makefile *.log modconfig.h + +install: module + $(INSTALL) -m 644 $(TARGET) $(DIRECTORY) + $(INSTALL) -m 644 $(DOCS) $(DIRECTORY)../doc/ + @echo "Installation complete." + @echo "See the README file for instructions on loading this module." + +dist: + @echo -n "Creating directories" + @-rm -rf $(DISTDIR) + @mkdir $(DISTDIR) + @mkdir $(DISTDIR)/libopm + @echo "Done" + @echo -n "Copying distribution files" + @for file in $(DISTFILES); do \ + echo -n "."; \ + cp -pr $$file $(DISTDIR)/$$file; \ + done + @echo "Done" + @tar -czf $(DISTDIR).tar.gz $(DISTDIR)/* + @echo "Tar file $(DISTDIR).tar.gz created, Freshmeat Time" + +$(OBJS): Makefile diff --git a/README.blsb b/README.blsb new file mode 100644 index 0000000..ce6e894 --- /dev/null +++ b/README.blsb @@ -0,0 +1,680 @@ + +OPSB Manual + _________________________________________________________________ + + 1. Prerequisites and Installation. + + 1.1. Compiling and Installation + + 2. Basic Configuration + + 2.1. Exclusion Lists + 2.2. TARGET IP and TARGET PORT + 2.3. BanTime + + 3. Detailed Configuration + + 3.1. CACHETIME Setting + 3.2. SCAN Setting + 3.3. AKILL Setting + 3.4. OPMDOMAIN Setting + 3.5. MAXBYTES Setting + 3.6. TIMEOUT + 3.7. OPENSTRING + 3.8. SPLITTIME + 3.9. SCANMSG Setting + 3.10. PORTS Setting + + 3.10.1. Listing Ports/Protocols + 3.10.2. Adding Ports + 3.10.3. Deleting Ports + + 4. Operational Commands + + 4.1. LOOKUP Command + 4.2. INFO Command + 4.3. CHECK Command + 4.4. STATUS Command + + Welcome to the Open Proxy Scanning Bot (OPSB) Manual. This document + will aid you in setting up and running OPSB on your IRC network. + + OPSB is a Proxy Scanning Service that scans connecting clients for + Open Proxies. These Open Proxies are often used by malicious users and + trojans to connect to your network and attack the network, users, or + channels that you host. It bases its scanning engine on the BOPM proxy + scanning library available at http://www.blitzed.org, but unlike the + BOPM software, it has native support to scan all clients network wide, + rather than via individual servers. This means that you only need one + OPSB service running on your network to protect your entire IRC + network. + + Additionally, OPSB makes use of Open Proxy lists. These lists often + contain IP addresses of verified Open Proxies, and OPSB can ban these + users without even scanning. By default, OPSB uses the blitzed open + proxy list (More details available at http://opm.blitzed.org) + + OPSB is flexible in that it has many advanced configuration options + available to IRC administrators, including the ability to easily + modify the protocols and ports to scan of connecting users, as well as + exclude certian users or servers from scanning. This allows you maxium + flexibility without the overhead of running multiple copies of proxy + scanning software. In addition, it has the ability to Queue up scans, + so during periods of peak usage, OPSB will not consume all bandwidth + or file descriptors, but still scan users in a timely manor. + + Proxy Scanning is only one defence against Trojans and Malicious + users, and can not detect all types of open Proxies. We therefore + recomend that the IRC administrators run other software such as + SecureServ, and familiarize themselves with the OperServ functionality + found in most traditional IRC services packages. + + By Default, OPSB scans the following protocols and ports (But this can + be easily customized) + * HTTP Proxies on Port 80, 3128, 8000, 8080 + * HTTP Post Proxies on Port 80, 3128, 8000, 8080 + * Wingate Servers on Port 23 + * Insecure Cisco Routers on port 23 + * SOCKS4 Servers on 1080 + * SOCKS5 Servers on 1080 + + These ports are some of the more common ports, but administrators + might find other ports that are often associated with open proxies. In + these cases, the administrator can simple add the new port to be + scanning without restarting OPSB. + +Warning + + When picking a host to run OPSB from, make sure you check with your + Shell or ISP provider to ensure that there are no Transparent HTTP + proxies enabled on that network. Transparent proxies are often used to + speed up HTTP downloads for users without requiring the user to update + their browser configuration. If you often get false positive scans on + users on port 80, then most likely your hosting provider has + implemented a Transparent Proxy. See if they can disable this + transparent proxy for you, or alternativly, find a new hosting + provider that does not run a transparent proxy. THERE IS NO WAY FOR + OPSB TO DETECT IT IS BEHIND A TRANSPARENT PROXY. + + OPSB is written and maintained by Justin Hammond. It requires the + NeoStats software. More information about OPSB, or NeoStats, can be + found at http://www.neostats.net/ + + OPSB is Copyright, 2004 by Justin Hammond. + +1. Prerequisites and Installation. + + OPSB is designed to run on Top of NeoStats. The Following requirements + at the time of writting are required for NeoStats: + * A Linux or BSD based Server or Shell. + * A supported IRCd. Currently, Hybrid7, Unreal, Ultimate2.x, + Ultimate3.x, NeoIRCd, Bahumat + * Some basic Unix administration Skill + * Of Course, a IRC network to connect it all together. + + Please refer to the NeoStats website for more information on the + requirements + + OPSB itself requires the following: + * NeoStats 2.5.8 or Higher correctly installed and Running + * The time to read this entire document. + +Warning + OPSB has the potential to Akill/Gline your entire network. Its + strongly suggested that you read this entire document before even + attempting to compile OPSB, as I'm just going to laugh, if you + didn't read, and it AKILL's your entire network. This is Beta + Software, there are BUGS. beware. + +1.1. Compiling and Installation + + As long as you have successfully setup NeoStats, and installed it + correctly, Compiling OPSB is very simple and straight forward. First + you must extract the files from the download package. This is as + simple as: +bash$ tar -xzf OPSB-.tar.gz + + This should then create a directory called OPSB- where + is the Version of OPSB. Then Proceed to Change into the OPSB + directory, and run Configure as follows: +bash$./configure [--enable-debug | --with-neostats=] + + --enable-debug is only usefull for diagnostics purposes when used in + conjuction with debugging tools. There should be no need to use this + option on a day to day basis + + --with-neostats= should be used if your neostats directory is not + in a standard location (~/NeoStats/). Replace with the full path + to your NeoStats installation directory (NOT SOURCE DIRECTORY) + + Configuring OPSB will look something like the following screen: +[Fish@fish-dt]$ ./configure +checking for gcc... gcc +checking for C compiler default output... a.out +checking whether the C compiler works... yes +checking whether we are cross compiling... no +checking for suffix of executables... +checking for suffix of object files... o +checking whether we are using the GNU C compiler... yes +checking whether gcc accepts -g... yes +checking for gcc option to accept ANSI C... none needed +checking for a BSD-compatible install... /usr/bin/install -c +checking for pcre_compile in -lpcre... yes +checking Location of NeoStats...... /home/fish/NeoStats/ +checking for /home/fish/NeoStats//include/dl.h... yes +checking Version of NeoStats...... Compatible Version +checking Whether to Enable Debuging...... no +configure: creating ./config.status +config.status: creating Makefile + +(*----------------------------------------------------------*) +(| To compile your module, please type 'make' |) +(| If make completes without errors, then you |) +(| Must 'make install', but please be sure that NeoStats |) +(| Is not currently running with a module of the same name |) +(| Running, otherwise Make install will not work |) +(| !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |) +(| If you are running a BSD, make install may produce a |) +(| Error, if that is the case, then please manually copy |) +(| opsb.so to the NeoStats/dl directory |) +(| !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |) +(*----------------------------------------------------------*) +(| For Support please visit: |) +(| IRC: /server irc.irc-chat.org |) +(| #neostats channel |) +(| WWW: http://www.neostats.net/boards/ |) +(*----------------------------------------------------------*) +(|This Module was written by: |) +(| fish (fish@dynam.ac) |) +(*----------------------------------------------------------*) + + If the configuration did not produce a error, you may then move onto + Compiling OPSB. Compiling is simply just issuing the "make" command + (or "gmake" if you are running BSD): +[Fish@fish-dt]$ make +(cd libopm; make libopm.a) +make[1]: Entering directory `/home/fish/opsb/libopm' +gcc -c -O2 -Wall -I. -I.. compat.c +gcc -c -O2 -Wall -I. -I.. config.c +gcc -c -O2 -Wall -I. -I.. inet.c +gcc -c -O2 -Wall -I. -I.. libopm.c +gcc -c -O2 -Wall -I. -I.. list.c +gcc -c -O2 -Wall -I. -I.. malloc.c +gcc -c -O2 -Wall -I. -I.. proxy.c +ar cru libopm.a compat.o config.o inet.o libopm.o list.o malloc.o proxy.o +ranlib libopm.a +make[1]: Leaving directory `/home/fish/opsb/libopm' +gcc -c -O2 -Wall -I/home/fish/NeoStats//include/ -I. -Ilibopm opsb.c +gcc -c -O2 -Wall -I/home/fish/NeoStats//include/ -I. -Ilibopm proxy.c +gcc -c -O2 -Wall -I/home/fish/NeoStats//include/ -I. -Ilibopm opsb_help.c +ld -shared -o opsb.so opsb.o proxy.o opsb_help.o libopm/libop +m.a +[1005|/home/fish/opsb] +[Fish@fish-dt]$ + + Again, check for Error messages. As long as there are not error + messages, "make install" will install OPSB, this README file, and any + auxiluary files needed into your NeoStats directory: +[Fish@fish-dt]$ make install +(cd libopm; make libopm.a) +make[1]: Entering directory `/home/fish/opsb/libopm' +make[1]: `libopm.a' is up to date. +make[1]: Leaving directory `/home/fish/opsb/libopm' +ld -shared -o opsb.so opsb.o proxy.o opsb_help.o libopm/libop +m.a +/usr/bin/install -c + -m 644 opsb.so + /home/fish/NeoStats//dl/ +/usr/bin/install -c + -m 644 README.opsb opsb.S +ettings /home/fish/NeoStats//dl/../doc/ +[1006|/home/fish/opsb] + + If you recieve *ANY* errors at all during the this process, please + post them on our Support boards, at http//www.neostats.net/boards/ + + Once Installation is complete, you can either configure NeoStats to + load OPSB when it starts, or load OPSB via IRC. + + To Configure NeoStats to automatically load OPSB when it boots, add + the following line to your "neostats.cfg" file in the NeoStats + directory: + + LOAD_MODULE OPSB + + To load OPSB via IRC, you must make sure you have the appropriate + permissions and issue the following command: + + /msg neostats load OPSB + + Thats it. OPSB is now loaded and ready for use (in fact, it will + already be running now, but read on for futher information. + +2. Basic Configuration + + OPSB is completly configured online via IRC. When you first start up + OPSB, it attempts some "Sane" defaults for you to get started with, + but you should always review these settings as soon as you install. + Additionally, while its in this "Default" state, it will warn you + every so often via a global message as well as messages to the + services channel that it is still "unconfigured". Some of the settings + that you may want to review right away are: + * Exclusion Lists - You should setup a Exclude list for your IRC + Services server (NickServ etc) + * Target IP address and Ports that OPSB tries to get the proxies to + connect to. + * Default Ban Time when OPSB finds a open Proxy. + + These are outlined below: + +2.1. Exclusion Lists + + Exclusion lists allow you to specify certian Hostmasks or Servers that + should be excluded from monitoring by OPSB. This exclusion list would + allow a administrator to say, allow users on that are matched against + a open proxy, when the administrator has verified that the trojan does + not in fact exist on the users host. + +Caution + + Exclusions should be setup for your Services Server, so that OPSB does + not try to scan ChanServ, or NickServ, or any of the bots relating to + Nickname protection. + + Adding a Entry + + To add a entry to the Exclusion list, use the following format: +/msg OPSB exclude add <1/0> + + Where: + + = The HostName/Server or Channel name. WildCards ? and * are + permitted. + + = The type of exclusion. 0 is for HostNames, 1 is for Servers + + = a short description of the exclusion, for operator + reference only. + + The output is as follows: +>OPSB< exclude add services.irc-chat.net 1 Blah is my reason +-OPSB- Added services.irc-chat.net (Server) exception to list + + Listing an Entry + + To list the Exclusions simple type: +/msg OPSB exclude list + + And all the current exclusions are listed. Additionaly, a Position + number is provided for use with the delete command. The output is as + follows: +>OPSB< exclude list +-OPSB- Exception List: +-OPSB- 1) *.blah.com (Server) Added by Fish for Blah is my reason +-OPSB- 2) is.blah.com (HostName) Added by Fish for can by high +-OPSB- End of List. + + Deleting an Entry + + To delete a entry, you should first lookup the Position of the entry + that you wish to delete. The format of the command is as follows: +/msg OPSB exclude del + + Where: + + is the position of the entry you wish to delete in the list + + The output of the command is as follows: +>OPSB< exclude del 1 +-OPSB- Deleted services.irc-chat.net server out of exception list + +2.2. TARGET IP and TARGET PORT + + By default, OPSB sets up each proxy scan to attempt to connect back to + the IP address and port of the server that NeoStats connects to. This + may not always be what you wish, as it can help a attacker map our how + your network is structured. Ideally, you should pick the IP address of + a IRC server you host that is stable and on a fast connection, and + enter its IP address and port numbers into OPSB. + + Changing the TargetIP + + To add a entry to the Helper list, use the following format: +/msg OPSB set targetip + + Where: + + = The ip address to attempt to get proxies to connect + to + + The output is as follows: + -> *opsb* set targetip 203.208.228.144 +=opsb= Target IP set to 203.208.228.144 + + Changing the Target Port + + To list the helpers simple type: +/msg OPSB set targetport + + Where: + + = the new port to attempt to get proxies to connect to + + The output is as follows: + -> *opsb* set targetport 6667 +=opsb= Target PORT set to 6667 + +2.3. BanTime + + OPSB by default bans the IP/Hostname of a Open Proxy for 1 day (86400 + seconds). Some networks may wish to increase or decrease this time + value. + + Changing the Ban Time + + To change the akilltime, type: + -> *opsb* set akilltime 86400 +=opsb= Ban time changed to 86400 + +3. Detailed Configuration + + OPSB attempts to be as configurable as possible in order to cater for + each individual networks requirements. This in turn though makes the + configuration very complex. There are many many settings with OPSB + that affect how it operates, how it responds and even, how affects the + performance of NeoStats Overall. Out of the box, OPSB provides + sensible defaults for these settings, but you may wish to read this + section for details on exactly what each option does, and its affect + on how OPSB operates. + + The following list summaries the available Options you can set in OPSB + * CACHETIME + * SCAN + * AKILL + * OPMDOMAIN + * MAXBYTES + * TIMEOUT + * OPENSTRING + * SPLITTIME + * SCANMSG + * PORTS + + To change any of these settings, you use the Set Interface in OPSB. + Eg: +/msg OPSB set