1 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
3 File : $Source: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v $
7 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
9 $Id: user-manual.sgml,v 1.27 2002/01/11 14:14:32 hal9 Exp $
11 Written by and Copyright (C) 2001 the SourceForge
12 IJBSWA team. http://ijbswa.sourceforge.net
14 Based on the Internet Junkbuster originally written
15 by and Copyright (C) 1997 Anonymous Coders and
16 Junkbusters Corporation. http://www.junkbusters.com
20 Sun 09/23/01 08:53:31 PM
22 This is an unfinished, rough draft. Anyone reading this, believe let me
23 know errors!!!!! Stefan, especially you!
25 Hal Burgiss <hal@foobox.net>
30 <title>Junkbuster User Manual</title>
32 <pubdate>$Id: user-manual.sgml,v 1.27 2002/01/11 14:14:32 hal9 Exp $</pubdate>
37 <orgname>By: Junkbuster Developers</orgname>
44 The user manual gives the users information on how to install and configure
45 <application>Internet Junkbuster</application>. <application>Internet
46 Junkbuster</application> is an application that provides privacy and
47 security to users of the World Wide Web.
50 You can find the latest version of the user manual at <ulink url="http://ijbswa.sourceforge.net/user-manual/">http://ijbswa.sourceforge.net/user-manual/</ulink>.
54 Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>.
61 <!-- ~~~~~ New section ~~~~~ -->
63 <sect1 id="introduction"><title>Introduction</title>
65 <application>Internet Junkbuster</application> is a web proxy with advanced
66 filtering capabilities for protecting privacy, filtering web page content,
67 managing cookies, controlling access, and removing ads, banners, pop-ups and
68 other obnoxious Internet Junk. <application>Junkbuster</application> has a
69 very flexible configuration and can be customized to suit individual needs
70 and tastes. <application>Internet Junkbuster</application> has application
71 for both stand-alone systems and multi-user networks.
75 This documentation is included with the current development version of
76 <application>Internet Junkbuster</application> and is incomplete at this
77 point. The most up to date reference for the time being is still the comments
78 in the source files and in the individual configuration files. Development
79 of version 3.0 is currently underway, and includes many significant changes and
80 enhancements over earlier verions. The target release date for stable v3.0 is
85 Since this is a development version, some features are in the process of
86 being implemented. This documentation may be slightly out of sync as a
87 result. And there <emphasis>are</emphasis> bugs, though hopefully not many!
91 <!-- ~~~~~ New section ~~~~~ -->
93 <title>New Features</title>
95 In addition to <application>Junkbuster's</application> traditional features
96 of ad and banner blocking and cookie management, this is a list of new
97 features currently under development:
105 A browser based configuration utility (WIP at
106 <ulink url="http://i.j.b">http://i.j.b</ulink>).
112 Modularized configuration that will allow for system wide settings, and
113 individual user settings. (not implemented yet, probably a 3.1 feature)
119 Blocking of annoying pop-up browser windows (previously available as a
126 Support for HTTP/1.1 (partially implemented at this point).
132 Support for Perl Compatible Regular Expressions in the configuration files, and
133 generally a more sophisticated configuration syntax over previous versions.
139 Web page content filtering.
151 Auto-detection of config file changes.
160 In addition, the configuration is much more versatile overall.
167 <!-- ~ End section ~ -->
170 <!-- ~~~~~ New section ~~~~~ -->
171 <sect1 id="installation"><title>Installation</title>
173 <application>Junkbuster</application> is available as raw source code, or
174 pre-compiled binaries. See the <ulink
175 url="http://sourceforge.net/projects/ijbswa/">Junkbuster Home Page</ulink>
176 for current release info. <application>Junkbuster</application> is also available
178 url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
179 This is the recommended approach at this time. But please be aware that CVS
180 is constantly changing, and it may break in mysterious ways.
183 <!-- ~~~~~ New section ~~~~~ -->
184 <sect2 id="installation-source"><title>Source</title>
186 For gzipped tar archives, unpack the source:
191 tar xzvf ijb_source_* [.tgz or .tar.gz]
192 cd ijb_source_2.9.10_beta
197 For retrieving the current CVS sources, you'll need the CVS
198 package installed first. To download CVS source:
203 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
204 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
210 This will create a directory named <filename>current/</filename>, which will
211 contain the source tree.
215 Then, in either case, to build from tarball/CVS source:
220 ./configure (--help to see options)
221 make (the make from gnu, gmake for *BSD)
223 make -n install (to see where all the files will go)
224 make install (to really install)
229 For Redhat and SuSE Linux RPM packages, see below.
235 <!-- ~~~~~ New section ~~~~~ -->
236 <sect2 id="installation-rh"><title>Red Hat</title>
238 To build Redhat RPM packages, install source as above. Then:
243 autoheader [suggested for CVS source]
244 autoconf [suggested for CVS source]
251 This will create both binary and src RPMs in the usual places. Example:
255 /usr/src/redhat/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
258 /usr/src/redhat/SRPMS/junkbuster-2.9.10-1.src.rpm
262 To install, of course:
267 rpm -Uvv /usr/src/redhat/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
272 This will place the <application>Junkbuster</application> configuration
273 files in <filename>/etc/junkbuster/</filename>, and log files in
274 <filename>/var/log/junkbuster/</filename>.
279 <!-- ~~~~~ New section ~~~~~ -->
280 <sect2 id="installation-suse"><title>SuSE</title>
282 To build SuSE RPM packages, install source as above. Then:
287 autoheader [suggested for CVS source]
288 autoconf [suggested for CVS source]
295 This will create both binary and src RPMs in the usual places. Example:
299 /usr/src/packages/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
302 /usr/src/packages/SRPMS/junkbuster-2.9.10-1.src.rpm
306 To install, of course:
311 rpm -Uvv /usr/src/packages/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
316 This will place the <application>Junkbuster</application> configuration
317 files in <filename>/etc/junkbuster/</filename>, and log files in
318 <filename>/var/log/junkbuster/</filename>.
324 <!-- ~~~~~ New section ~~~~~ -->
325 <sect2 id="installation-os2"><title>OS/2</title>
332 The OS/2 version of <application>Junkbuster</application> requires the EMX
333 runtime library to be installed. The EMX runtime library is available on
334 the hobbes OS/2 archive, among many other locations:
335 <ulink url="http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=emxrt.zip&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fdev%2Femx%2Fv0.9d">http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&button=Search&key=emxrt.zip&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fdev%2Femx%2Fv0.9d</ulink>
339 <application>Junkbuster</application> is packaged in a WarpIN self-
340 installing archive. The self-installing program will be named depending
341 on the release version, something like:
342 <filename>ijbos123.exe</filename>. In order to install it, simply run
343 this executable or double-click on its icon and follow the WarpIN
344 installation panels. A shadow of the <application>Junkbuster</application>
345 executable will be placed in your startup folder so it will start
346 automatically whenever OS/2 starts.
350 The directory you choose to install <application>Junkbuster</application>
351 into will contain all of the configuration files.
355 If you would like to build binary images on OS/2 yourself, you will need
356 a working EMX/GCC environment, plus several Unix-like tools. The Hobbes
357 OS/2 archive is a good place to start when building such an environment.
358 A set of Unix-like tools named gnupack is located here:
359 <ulink url="http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&key=gnupack&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fapps">http://hobbes.nmsu.edu/cgi-bin/h-search?sh=1&key=gnupack&stype=all&sort=type&dir=%2Fpub%2Fos2%2Fapps</ulink>
362 Once you have the source code unpacked as above, you can build the binaries
363 from the <filename>current/</filename> directory:
377 <!-- ~~~~~ New section ~~~~~ -->
378 <sect2 id="installation-win"><title>Windows</title>
379 <para>Click-click. (I need help on this. Not a clue here. Also for
380 configuration section below. HB.)
384 <!-- ~~~~~ New section ~~~~~ -->
385 <sect2 id="installation-other"><title>Other</title>
387 Some quick notes on other Operating Systems.
391 For FreeBSD (and other *BSDs?), the build will require <command>gmake</command>
392 instead of the included <command>make</command>. <command>gmake</command> is
393 available from <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>.
394 The rest should be the same as above for Linux/Unix.
401 <!-- ~ End section ~ -->
404 <!-- ~~~~~ New section ~~~~~ -->
405 <sect1 id="configuration"><title>Junkbuster Configuration</title>
407 For Unix, *BSD and Linux, all configuraton files are located in
408 <filename>/etc/junkbuster/</filename> by default. For MS Windows and OS/2,
409 these are all in the same directory as the
410 <application>Junkbuster</application> executable. The name and number of
411 configuration files has changed from previous versions, and is subject to
412 change as development progresses.
416 The installed defaults provide a reasonable starting point, though possibly
417 aggressive by some standards. For the time being, there are only three
418 default configuration files (this will change in time):
426 The main configuration file is named <filename>config</filename>
427 on Linux, Unix, BSD, and OS/2, and <filename>config.txt</filename> on
428 Windows. On Amiga, it is
429 <filename>AmiTCP:db/junkbuster/config</filename>.
435 The <filename>ijb.action</filename> file is used to define various
436 <quote>actions</quote> relating to images, banners, pop-ups, access
437 restrictions, banners and cookies. There is a CGI based editor for this
438 file that can be accessed via <ulink
439 url="http://i.j.b">http://i.j.b</ulink>. This is the easiest method of
440 configuring actions. (Still under active development. Other actions
441 files are included as well with differing levels of filtering
442 and blocking, e.g. <filename>ijb-basic.action</filename>.)
448 The <filename>re_filterfile</filename> file can be used to rewrite the raw
449 page content, including text as well as embedded HTML and JavaScript.
457 <filename>ijb.action</filename> and <filename>re_filterfile</filename>
458 can use Perl style regular expressions for maximum flexibility. All files use
459 the <quote><literal>#</literal></quote> character to denote a comment. Such
460 lines are not processed by <application>Junkbuster</application>. After
461 making any changes, there is no need to restart
462 <application>Junkbuster</application> in order for the changes to take
463 effect. <application>Junkbuster</application> should detect such changes
468 While under development, the configuration content is subject to change.
469 The below documentation may not be accurate by the time you read this.
470 Also, what constitutes a <quote>default</quote> setting, may change, so
471 please check all your configuration files on important issues.
474 <!-- ~~~~~ New section ~~~~~ -->
477 <title>The Main Configuration File</title>
479 Again, the main configuration file is named <filename>config</filename> on
480 Linux/Unix/BSD and OS/2, and <filename>config.txt</filename> on Windows.
481 Configuration lines consist of an initial keyword followed by a list of
482 values, all separated by whitespace (any number of spaces or tabs). For
490 <emphasis>blockfile blocklist.ini</emphasis>
497 Indicates that the blockfile is named <quote>blocklist.ini</quote>.
501 A <quote><literal>#</literal></quote> indicates a comment. Any part of a
502 line following a <quote><literal>#</literal></quote> is ignored, except if
503 the <quote><literal>#</literal></quote> is preceded by a
504 <quote><literal>\</literal></quote>.
508 Thus, by placing a <quote><literal>#</literal></quote> at the start of an
509 existing configuration line, you can make it a comment and it will be treated
510 as if it weren't there. This is called <quote>commenting out</quote> an
511 option and can be useful to turn off features: If you comment out the
512 <quote>logfile</quote> line, <application>junkbuster</application> will not
513 log to a file at all. Watch for the <quote>default:</quote> section in each
514 explanation to see what happens if the option is left unset (or commented
519 Long lines can be continued on the next line by using a
520 <quote><literal>\</literal></quote> as the very last character.
524 There are various aspects of <application>Junkbuster</application> behavior
529 <!-- ~~~~~ New section ~~~~~ -->
532 <title>Defining Other Configuration Files</title>
535 <application>Junkbuster</application> can use a number of other files to tell it
536 what ads to block, what cookies to accept, etc. This section of the
537 configuration file tells <application>Junkbuster</application> where to find
538 all those other files.
542 On <application>Windows</application>, <application>Junkbuster</application>
543 looks for these files in the same directory as the executable. On Unix and
544 OS/2, <application>Junkbuster</application> looks for these files in the current
545 working directory. In either case, an absolute path name can be used to
550 When development goes modular and multiuser, the blocker, filter, and
551 per-user config will be stored in subdirectories of <quote>confdir</quote>.
552 For now, only <filename>confdir/templates</filename> is used for storing HTML
553 templates for CGI results.
557 The location of the configuration files:
564 <emphasis>confdir /etc/junkbuster</emphasis> # No trailing /, please.
571 The directory where all logging (i.e. <filename>logfile</filename> and
572 <filename>jarfile</filename>) takes place. No trailing
573 <quote><literal>/</literal></quote>, please:
580 <emphasis>logdir /var/log/junkbuster</emphasis>
587 Note that all file specifications below are relative to
588 the above two directories!
592 The <quote>ijb.action</quote> file contains patterns to specify the actions to
593 apply to requests for each site. Default: Cookies to and from all
594 destinations are kept only during the current browser session (i.e. they
595 are not saved to disk). Popups are disabled for all sites. All sites are
596 filtered if <quote>re_filterfile</quote> specified. No sites are blocked. An
597 empty image is displayed for filtered ads and other images (formerly
598 <quote>tinygif</quote>). The syntax of this file is explained in detail <link
599 linkend="actionsfile">below</link>.
606 <emphasis>actionsfile ijb.action</emphasis>
613 The <quote>re_filterfile</quote> file contains content modification rules.
614 These rules permit powerful changes on the content of Web pages, e.g., you
615 could disable your favourite JavaScript annoyances, rewrite the actual
616 content, or just have some fun replacing <quote>Microsoft</quote> with
617 <quote>MicroSuck</quote> wherever it appears on a Web page. Default: No
618 content modification, or whatever the developers are playing with :-/
625 <emphasis>re_filterfile re_filterfile</emphasis>
632 The logfile is where all logging and error messages are written. The logfile
633 can be useful for tracking down a problem with
634 <application>Junkbuster</application> (e.g., it's not blocking an ad you
635 think it should block) but in most cases you probably will never look at it.
639 Your logfile will grow indefinitely, and you will probably want to
640 periodically remove it. On Unix systems, you can do this with a cron job
641 (see <quote>man cron</quote>). For Redhat, a <command>logrotate</command>
642 script has been included.
646 On SuSE Linux systems, you can place a line like <quote>/var/log/junkbuster.*
647 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
648 the effect that cron.daily will automatically archive, gzip, and empty the
649 log, when it exceeds 1M size.
653 Default: Log to the a file named <filename>logfile</filename>.
654 Comment out to disable logging.
661 <emphasis>logfile logfile</emphasis>
668 The <quote>jarfile</quote> defines where
669 <application>Junkbuster</application> stores the cookies it intercepts. Note
670 that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
671 Don't store intercepted cookies.
678 <emphasis>#jarfile jarfile</emphasis>
685 If you specify a <quote>trustfile</quote>,
686 <application>Junkbuster</application> will only allow access to sites that
687 are named in the trustfile. You can also mark sites as trusted referrers,
688 with the effect that access to untrusted sites will be granted, if a link
689 from a trusted referrer was used. The link target will then be added to the
690 <quote>trustfile</quote>. This is a very restrictive feature that typical
691 users most propably want to leave disabled. Default: Disabled, don't use the
699 <emphasis>#trustfile trust</emphasis>
706 If you use the trust mechanism, it is a good idea to write up some online
707 documentation about your blocking policy and to specify the URL(s) here. They
708 will appear on the page that your users receive when they try to access
709 untrusted content. Use multiple times for multiple URLs. Default: Don't
710 display links on the <quote>untrusted</quote> info page.
717 <emphasis>trust-info-url http://www.your-site.com/why_we_block.html</emphasis>
718 <emphasis>trust-info-url http://www.your-site.com/what_we_allow.html</emphasis>
726 <!-- ~ End section ~ -->
730 <!-- ~~~~~ New section ~~~~~ -->
733 <title>Other Configuration Options</title>
736 This part of the configuration file contains options that control how
737 <application>Junkbuster</application> operates.
741 <quote>Admin-address</quote> should be set to the email address of the proxy
742 administrator. It is used in many of the proxy-generated pages. Default:
750 <emphasis>#admin-address fill@me.in.please</emphasis>
757 <quote>Proxy-info-url</quote> can be set to a URL that contains more info
758 about this <application>Junkbuster</application> installation, it's
759 configuration and policies. It is used in many of the proxy-generated pages
760 and its use is highly recommended in multi-user installations, since your
761 users will want to know why certain content is blocked or modified. Default:
762 Don't show a link to online documentation.
769 <emphasis>proxy-info-url http://www.your-site.com/proxy.html</emphasis>
776 <quote>Listen-address</quote> specifies the address and port where
777 <application>Junkbuster</application> will listen for connections from your
778 Web browser. The default is to listen on the localhost port 8000, and
779 this is suitable for most users. (In your web browser, under proxy
780 configuration, list the proxy server as <quote>localhost</quote> and the
781 port as <quote>8000</quote>).
785 If you already have another service running on port 8000, or if you want to
786 serve requests from other machines (e.g. on your local network) as well, you
787 will need to override the default. The syntax is
788 <quote>listen-address [<ip-address>]:<port></quote>. If you leave
789 out the IP address, <application>junkbuster</application> will bind to all
790 interfaces (addresses) on your machine and may become reachable from the
791 Internet. In that case, consider using access control lists (acl's) (see
792 <quote>aclfile</quote> above), or a firewall.
796 For example, suppose you are running <application>Junkbuster</application> on
797 a machine which has the address 192.168.0.1 on your local private network
798 (192.168.0.0) and has another outside connection with a different address.
799 You want it to serve requests from inside only:
806 <emphasis>listen-address 192.168.0.1:8000</emphasis>
813 If you want it to listen on all addresses (including the outside
821 <emphasis>listen-address :8000</emphasis>
828 If you do this, consider using ACLs (see <quote>aclfile</quote> above). Note:
829 you will need to point your browser(s) to the address and port that you have
830 configured here. Default: localhost:8000 (127.0.0.1:8000).
834 The debug option sets the level of debugging information to log in the
835 logfile (and to the console in the Windows version). A debug level of 1 is
836 informative because it will show you each request as it happens. Higher
837 levels of debug are probably only of interest to developers.
844 debug 1 # GPC = show each GET/POST/CONNECT request
845 debug 2 # CONN = show each connection status
846 debug 4 # IO = show I/O status
847 debug 8 # HDR = show header parsing
848 debug 16 # LOG = log all data into the logfile
849 debug 32 # FRC = debug force feature
850 debug 64 # REF = debug regular expression filter
851 debug 128 # = debug fast redirects
852 debug 256 # = debug GIF deanimation
853 debug 512 # CLF = Common Log Format
854 debug 1024 # = debug kill popups
855 debug 4096 # INFO = Startup banner and warnings.
856 debug 8192 # ERROR = Non-fatal errors
863 It is <emphasis>highly recommended</emphasis> that you enable ERROR
864 reporting (debug 8192), at least until the next stable release.
868 The reporting of FATAL errors (i.e. ones which crash
869 <application>JunkBuster</application>) is always on and cannot be disabled.
873 If you want to use CLF (Common Log Format), you should set <quote>debug
874 512</quote> ONLY, do not enable anything else.
878 Multiple <quote>debug</quote> directives, are OK - they're logical-OR'd
886 <emphasis>debug 15 # same as setting the first 4 listed above</emphasis>
900 <emphasis>debug 1 # URLs</emphasis>
901 <emphasis>debug 4096 # Info</emphasis>
902 <emphasis>debug 8192 # Errors - *we highly recommended enabling this*</emphasis>
909 <application>Junkbuster</application> normally uses
910 <quote>multi-threading</quote>, a software technique that permits it to
911 handle many different requests simultaneously. In some cases you may wish to
912 disable this -- particularly if you're trying to debug a problem. The
913 <quote>single-threaded</quote> option forces
914 <application>Junkbuster</application> to handle requests sequentially.
915 Default: Multi-threaded mode.
922 <emphasis>#single-threaded</emphasis>
929 <quote>toggle</quote> allows you to temporarily disable all
930 <application>Junkbuster's</application> filtering. Just set <quote>toggle
935 The Windows version of <application>Junkbuster</application> puts an icon in
936 the system tray, which also allows you to change this option. If you
937 right-click on that icon (or select the <quote>Options</quote> menu), one
938 choice is <quote>Enable</quote>. Clicking on enable toggles
939 <application>Junkbuster</application> on and off. This is useful if you want
940 to temporarily disable <application>Junkbuster</application>, e.g., to access
941 a site that requires cookies which you would otherwise have blocked. This can also
942 be toggled via a web browser at the <application>Junkbuster</application>
943 internal address of <ulink url="http://i.j.b">http://i.j.b</ulink> on
948 <quote>toggle 1</quote> means <application>Junkbuster</application> runs
949 normally, <quote>toggle 0</quote> means that
950 <application>Junkbuster</application> becomes a non-anonymizing non-blocking
951 proxy. Default: 1 (on).
958 <emphasis>toggle 1</emphasis>
965 For content filtering, i.e. the <quote>+filter</quote> and
966 <quote>+deanimate-gif</quote> actions, it is neccessary that
967 <application>Junkbuster</application> buffers the entire document body.
968 This can be potentially dangerous, since a server could just keep sending
969 data indefinitely and wait for your RAM to exhaust. With nasty consequences.
973 The <application>buffer-limit</application> option lets you set the maximum
974 size in Kbytes that each buffer may use. When the documents buffer exceeds
975 this size, it is flushed to the client unfiltered and no further attempt to
976 filter the rest of it is made. Remember that there may multiple threads
977 running, which might require increasing the <quote>buffer-limit</quote>
978 Kbytes <emphasis>each</emphasis>, unless you have enabled
979 <quote>single-threaded</quote> above.
986 <emphasis>buffer-limit 4069</emphasis>
993 To enable the web-based <filename>ijb.action</filename> file editor set
994 <application>enable-edit-actions</application> to 1, or 0 to disable. Note
995 that you must have compiled <application>JunkBuster</application> with
996 support for this feature, otherwise this option has no effect. This
997 internal page can be reached at <ulink
998 url="http://i.j.b">http://i.j.b</ulink>.
1002 Security note: If this is enabled, anyone who can use the proxy
1003 can edit the actions file, and their changes will affect all users.
1004 For shared proxies, you probably want to disable this. Default: enabled.
1011 <emphasis>enable-edit-actions 1</emphasis>
1018 Allow <application>JunkBuster</application> to be toggled on and off
1019 remotely, using your web browser. Set <quote>enable-remote-toggle</quote>to
1020 1 to enable, and 0 to disable. Note that you must have compiled
1021 <application>JunkBuster</application> with support for this feature,
1022 otherwise this option has no effect.
1026 Security note: If this is enabled, anyone who can use the proxy can toggle
1027 it on or off (see <ulink url="http://i.j.b">http://i.j.b</ulink>), and
1028 their changes will affect all users. For shared proxies, you probably want to
1029 disable this. Default: enabled.
1036 <emphasis>enable-remote-toggle 1</emphasis>
1044 <!-- ~ End section ~ -->
1047 <!-- ~~~~~ New section ~~~~~ -->
1050 <title>Access Control List (ACL)</title>
1052 Access controls are included at the request of some ISPs and systems
1053 administrators, and are not usually needed by individual users. Please note
1054 the warnings in the FAQ that this proxy is not intended to be a substitute
1055 for a firewall or to encourage anyone to defer addressing basic security
1060 If no access settings are specified, the proxy talks to anyone that
1061 connects. If any access settings file are specified, then the proxy
1062 talks only to IP addresses permitted somewhere in this file and not
1063 denied later in this file.
1067 Summary -- if using an ACL:
1072 Client must have permission to receive service.
1077 LAST match in ACL wins.
1082 Default behavior is to deny service.
1087 The syntax for an entry in the Access Control List is:
1094 ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
1101 Where the individual fields are:
1108 <emphasis>ACTION</emphasis> = <quote>permit-access</quote> or <quote>deny-access</quote>
1110 <emphasis>SRC_ADDR</emphasis> = client hostname or dotted IP address
1111 <emphasis>SRC_MASKLEN</emphasis> = number of bits in the subnet mask for the source
1113 <emphasis>DST_ADDR</emphasis> = server or forwarder hostname or dotted IP address
1114 <emphasis>DST_MASKLEN</emphasis> = number of bits in the subnet mask for the target
1122 The field separator (FS) is whitespace (space or tab).
1126 IMPORTANT NOTE: If the <application>junkbuster</application> is using a
1127 forwarder (see below) or a gateway for a particular destination URL, the
1128 <literal>DST_ADDR</literal> that is examined is the address of the forwarder
1129 or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
1130 target. This is necessary because it may be impossible for the local
1131 <application>Junkbuster</application> to determine the address of the
1132 ultimate target (that's often what gateways are used for).
1136 Here are a few examples to show how the ACL features work:
1140 <quote>localhost</quote> is OK -- no DST_ADDR implies that
1141 <emphasis>ALL</emphasis> destination addresses are OK:
1148 <emphasis>permit-access localhost</emphasis>
1155 A silly example to illustrate permitting any host on the class-C subnet with
1156 <application>Junkbuster</application> to go anywhere:
1163 <emphasis>permit-access www.junkbusters.com/24</emphasis>
1170 Except deny one particular IP address from using it at all:
1177 <emphasis>deny-access ident.junkbusters.com</emphasis>
1184 You can also specify an explicit network address and subnet mask.
1185 Explicit addresses do not have to be resolved to be used.
1192 <emphasis>permit-access 207.153.200.0/24</emphasis>
1199 A subnet mask of 0 matches anything, so the next line permits everyone.
1206 <emphasis>permit-access 0.0.0.0/0</emphasis>
1213 Note, you <emphasis>cannot</emphasis> say:
1220 <emphasis>permit-access .org</emphasis>
1227 to allow all *.org domains. Every IP address listed must resolve fully.
1231 An ISP may want to provide a <application>Junkbuster</application> that is
1232 accessible by <quote>the world</quote> and yet restrict use of some of their
1233 private content to hosts on its internal network (i.e. its own subscribers).
1234 Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
1235 bit netmask). This is how they could do it:
1242 <emphasis>permit-access 0.0.0.0/0 0.0.0.0/0</emphasis> # other clients can go anywhere
1243 # with the following exceptions:
1245 <emphasis>deny-access</emphasis> 0.0.0.0/0 123.124.0.0/16 # block all external requests for
1246 # sites on the ISP's network
1248 <emphasis>permit 0.0.0.0/0 www.my_isp.com</emphasis> # except for the ISP's main
1251 <emphasis>permit 123.124.0.0/16 0.0.0.0/0</emphasis> # the ISP's clients can go
1259 Note that if some hostnames are listed with multiple IP addresses,
1260 the primary value returned by DNS (via gethostbyname()) is used. Default:
1261 Anyone can access the proxy.
1266 <!-- ~ End section ~ -->
1269 <!-- ~~~~~ New section ~~~~~ -->
1272 <title>Forwarding</title>
1275 This feature allows chaining of HTTP requests via multiple proxies.
1276 It can be used to better protect privacy and confidentiality when
1277 accessing specific domains by routing requests to those domains
1278 to a special purpose filtering proxy such as lpwa.com. Or to use
1279 a caching proxy to speed up browsing.
1283 It can also be used in an environment with multiple networks to route
1284 requests via multiple gateways allowing transparent access to multiple
1285 networks without having to modify browser configurations.
1289 Also specified here are SOCKS proxies. <application>Junkbuster</application>
1290 SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
1291 hostname using DNS on the SOCKS server, not our local DNS client.
1295 The syntax of each line is:
1302 <emphasis>forward target_domain[:port] http_proxy_host[:port]</emphasis>
1303 <emphasis>forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1304 <emphasis>forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1311 If http_proxy_host is <quote>.</quote>, then requests are not forwarded to a
1312 HTTP proxy but are made directly to the web servers.
1316 Lines are checked in sequence, and the last match wins.
1320 There is an implicit line equivalent to the following, which specifies that
1321 anything not finding a match on the list is to go out without forwarding
1322 or gateway protocol, like so:
1329 <emphasis>forward .* . </emphasis># implicit
1336 In the following common configuration, everything goes to Lucent's LPWA,
1337 except SSL on port 443 (which it doesn't handle):
1344 <emphasis>forward .* lpwa.com:8000</emphasis>
1345 <emphasis>forward :443 .</emphasis>
1352 See the FAQ for instructions on how to automate the login procedure for LPWA.
1353 Some users have reported difficulties related to LPWA's use of
1354 <quote>.</quote> as the last element of the domain, and have said that this
1355 can be fixed with this:
1362 <emphasis>forward lpwa. lpwa.com:8000</emphasis>
1369 (NOTE: the syntax for specifiying target_domain has changed since the
1370 previous paragraph was written -- it will not work now. More information
1375 In this fictitious example, everything goes via an ISP's caching proxy,
1376 except requests to that ISP:
1383 <emphasis>forward .* caching.myisp.net:8000</emphasis>
1384 <emphasis>forward myisp.net .</emphasis>
1391 For the @home network, we're told the forwarding configuration is this:
1399 <emphasis>forward .* proxy:8080</emphasis>
1406 Also, we're told they insist on getting cookies and JavaScript, so you should
1407 add home.com to the cookie file. We consider JavaScript a security risk.
1408 Java need not be enabled.
1412 In this example direct connections are made to all <quote>internal</quote>
1413 domains, but everything else goes through Lucent's LPWA by way of the
1414 company's SOCKS gateway to the Internet.
1421 <emphasis>forward-socks4 .* lpwa.com:8000 firewall.my_company.com:1080</emphasis>
1422 <emphasis>forward my_company.com .</emphasis>
1429 This is how you could set up a site that always uses SOCKS but no forwarders:
1436 <emphasis>forward-socks4a .* . firewall.my_company.com:1080</emphasis>
1443 An advanced example for network administrators:
1447 If you have links to multiple ISPs that provide various special content to
1448 their subscribers, you can configure forwarding to pass requests to the
1449 specific host that's connected to that ISP so that everybody can see all
1450 of the content on all of the ISPs.
1454 This is a bit tricky, but here's an example:
1459 host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
1460 isp-b.com. host-a can run a <application>Junkbuster</application> proxy with
1461 forwarding like this:
1468 <emphasis>forward .* .</emphasis>
1469 <emphasis>forward isp-b.com host-b:8000</emphasis>
1476 host-b can run a <application>Junkbuster</application> proxy with forwarding
1484 <emphasis>forward .* .</emphasis>
1485 <emphasis>forward isp-a.com host-a:8000</emphasis>
1492 Now, <emphasis>anyone</emphasis> on the Internet (including users on host-a
1493 and host-b) can set their browser's proxy to <emphasis>either</emphasis>
1494 host-a or host-b and be able to browse the content on isp-a or isp-b.
1498 Here's another practical example, for University of Kent at
1499 Canterbury students with a network connection in their room, who
1500 need to use the University's Squid web cache.
1507 <emphasis>forward *. ssbcache.ukc.ac.uk:3128</emphasis> # Use the proxy, except for:
1508 <emphasis>forward .ukc.ac.uk . </emphasis> # Anything on the same domain as us
1509 <emphasis>forward * . </emphasis> # Host with no domain specified
1510 <emphasis>forward 129.12.*.* . </emphasis> # A dotted IP on our /16 network.
1511 <emphasis>forward 127.*.*.* . </emphasis> # Loopback address
1512 <emphasis>forward localhost.localdomain . </emphasis> # Loopback address
1513 <emphasis>forward www.ukc.mirror.ac.uk . </emphasis> # Specific host
1520 If you intend to chain <application>Junkbuster</application> and
1521 <application>squid</application> locally, then chain as
1522 <literal>browser -> squid -> junkbuster</literal> is the recommended way.
1526 Your squid configuration could then look like this:
1533 # Define junkbuster as parent cache
1534 <!-- per feedback from user...
1535 cache_peer 127.0.0.1 8000 parent 0 no-query
1537 cache_peer 127.0.0.1 parent 8000 0 no-query
1539 # Define ACL for protocol FTP
1542 # Do not forward ACL FTP to junkbuster
1543 always_direct allow FTP
1545 # Do not forward ACL CONNECT (https) to junkbuster
1546 always_direct allow CONNECT
1548 # Forward the rest to junkbuster
1549 never_direct allow all
1557 <!-- ~ End section ~ -->
1560 <!-- ~~~~~ New section ~~~~~ -->
1563 <title>Windows GUI Options</title>
1565 Removed references to Win32. HB 09/23/01
1568 <application>Junkbuster</application> has a number of options specific to the
1569 Windows GUI interface:
1573 If <quote>activity-animation</quote> is set to 1, the
1574 <application>Junkbuster</application> icon will animate when
1575 <quote>Junkbuster</quote> is active. To turn off, set to 0.
1582 <emphasis>activity-animation 1</emphasis>
1589 If <quote>log-messages</quote> is set to 1,
1590 <application>Junkbuster</application> will log messages to the console
1598 <emphasis>log-messages 1</emphasis>
1605 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
1606 i.e. the amount of memory used for the log messages displayed in the
1607 console window, will be limited to <quote>log-max-lines</quote> (see below).
1611 Warning: Setting this to 0 will result in the buffer to grow infinitely and
1612 eat up all your memory!
1619 <emphasis>log-buffer-size 1</emphasis>
1626 <application>log-max-lines</application> is the maximum number of lines held
1627 in the log buffer. See above.
1634 <emphasis>log-max-lines 200</emphasis>
1641 If <quote>log-highlight-messages</quote> is set to 1,
1642 <application>Junkbuster</application> will highlight portions of the log
1643 messages with a bold-faced font:
1650 <emphasis>log-highlight-messages 1</emphasis>
1657 The font used in the console window:
1664 <emphasis>log-font-name Comic Sans MS</emphasis>
1671 Font size used in the console window:
1678 <emphasis>log-font-size 8</emphasis>
1685 <quote>show-on-task-bar</quote> controls whether or not
1686 <application>Junkbuster</application> will appear as a button on the Task bar
1694 <emphasis>show-on-task-bar 0</emphasis>
1701 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
1702 button will minimize <application>Junkbuster</application> instead of closing
1703 the program (close with the exit option on the File menu).
1710 <emphasis>close-button-minimizes 1</emphasis>
1717 The <quote>hide-console</quote> option is specific to the MS-Win console
1718 version of <application>JunkBuster</application>. If this option is used,
1719 <application>Junkbuster</application> will disconnect from and hide the
1736 <!-- ~ End section ~ -->
1739 <!-- ~~~~~ New section ~~~~~ -->
1740 <sect2 id="actionsfile">
1741 <title>The Actions File</title>
1744 The <quote>ijb.action</quote> file (formerly
1745 <filename>actionsfile</filename>) is used to define what actions
1746 <application>Junkbuster</application> takes, and thus determines how images,
1747 cookies and various other aspects of HTTP content and transactions are
1748 handled. Images can be anything you want, including ads, banners, or just
1749 some obnoxious image that you would rather not see. Cookies can be accepted
1750 or rejected, or accepted only during the current browser session (i.e.
1751 not written to disk). Changes to <filename>ijb.action</filename> should
1752 be immediately visible to <application>Junkbuster</application> without
1753 the need to restart.
1757 To determine which actions apply to a request, the URL of the request is
1758 compared to all patterns in this file. Every time it matches, the list of
1759 applicable actions for the URL is incrementally updated. You can trace
1760 this process by visiting <ulink
1761 url="http://i.j.b/show-url-info">http://i.j.b/show-url-info</ulink>.
1765 The actions file can be edited with a browser by loading
1766 <ulink url="http://i.j.b/">http://i.j.b/</ulink>, and then select
1767 <quote>Edit Actions</quote>.
1771 There are four types of lines in this file: comments (begin with a
1772 <quote>#</quote> character), actions, aliases and patterns, all of which are
1773 explained below, as well as the configuration file syntax that
1774 <application>Junkbuster</application> understands.
1779 <!-- ~~~~~ New section ~~~~~ -->
1781 <title>URL Domain and Path Syntax</title>
1783 Generally, a pattern has the form <domain>/<path>, where both the
1784 <domain> and <path> part are optional. If you only specify a
1785 domain part, the <quote>/</quote> can be left out:
1789 <emphasis>www.example.com</emphasis> - is a domain only pattern and will match any request to
1790 <quote>www.example.com</quote>.
1794 <emphasis>www.example.com/</emphasis> - means exactly the same.
1798 <emphasis>www.example.com/index.html</emphasis> - matches only the single
1799 document <quote>/index.html</quote> on <quote>www.example.com</quote>.
1803 <emphasis>/index.html</emphasis> - matches the document <quote>/index.html</quote>, regardless of
1808 <emphasis>index.html</emphasis> - matches nothing, since it would be
1809 interpreted as a domain name and there is no top-level domain called
1810 <quote>.html</quote>.
1814 The matching of the domain part offers some flexible options: if the
1815 domain starts or ends with a dot, it becomes unanchored at that end.
1820 <emphasis>.example.com</emphasis> - matches any domain that <emphasis>ENDS</emphasis> in
1821 <quote>.example.com</quote>.
1825 <emphasis>www.</emphasis> - matches any domain that <emphasis>STARTS</emphasis> with
1830 Additionally, there are wildcards that you can use in the domain names
1831 themselves. They work pretty similar to shell wildcards: <quote>*</quote>
1832 stands for zero or more arbitrary characters, <quote>?</quote> stands for
1833 any single character. And you can define charachter classes in square
1834 brackets and they can be freely mixed:
1838 <emphasis>ad*.example.com</emphasis> - matches <quote>adserver.example.com</quote>,
1839 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>.
1843 <emphasis>*ad*.example.com</emphasis> - matches all of the above, and then some.
1847 <emphasis>.?pix.com</emphasis> - matches <quote>www.ipix.com</quote>,
1848 <quote>pictures.epix.com</quote>, <quote>a.b.c.d.e.upix.com</quote>, etc.
1852 <emphasis>www[1-9a-ez].example.com</emphasis> - matches <quote>www1.example.com</quote>,
1853 <quote>www4.example.com</quote>, <quote>wwwd.example.com</quote>,
1854 <quote>wwwz.example.com</quote>, etc., but <emphasis>not</emphasis>
1855 <quote>wwww.example.com</quote>.
1859 If <application>Junkbuster</application> was compiled with
1860 <quote>pcre</quote> support (default), Perl compatible regular expressions
1861 can be used. See the <filename>pcre/docs/</filename> direcory or <quote>man
1862 perlre</quote> (also available on <ulink
1863 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>)
1864 for details. A brief discussion of regular expressions is in the
1865 <link linkend="regex">Appendix</link>. For instance:
1869 <emphasis>/.*/advert[0-9]+\.jpe?g</emphasis> - would match a URL from any
1870 domain, with any path that includes <quote>advert</quote> followed
1871 immediately by one or more digits, then a <quote>.</quote> and ending in
1872 either <quote>jpeg</quote> or <quote>jpg</quote>. So we match
1873 <quote>example.com/ads/advert2.jpg</quote>, and
1874 <quote>www.example.com/ads/banners/advert39.jpeg</quote>, but not
1875 <quote>www.example.com/ads/banners/advert39.gif</quote> (no gifs in the
1880 Please note that matching in the path is case
1881 <emphasis>INSENSITIVE</emphasis> by default, but you can switch to case
1882 sensitive at any point in the pattern by using the
1883 <quote>(?-i)</quote> switch:
1887 <emphasis>www.example.com/(?-i)PaTtErN.*</emphasis> - will match only
1888 documents whose path starts with <quote>PaTtErN</quote> in
1889 <emphasis>exactly</emphasis> this capitalization.
1894 <!-- ~ End section ~ -->
1898 <!-- ~~~~~ New section ~~~~~ -->
1901 <title>Actions</title>
1903 Actions are enabled if preceded with a <quote>+</quote>, and disabled if
1904 preceded with a <quote>-</quote>. Actions are invoked by enclosing the
1905 action name in curly braces (e.g. {+some_action}), followed by a list of
1906 URLs to which the action applies. There are three classes of actions:
1914 Boolean (e.g. <quote>+/-block</quote>):
1920 <emphasis>{+name}</emphasis> # enable this action
1921 <emphasis>{-name}</emphasis> # disable this action
1931 parameterized (e.g. <quote>+/-hide-user-agent</quote>):
1937 <emphasis>{+name{param}}</emphasis> # enable action and set parameter to <quote>param</quote>
1938 <emphasis>{-name}</emphasis> # disable action
1947 Multi-value (e.g. <quote>{+/-add-header{Name: value}}</quote>, <quote>{+/-wafer{name=value}}</quote>):
1953 <emphasis>{+name{param}}</emphasis> # enable action and add parameter <quote>param</quote>
1954 <emphasis>{-name{param}}</emphasis> # remove the parameter <quote>param</quote>
1955 <emphasis>{-name}</emphasis> # disable this action totally
1966 If nothing is specified in this file, no <quote>actions</quote> are taken.
1967 So in this case <application>JunkBuster</application> would just be a
1968 normal, non-blocking, non-anonymizing proxy. You must specifically
1969 enable the privacy and blocking features you need (although the
1970 provided default <filename>ijb.action</filename> file will
1971 give a good starting point).
1975 Later defined actions always over-ride earlier ones. For multi-valued
1976 actions, the actions are applied in the order they are specified.
1980 The list of valid <application>Junkbuster</application> <quote>actions</quote> are:
1988 Add the specified HTTP header, which is not checked for validity.
1989 You may specify this many times to specify many different headers:
1995 <emphasis>+add-header{Name: value}</emphasis>
2005 Block this URL totally.
2011 <emphasis>+block</emphasis>
2021 De-animate all animated GIF images, i.e. reduce them to their last frame.
2022 This will also shrink the images considerably (in bytes, not pixels!). If
2023 the option <quote>first</quote> is given, the first frame of the animation
2024 is used as the replacement. If <quote>last</quote> is given, the last frame
2025 of the animation is used instead, which propably makes more sense for most
2026 banner animations, but also has the risk of not showing the entire last
2027 frame (if it is only a delta to an earlier frame).
2033 <emphasis>+deanimate-gifs{last}</emphasis>
2034 <emphasis>+deanimate-gifs{first}</emphasis>
2043 <quote>+downgrade</quote> will downgrade HTTP/1.1 client requests to
2044 HTTP/1.0 and downgrade the responses as well. Use this action for servers
2045 that use HTTP/1.1 protocol features that
2046 <application>Junkbuster</application> doesn't handle well yet. HTTP/1.1
2047 is only partially implemented. Default is not to downgrade requests.
2053 <emphasis>+downgrade</emphasis>
2062 Many sites, like yahoo.com, don't just link to other sites. Instead, they
2063 will link to some script on their own server, giving the destination as a
2064 parameter, which will then redirect you to the final target. URLs resulting
2065 from this scheme typically look like:
2066 http://some.place/some_script?http://some.where-else.
2069 Sometimes, there are even multiple consecutive redirects encoded in the
2070 URL. These redirections via scripts make your web browing more traceable,
2071 since the server from which you follow such a link can see where you go to.
2072 Apart from that, valuable bandwidth and time is wasted, while your browser
2073 ask the server for one redirect after the other. Plus, it feeds the
2077 The <quote>+fast-redirects</quote> option enables interception of these
2078 requests by <application>Junkbuster</application>, who will cut off all but
2079 the last valid URL in the request and send a local redirect back to your
2080 browser without contacting the remote site.
2086 <emphasis>+fast-redirects</emphasis>
2095 Filter the website through the re_filterfile:
2101 <emphasis>+filter{filename}</emphasis>
2110 Block any existing X-Forwarded-for header, and do not add a new one:
2116 <emphasis>+hide-forwarded</emphasis>
2125 If the browser sends a <quote>From:</quote> header containing your e-mail
2126 address, this either completely removes the header (<quote>block</quote>), or
2127 changes it to the specified e-mail address.
2133 <emphasis>+hide-from{block}</emphasis>
2134 <emphasis>+hide-from{spam@sittingduck.xqq}</emphasis>
2143 Don't send the <quote>Referer:</quote> (sic) header to the web site. You
2144 can block it, forge a URL to the same server as the request (which is
2145 preferred because some sites will not send images otherwise) or set it to a
2146 constant string of your choice.
2152 <emphasis>+hide-referer{block}</emphasis>
2153 <emphasis>+hide-referer{forge}</emphasis>
2154 <emphasis>+hide-referer{http://nowhere.com}</emphasis>
2163 Alternative spelling of <quote>+hide-referer</quote>. It has the same
2164 parameters, and can be freely mixed with, <quote>+hide-referer</quote>.
2165 (<quote>referrer</quote> is the correct English spelling, however the HTTP
2166 specification has a bug - it requires it to be spelled <quote>referer</quote>.)
2172 <emphasis>+hide-referrer{...}</emphasis>
2181 Change the <quote>User-Agent:</quote> header so web servers can't tell your
2182 browser type. Warning! This breaks many web sites. Specify the
2183 user-agent value you want. Example, pretend to be using Netscape on
2190 <emphasis>+hide-user-agent{Mozilla (X11; I; Linux 2.0.32 i586)}</emphasis>
2197 Or to identify yourself explicitly as a <quote>Junkbuster</quote> user:
2203 <emphasis>+hide-user-agent{JunkBuster/1.0}</emphasis>
2208 (Don't change the version number from 1.0 - after all, why tell them?)
2215 <emphasis>+hide-user-agent{browser-type}</emphasis>
2225 Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
2226 in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
2227 See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
2233 <emphasis>+image</emphasis>
2242 Decides what to do with URLs that end up tagged with <quote>{+block
2243 +image}</quote>. There are 4 options. <quote>-image-blocker</quote> will
2244 send a HTML <quote>blocked</quote> page, usually resulting in a
2245 <quote>broken image</quote> icon. <quote>+image-blocker{logo}</quote> will
2246 send a <quote>JunkBuster</quote> image.
2247 <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF image.
2248 And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a HTTP
2249 temporary redirect to the specified image. This has the advantage of the
2250 icon being being cached by the browser, which will speed up the display.
2256 <emphasis>+image-blocker{logo}</emphasis>
2257 <emphasis>+image-blocker{blank}</emphasis>
2258 <emphasis>+image-blocker{http://i.j.b/send-banner}</emphasis>
2267 By default (i.e. in the absence of a <quote>+limit-connect</quote>
2268 action), <application>Junkbuster</application> will only allow CONNECT
2269 requests to port 443, which is the standard port for https as a
2274 The CONNECT methods exists in HTTP to allow access to secure websites
2275 (https:// URLs) through proxies. It works very simply: the proxy
2276 connects to the server on the specified port, and then short-circuits
2277 its connections to the client <emphasis>and</emphasis> to the remote proxy.
2278 This can be a big security hole, since CONNECT-enabled proxies can
2279 be abused as TCP relays very easily.
2283 If you want to allow CONNECT for more ports than this, or want to forbid
2284 CONNECT altogether, you can specify a comma separated list of ports and
2285 port ranges (the latter using dashes, with the minimum defaulting to 0 and
2293 <emphasis>+limit-connect{443} # This is the default and need no be specified.</emphasis>
2294 <emphasis>+limit-connect{80,443} # Ports 80 and 443 are OK.</emphasis>
2295 <emphasis>+limit-connect{-3, 7, 20-100, 500-} # Port less than 3, 7, 20 to 100</emphasis>
2296 <emphasis> #and above 500 are OK.</emphasis>
2306 <quote>+no-compression</quote> prevents the website from compressing the
2307 data. Some websites do this, which can be a problem for
2308 <application>Junkbuster</application>, since <quote>+filter</quote>,
2309 <quote>+no-popup</quote> and <quote>+gif-deanimate</quote> will not work on
2310 compressed data. This will slow down connections to those websites,
2311 though. Default is <quote>nocompression</quote> is turned on.
2318 <emphasis>+nocompression</emphasis>
2327 If the website sets cookies, <quote>no-cookies-keep</quote> will make sure
2328 they are erased when you exit and restart your web browser. This makes
2329 profiling cookies useless, but won't break sites which require cookies so
2330 that you can log in for transactions. Default: on.
2336 <emphasis>+no-cookies-keep</emphasis>
2345 Prevent the website from reading cookies:
2351 <emphasis>+no-cookies-read</emphasis>
2360 Prevent the website from setting cookies:
2366 <emphasis>+no-cookies-set</emphasis>
2375 Filter the website through a built-in filter to disable those obnoxious
2376 JavaScript pop-up windows via window.open(), etc. The two alternative
2377 spellings are equivalent.
2383 <emphasis>+no-popup</emphasis>
2384 <emphasis>+no-popups</emphasis>
2393 This action only applies if you are using a <filename>jarfile</filename>
2394 for saving cookies. It sends a cookie to every site stating that you do not
2395 accept any copyright on cookies sent to you, and asking them not to track
2396 you. Of course, this is a (relatively) unique header they could use to
2403 <emphasis>+vanilla-wafer</emphasis>
2412 This allows you to add an arbitrary cookie. It can be specified multiple
2413 times in order to add as many cookies as you like.
2419 <emphasis>+wafer{name=value}</emphasis>
2430 The meaning of any of the above is reversed by preceding the action with a
2431 <quote>-</quote>, in place of the <quote>+</quote>.
2439 Turn off cookies by default, then allow a few through for specified sites:
2446 # Turn off all persistant cookies
2447 { +no-cookies-read }
2449 # Allow cookies for this browser session ONLY
2450 { +no-cookies-keep }
2452 # Execeptions to the above, sites that benefit from persistant cookies
2453 { -no-cookies-read }
2455 { -no-cookies-keep }
2462 # Alternative way of saying the same thing
2463 {-no-cookies-set -no-cookies-read -no-cookies-keep}
2472 Now turn off <quote>fast redirects</quote>, and then we allow two exceptions:
2482 # Reverse it for these two sites, which don't work right without it.
2484 www.ukc.ac.uk/cgi-bin/wac\.cgi\?
2492 Turn on page filtering, with one exception for sourceforge:
2499 # Run everything through the default filter file (<filename>re_filterfile</filename>):
2502 # But please don't re_filter code from sourceforge!
2504 .cvs.sourceforge.net
2511 Now some URLs that we want <quote>blocked</quote>, ie we won't see them.
2512 Many of these use regular expressions that will expand to match multiple
2522 /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g))
2523 /.*/(.*[-_.])?count(er)?(\.cgi|\.dll|\.exe|[?/])
2524 /.*/(ng)?adclient\.cgi
2525 /.*/(plain|live|rotate)[-_.]?ads?/
2526 /.*/(sponsor)s?[0-9]?/
2527 /.*/_?(plain|live)?ads?(-banners)?/
2529 /.*/ad(sdna_image|gifs?)/
2530 /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe)
2534 /.*/adv((er)?ts?|ertis(ing|ements?))?/
2538 /.*/cgi-bin/centralad/getimage
2539 /.*/images/addver\.gif
2540 /.*/images/marketing/.*\.(gif|jpe?g)
2544 /.*/sponsors?[0-9]?/
2545 /.*/advert[0-9]+\.jpg
2552 /graphics/defaultAd/
2554 /image\.ng/transactionID
2555 /images/.*/.*_anim\.gif # alvin brattli
2556 /ip_img/.*\.(gif|jpe?g)
2560 /cgi-bin/nph-adclick.exe/
2561 /.*/Image/BannerAdvertising/
2563 /.*/adlib/server\.cgi
2572 <!-- ~ End section ~ -->
2575 <!-- ~~~~~ New section ~~~~~ -->
2577 <title>Aliases</title>
2579 Custom <quote>actions</quote>, known to <application>Junkbuster</application>
2580 as <quote>aliases</quote>, can be defined by combining other <quote>actions</quote>.
2581 These can in turn be invoked just like the built-in <quote>actions</quote>.
2582 Currently, an alias can contain any character except space, tab, <quote>=</quote>,
2583 <quote>{</quote> or <quote>}</quote>. But please use only <quote>a</quote>-
2584 <quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
2585 <quote>-</quote>. Alias names are not case sensitive, and
2586 <emphasis>must be defined before anything</emphasis> else in the
2587 <filename>ijb.action</filename>file ! And there can only be one set of
2588 <quote>aliases</quote> defined.
2592 Now let's define a few aliases:
2599 # Useful customer aliases we can use later. These must come first!
2601 +no-cookies = +no-cookies-set +no-cookies-read
2602 -no-cookies = -no-cookies-set -no-cookies-read
2603 fragile = -block -no-cookies -filter -fast-redirects -hide-referer -no-popups
2604 shop = -no-cookies -filter -fast-redirects
2605 +imageblock = +block +image
2607 #For people who don't like to type too much: ;-)
2610 c2 = -no-cookies-set +no-cookies-read
2611 c3 = +no-cookies-set -no-cookies-read
2612 #... etc. Customize to your heart's content.
2619 Some examples using our <quote>shop</quote> and <quote>fragile</quote>
2627 # These sites are very complex and require
2628 # minimal interference.
2630 .office.microsoft.com
2631 .windowsupdate.microsoft.com
2634 # Shopping sites - still want to block ads.
2637 .worldpay.com # for quietpc.com
2641 # These shops require pop-ups
2653 <!-- ~ End section ~ -->
2656 <!-- ~~~~~ New section ~~~~~ -->
2657 <sect2 id="filterfile">
2658 <title>The Filter File</title>
2660 The filter file defines what filtering of web pages
2661 <application>Junkbuster</application> does. The default filter file is
2662 <filename>re_filterfile</filename>, located in the config directory. In this
2663 file, <emphasis>any document content</emphasis>, whether viewable text or
2664 embedded non-visible content, can be changed.
2668 This file uses regular expressions to alter or remove any string in the
2669 target page. Some examples from the included default <filename>re_filterfile</filename>:
2673 Stop web pages from displaying annoying messages in the status bar by
2674 deleting such references:
2681 # The status bar is for displaying link targets, not pointless buzzwords.
2682 # Again, check it out on http://www.airport-cgn.de/.
2683 s/status='.*?';*//ig
2690 Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
2691 <quote>MicroSuck</quote>:
2698 s/microsoft(?!.com)/MicroSuck/ig
2705 Kill those auto-refresh tags:
2712 # Kill refresh tags. I like to refresh myself. Manually.
2713 # check it out on http://www.airport-cgn.de/ and go to the arrivals page.
2715 s/<meta[^>]*http-equiv[^>]*refresh.*URL=([^>]*?)"?>/<link rev="x-refresh" href=$1>/i
2716 s/<meta[^>]*http-equiv="?page-enter"?[^>]*content=[^>]*>/<!--no page enter for me-->/i
2724 <!-- ~ End section ~ -->
2728 <!-- ~~~~~ New section ~~~~~ -->
2731 <title>Templates</title>
2733 When <application>Junkbuster</application> displays one of its internal
2734 pages, such as a 404 Not Found error page, it uses the appropriate template.
2735 On Linux, BSD, and Unix, these are locate in
2736 <filename>/etc/junkbuster/templates</filename> by default. These may be
2737 customized, if desired.
2744 <!-- ~ End section ~ -->
2748 <!-- ~~~~~ New section ~~~~~ -->
2749 <sect1 id="quickstart"><title>Quickstart to Using Junkbuster</title>
2751 Install package, then run and enjoy! <application>Junbuster</application>
2752 accepts only one command line option -- the configuration file to be
2753 used. Example Unix startup command:
2759 # /usr/sbin/junkbuster /etc/junkbuster/config
2765 An init script is provided for SuSE and Redhat.
2769 For for SuSE: /etc/rc.d/junkbuster start
2773 For RedHat: /etc/rc.d/init.d/junkbuster start
2778 If no configuration file is specified on the command line,
2779 <application>Junkbuster</application> will look for a file named
2780 <filename>config</filename> in the current directory. Except on Amiga where
2781 it will look for <filename>AmiTCP:db/junkbuster/config</filename> and Win32
2782 where it will try <filename>config.txt</filename>. If no file is specified
2783 on the command line and no default configuration file can be found,
2784 <application>Junkbuster</application> will fail to start.
2788 Be sure your browser is set to use the proxy which is by default at
2789 localhost, port 8000. With <application>Netscape</application> (and
2790 <application>Mozilla</application>), this can be set under <literal>Edit
2791 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</literal>.
2792 For <application>Internet Explorer</application>: <literal>Tools >
2793 Internet Properties -> Connections -> LAN Setting</literal>. Then,
2794 check <quote>Use Proxy</quote> and fill in the appropriate info (Address:
2795 localhost, Port: 8000). Include if HTTPS proxy support too.
2799 The included default configuration files should give a reasonable starting
2800 point, though may be somewhat aggressive in blocking junk. You will probably
2801 want to keep an eye out for sites that require persistant cookies, and add these to
2802 <filename>ijb.action</filename> as needed. By default, most of these will
2803 be accepted only during the current browser session, until you add them to
2804 the configuration. If you want the browser to handle this instead, you will
2805 need to edit <filename>ijb.action</filename> and disable this feature. If you
2806 use more than one browser, it would make more sense to let
2807 <application>Junkbuster</application> handle this. In which case, the
2808 browser(s) should be set to accept all cookies.
2812 If a particular site shows problems loading properly, try adding it
2813 to the <literal>{fragile}</literal> section of
2814 <filename>ijb.action</filename>. This will turn off most actions for
2819 HTTP/1.1 support is not fully implemented. If browsers that
2820 support HTTP/1.1 (like <application>Mozilla</application> or recent versions
2821 of I.E.) experience problems, you might try to force HTTP/1.0 compatiblity.
2822 For Mozilla, look under <literal>Edit -> Preferences -> Debug ->
2823 Networking</literal>. Or set the <quote>+downgrade</quote> config option in
2824 <filename>ijb.action</filename>.
2828 After running <application>Junkbuster</application> for a while, you can
2829 start to fine tune the configuration to suit your personal, or site,
2830 preferences and requirements. There are many, many aspects that can
2831 be customized. <quote>Actions</quote> (as specified in <filename>ijb.action</filename>)
2832 can be adjusted by pointing your browser to
2833 <ulink url="http://i.j.b/">http://i.j.b/</ulink>,
2834 and then follow the link to <quote>edit the actions list</quote>.
2835 (This is an internal page and does not require Internet access.)
2839 In fact, various aspects of <application>Junkbuster</application>
2840 configuration can be viewed from this page, including
2841 current configuration parameters, source code version numbers,
2842 the browser's request headers, and <quote>actions</quote> that apply
2843 to a given URL. In addition to the <filename>ijb.action</filename> file
2844 editor mentioned above, <application>Junkbuster</application> can also
2845 be turned <quote>on</quote> and <quote>off</quote> from this page.
2849 If you encounter problems, please verify it is a
2850 <application>Junkbuster</application> bug, by disabling
2851 <application>Junkbuster</application>, and then trying the same page.
2852 Also, try another browser if possible to eliminate browser or site
2853 problems. Before reporting it as a bug, see if there is not a configuration
2854 option that is enabled that is causing the page not to load. You can
2855 then add an exception for that page or site. If a bug, please report it to
2856 the developers (see below).
2862 <!-- ~~~~~ New section ~~~~~ -->
2863 <sect1 id="contact"><title>Contact the Developers</title>
2866 To be filled. mention the support forums as the primary channel of
2867 communication (bugs, feature requests, etc.)
2869 Feature requests and other questions should be posted to the <ulink
2870 url="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse">Feature
2871 request page</ulink> at SourceForge. There is also an archive there.
2875 Anyone interested in actively participating in development and related
2876 discussions can join the appropriate mailing list
2877 <ulink url="http://sourceforge.net/mail/?group_id=11118">here</ulink>.
2878 Archives are available here too.
2882 Please report bugs, using the form at
2883 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge</ulink>.
2884 Please try to verify that it is a <application>Junkbuster</application> bug,
2885 and not a browser or site bug first. Also, check to make sure this is not
2886 already a known bug.
2892 <!-- ~~~~~ New section ~~~~~ -->
2893 <sect1 id="copyright"><title>Copyright and History</title>
2896 <title>License</title>
2898 <application>Internet Junkbuster</application> is free software; you can
2899 redistribute it and/or modify it under the terms of the GNU General Public
2900 License as published by the Free Software Foundation; either version 2 of the
2901 License, or (at your option) any later version.
2905 This program is distributed in the hope that it will be useful, but WITHOUT
2906 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
2907 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
2908 details, which is available from <ulink
2909 url="http://www.gnu.org/copyleft/gpl.html">the Free Software Foundation,
2910 Inc</ulink>, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
2915 <!-- ~ End section ~ -->
2918 <!-- ~~~~~ New section ~~~~~ -->
2921 <title>History</title>
2923 <application>Junkbuster</application> was originally written by Anonymous
2925 url="http://www.junkbusters.com/ht/en/ijbfaq.html">JunkBusters
2926 Corporation</ulink>, and was released as free open-source software under the
2927 GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
2928 Waldherr</ulink> made many improvements, and started the <ulink
2929 url="http://sourceforge.net/projects/ijbswa/">SourceForge project</ulink> to
2930 rekindle development. The last stable release was v2.0.2, which has now
2938 <!-- ~~~~~ New section ~~~~~ -->
2939 <sect1 id="seealso"><title>See also</title>
2944 <ulink url="http://sourceforge.net/projects/ijbswa">http://sourceforge.net/projects/ijbswa</ulink>
2949 <ulink url="http://ijbswa.sourceforge.net/">http://ijbswa.sourceforge.net/</ulink>
2954 <ulink url="http://i.j.b/">http://i.j.b/</ulink>
2959 <ulink url="http://www.junkbusters.com/ht/en/cookies.html">http://www.junkbusters.com/ht/en/cookies.html</ulink>
2964 <ulink url="http://www.waldherr.org/junkbuster/">http://www.waldherr.org/junkbuster/</ulink>
2969 <ulink url="http://privacy.net/analyze/">http://privacy.net/analyze/</ulink>
2974 <ulink url="http://www.squid-cache.org/">http://www.squid-cache.org/</ulink>
2983 <!-- ~~~~~ New section ~~~~~ -->
2984 <sect1 id="appendix"><title>Appendix</title>
2987 <!-- ~~~~~ New section ~~~~~ -->
2989 <title>Regular Expressions</title>
2991 <application>Junkbuster</application> can use <quote>regular expressions</quote>
2992 in various config files. Assuming support for <quote>pcre</quote> (Perl
2993 Compatible Regular Expressions) is compiled in, which is the default. Such
2994 configuration directives do not require regular expressions, but they can be
2995 used to increase flexibility by matching a pattern with wildcards against
3000 If you are reading this, you probably don't understand what <quote>regular
3001 expressions</quote> are, or what they can do. So this will be a very brief
3002 introduction only. A full explanation would require a book ;-)
3006 <quote>Regular expressions</quote> is a way of matching one character
3007 expression against another to see if it matches or not. One of the
3008 <quote>expressions</quote> is a literal string of readable characters
3009 (letter, numbers, etc), and the other is a complex string of literal
3010 characters combined with wildcards, and other special characters, called
3011 metacharacters. The <quote>metacharacters</quote> have special meanings and
3012 are used to build the complex pattern to be matched against. Perl Compatible
3013 Regular Expressions is an enhanced form of the regular expression language
3014 with backward compatibility.
3018 To make a simple analogy, we do something similar when we use wildcard
3019 characters when listing files with the <command>dir</command> command in DOS.
3020 <literal>*.*</literal> matches all filenames. The <quote>special</quote>
3021 character here is the asterik which matches any and all characters. We can be
3022 more specific and use <literal>?</literal> to match just individual
3023 characters. So <quote>dir file?.text</quote> would match
3024 <quote>file1.txt</quote>, <quote>file2.txt</quote>, etc. We are pattern
3025 matching, using a similar technique to <quote>regular expressions</quote>!
3029 Regular expressions do essentially the same thing, but are much, much more
3030 powerful. There are many more <quote>special characters</quote> and ways of
3031 building complex patterns however. Let's look at a few of the common ones,
3032 and then some examples:
3037 <emphasis>.</emphasis> - Matches any single character, e.g. <quote>a</quote>,
3038 <quote>A</quote>, <quote>4</quote>, <quote>:</quote>, or <quote>@</quote>.
3044 <emphasis>?</emphasis> - The preceding character or expression is matched ZERO or ONE
3051 <emphasis>+</emphasis> - The preceding character or expression is matched ONE or MORE
3058 <emphasis>*</emphasis> - The preceding character or expression is matched ZERO or MORE
3065 <emphasis>\</emphasis> - The <quote>escape</quote> character denotes that
3066 the following character should be taken literally. This is used where one of the
3067 special characters (e.g. <quote>.</quote>) needs to be taken literally and
3068 not as a special metacharacter.
3074 <emphasis>[]</emphasis> - Characters enclosed in brackets will be matched if
3075 any of the enclosed characters are encountered.
3081 <emphasis>()</emphasis> - pararentheses are used to group a sub-expression,
3082 or multiple sub-expressions.
3088 <emphasis>|</emphasis> - The <quote>bar</quote> character works like an
3089 <quote>or</quote> conditional statement. A match is successful if the
3090 sub-expression on either side of <quote>|</quote> matches.
3096 <emphasis>s/string1/string2/g</emphasis> - This is used to rewrite strings of text.
3097 <quote>string1</quote> is replaced by <quote>string2</quote> in this
3103 These are just some of the ones you are likely to use when matching URLs with
3104 <application>Junkbuster</application>, and is a long way from a definitive
3105 list. This is enough to get us started with a few simple examples which may
3106 be more illuminating:
3110 <emphasis><literal>/.*/banners/.*</literal></emphasis> - A simple example
3111 that uses the common combination of <quote>.</quote> and <quote>*</quote> to
3112 denote any character, zero or more times. In other words, any string at all.
3113 So we start with a literal forward slash, then our regular expression pattern
3114 (<quote>.*</quote>) another literal forward slash, the string
3115 <quote>banners</quote>, another forward slash, and lastly another
3116 <quote>.*</quote>. We are building
3117 a directory path here. This will match any file with the path that has a
3118 directory named <quote>banners</quote> in it. The <quote>.*</quote> matches
3119 any characters, and this could conceivably be more forward slashes, so it
3120 might expand into a much longer looking path. For example, this could match:
3121 <quote>/eye/hate/spammers/banners/annoy_me_please.gif</quote>, or just
3122 <quote>/banners/annoying.html</quote>, or almost an infinite number of other
3123 possible combinations, just so it has <quote>banners</quote> in the path
3128 A now something a little more complex:
3132 <emphasis><literal>/.*/adv((er)?ts?|ertis(ing|ements?))?/</literal></emphasis> -
3133 We have several literal forward slashes again (<quote>/</quote>), so we are
3134 building another expression that is a file path statement. We have another
3135 <quote>.*</quote>, so we are matching against any conceivable sub-path, just so
3136 it matches our expression. The only true literal that <emphasis>must
3137 match</emphasis> our pattern is <application>adv</application>, together with
3138 the forward slashes. What comes after the <quote>adv</quote> string is the
3143 Remember the <quote>?</quote> means the preceding expression (either a
3144 literal character or anything grouped with <quote>(...)</quote> in this case)
3145 can exist or not, since this means either zero or one match. So
3146 <quote>((er)?ts?|ertis(ing|ements?))</quote> is optional, as are the
3147 individual sub-expressions: <quote>(er)</quote>,
3148 <quote>(ing|ements?)</quote>, and the <quote>s</quote>. The <quote>|</quote>
3149 means <quote>or</quote>. We have two of those. For instance,
3150 <quote>(ing|ements?)</quote>, can expand to match either <quote>ing</quote>
3151 <emphasis>OR</emphasis> <quote>ements?</quote>. What is being done here, is an
3152 attempt at matching as many variations of <quote>advertisement</quote>, and
3153 similar, as possible. So this would expand to match just <quote>adv</quote>,
3154 or <quote>advert</quote>, or <quote>adverts</quote>, or
3155 <quote>advertising</quote>, or <quote>advertisement</quote>, or
3156 <quote>advertisements</quote>. You get the idea. But it would not match
3157 <quote>advertizements</quote> (with a <quote>z</quote>). We could fix that by
3158 changing our regular expression to:
3159 <quote>/.*/adv((er)?ts?|erti(s|z)(ing|ements?))?/</quote>, which would then match
3164 <emphasis><literal>/.*/advert[0-9]+\.(gif|jpe?g)</literal></emphasis> - Again
3165 another path statement with forward slashes. Anything in the square brackets
3166 <quote>[]</quote> can be matched. This is using <quote>0-9</quote> as a
3167 shorthand expression to mean any digit one through nine. It is the same as
3168 saying <quote>0123456789</quote>. So any digit matches. The <quote>+</quote>
3169 means one or more of the preceding expression must be included. The preceding
3170 expression here is what is in the square brackets -- in this case, any digit
3171 one through nine. Then, at the end, we have a grouping: <quote>(gif|jpe?g)</quote>.
3172 This includes a <quote>|</quote>, so this needs to match the expression on
3173 either side of that bar character also. A simple <quote>gif</quote> on one side, and the other
3174 side will in turn match either <quote>jpeg</quote> or <quote>jpg</quote>,
3175 since the <quote>?</quote> means the letter <quote>e</quote> is optional and
3176 can be matched once or not at all. So we are building an expression here to
3177 match image GIF or JPEG type image file. It must include the literal
3178 string <quote>advert</quote>, then one or more digits, and a <quote>.</quote>
3179 (which is now a literal, and not a special character, since it is escaped
3180 with <quote>\</quote>), and lastly either <quote>gif</quote>, or
3181 <quote>jpeg</quote>, or <quote>jpg</quote>. Some possible matches would
3182 include: <quote>//advert1.jpg</quote>,
3183 <quote>/nasty/ads/advert1234.gif</quote>,
3184 <quote>/banners/from/hell/advert99.jpg</quote>. It would not match
3185 <quote>advert1.gif</quote> (no leading slash), or
3186 <quote>/adverts232.jpg</quote> (the expression does not include an
3187 <quote>s</quote>), or <quote>/advert1.jsp</quote> (<quote>jsp</quote> is not
3188 in the expression anywhere).
3192 <emphasis><literal>s/microsoft(?!.com)/MicroSuck/i</literal></emphasis> - This is
3193 a substitution. <quote>MicroSuck</quote> will replace any occurence of
3194 <quote>microsoft</quote>. The <quote>i</quote> at the end of the expression
3195 means ignore case. The <quote>(?!.com)</quote> means
3196 the match should fail if <quote>microsoft</quote> is followed by
3197 <quote>.com</quote>. In other words, this acts like a <quote>NOT</quote>
3198 modifier. In case this is a hyperlink, we don't want to break it ;-).
3202 We are barely scratching the surface of regular expressions here so that you
3203 can understand the default <application>Junkbuster</application>
3204 configuration files, and maybe use this knowledge to customize your own
3205 installation. There is much, much more that can be done with regular
3206 expressions. Now that you know enough to get started, you can learn more on
3211 More reading on Perl Compatible Regular expressions:
3212 <ulink url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>
3221 This program is free software; you can redistribute it
3222 and/or modify it under the terms of the GNU General
3223 Public License as published by the Free Software
3224 Foundation; either version 2 of the License, or (at
3225 your option) any later version.
3227 This program is distributed in the hope that it will
3228 be useful, but WITHOUT ANY WARRANTY; without even the
3229 implied warranty of MERCHANTABILITY or FITNESS FOR A
3230 PARTICULAR PURPOSE. See the GNU General Public
3231 License for more details.
3233 The GNU General Public License should be included with
3234 this file. If not, you can view it at
3235 http://www.gnu.org/copyleft/gpl.html
3236 or write to the Free Software Foundation, Inc., 59
3237 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
3239 $Log: user-manual.sgml,v $
3240 Revision 1.27 2002/01/11 14:14:32 hal9
3241 Added a very short section on Templates
3243 Revision 1.26 2002/01/09 20:02:50 hal9
3244 Fix bug re: auto-detect config file changes.
3246 Revision 1.25 2002/01/09 18:20:30 hal9
3247 Touch ups for *.action files.
3249 Revision 1.24 2001/12/02 01:13:42 hal9
3252 Revision 1.23 2001/12/02 00:20:41 hal9
3253 Updates for recent changes.
3255 Revision 1.22 2001/11/05 23:57:51 hal9
3256 Minor update for startup now daemon mode.
3258 Revision 1.21 2001/10/31 21:11:03 hal9
3259 Correct 2 minor errors
3261 Revision 1.18 2001/10/24 18:45:26 hal9
3262 *** empty log message ***
3264 Revision 1.17 2001/10/24 17:10:55 hal9
3265 Catching up with Jon's recent work, and a few other things.
3267 Revision 1.16 2001/10/21 17:19:21 swa
3268 wrong url in documentation
3270 Revision 1.15 2001/10/14 23:46:24 hal9
3271 Various minor changes. Fleshed out SEE ALSO section.
3273 Revision 1.13 2001/10/10 17:28:33 hal9
3276 Revision 1.12 2001/09/28 02:57:04 hal9
3279 Revision 1.11 2001/09/28 02:25:20 hal9
3282 Revision 1.9 2001/09/27 23:50:29 hal9
3283 A few changes. A short section on regular expression in appendix.
3285 Revision 1.8 2001/09/25 00:34:59 hal9
3286 Some additions, and re-arranging.
3288 Revision 1.7 2001/09/24 14:31:36 hal9
3291 Revision 1.6 2001/09/24 14:10:32 hal9
3292 Including David's OS/2 installation instructions.
3294 Revision 1.2 2001/09/13 15:27:40 swa
3297 Revision 1.1 2001/09/12 15:36:41 swa
3298 source files for junkbuster documentation
3300 Revision 1.3 2001/09/10 17:43:59 swa
3301 first proposal of a structure.
3303 Revision 1.2 2001/06/13 14:28:31 swa
3304 docs should have an author.
3306 Revision 1.1 2001/06/13 14:20:37 swa
3307 first import of project's documentation for the webserver.