1 <!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
3 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
4 File : $Source: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v $
8 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
10 $Id: user-manual.sgml,v 1.2 2001/09/13 15:27:40 swa Exp $
12 Written by and Copyright (C) 2001 the SourceForge
13 IJBSWA team. http://ijbswa.sourceforge.net
15 Based on the Internet Junkbuster originally written
16 by and Copyright (C) 1997 Anonymous Coders and
17 Junkbusters Corporation. http://www.junkbusters.com
21 Sun 09/23/01 08:53:31 PM
23 This is an unfinished, rough draft. Anyone reading this, believe let me
24 know errors!!!!! Stefan, especially you!
26 Hal Burgiss <hal@foobox.net>
31 <title>Junkbuster User Manual</title>
33 <pubdate>$Id: user-manual.sgml,v 1.2 2001/09/13 15:27:40 swa Exp $</pubdate>
38 <orgname>By: Junkbuster Developers</orgname>
45 The user manual gives the users information on how to install and configure
46 <application>Internet Junkbuster</application>. <application>Internet
47 Junkbuster</application> is an application that provides privacy and
48 security to users of the World Wide Web.
51 You can find the latest version of the user manual at <ulink url="http://ijbswa.sourceforge.net/doc/user-manual/">http://ijbswa.sourceforge.net/doc/user-manual/</ulink>.
55 Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>.
62 <!-- ~~~~~ New section ~~~~~ -->
64 <sect1 id="introduction"><title>Introduction</title>
66 <application>Internet Junkbuster</application> is a web proxy with advanced
67 filtering capabilities for protecting privacy, filtering web page content,
68 managing cookies and removing ads, banners, pop-ups and other obnoxious
69 Internet Junk. <application>Junkbuster</application> has a very flexible
70 configuration and can be customized to suit individual needs and tastes.
71 <application>Internet Junkbuster</application> has application for both
72 stand-alone systems and multi-user networks.
76 This documentation is included with the current development version of
77 <application>Internet Junkbuster</application> and is incomplete at this
78 point. The most up to date reference for the time being is still the comments
79 in the source files and in the individual configuration files. Development
80 of version 3.0 is currently underway, and includes significant changes and
81 enhancements over earlier verions.
85 Since this is a development version, there <emphasis>are</emphasis> bugs!
88 <!-- ~~~~~ New section ~~~~~ -->
91 <title>License</title>
93 <application>Internet Junkbuster</application> is free software; you can
94 redistribute it and/or modify it under the terms of the GNU General Public
95 License as published by the Free Software Foundation; either version 2 of the
96 License, or (at your option) any later version.
100 This program is distributed in the hope that it will be useful, but WITHOUT
101 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
102 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
103 details, which is available from <ulink
104 url="http://www.gnu.org/copyleft/gpl.html">the Free Software Foundation,
105 Inc</ulink>, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
110 <!-- ~ End section ~ -->
113 <!-- ~~~~~ New section ~~~~~ -->
116 <title>History</title>
118 <application>Junkbuster</application> was originally written by <ulink
119 url="http://www.junkbusters.com/ht/en/ijbfaq.html">JunkBusters
120 Corporation</ulink>, and was released as free open-source software under the
121 GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
122 Waldherr</ulink> made many improvements, and started the <ulink
123 url="http://sourceforge.net/projects/ijbswa/">SourceForge project</ulink> to
124 rekindle development.
131 <!-- ~ End section ~ -->
134 <!-- ~~~~~ New section ~~~~~ -->
135 <sect1 id="installation"><title>Installation</title>
137 <application>Junkbuster</application> is available as raw source code, or
138 pre-compiled binaries. See the <ulink
139 url="http://sourceforge.net/projects/ijbswa/">Junkbuster Home Page</ulink>
140 for current releases. <application>Junkbuster</application> is also available
142 url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
143 This is the recommended approach at this time.
146 <!-- ~~~~~ New section ~~~~~ -->
147 <sect2 id="installation-source"><title>Source</title>
149 For gzipped tar archives, unpack the source:
154 tar zxvf ijb_source_2.9*
160 For retrieving the current CVS sources, you'll need the CVS
161 package installed first. To download CVS source:
166 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
167 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
173 This will create a directory named <filename>current/</filename>, which will
174 contain the source tree.
178 Then, in either case, to build from source:
191 For Redhat and SuSE Linux RPM packages, see below.
197 <!-- ~~~~~ New section ~~~~~ -->
198 <sect2 id="installation-rh"><title>Red Hat</title>
200 To build Redhat RPM packages, install source as above. Then:
211 This will create both binary and src RPMs in the usual places. Example:
215 /usr/src/redhat/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
218 /usr/src/redhat/SRPMS/junkbuster-2.9.8-1.src.rpm
222 To install, of course:
227 rpm -Uvv /usr/src/redhat/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
232 This will place the <application>Junkbuster</application> configuration
233 files in <filename>/etc/junkbuster/</filename>, and log files in
234 <filename>/var/log/junkbuster/</filename>.
239 <!-- ~~~~~ New section ~~~~~ -->
240 <sect2 id="installation-suse"><title>SuSE</title>
242 To build SuSE RPM packages, install source as above. Then:
253 This will create both binary and src RPMs in the usual places. Example:
257 /usr/src/suse/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
260 /usr/src/suse/SRPMS/junkbuster-2.9.8-1.src.rpm
264 To install, of course:
269 rpm -Uvv /usr/src/suse/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
274 This will place the <application>Junkbuster</application> configuration
275 files in <filename>/etc/junkbuster/</filename>, and log files in
276 <filename>/var/log/junkbuster/</filename>.
282 <!-- ~~~~~ New section ~~~~~ -->
283 <sect2 id="installation-win"><title>Windows</title>
284 <para>I need help on this. Not a clue here. Also for
285 configuration section below.
289 <!-- ~~~~~ New section ~~~~~ -->
290 <sect2 id="installation-other"><title>Other</title>
291 <para>I need help on this too. OS/2? What others?
297 <!-- ~ End section ~ -->
300 <!-- ~~~~~ New section ~~~~~ -->
301 <sect1 id="configuration"><title>Junkbuster Configuration</title>
303 For Unix and Linux, all configuraton files are located in
304 <filename>/etc/junkbuster/</filename> by default. For MS Windows, these
305 are all in the same directory as the <application>Junkbuster</application>
306 executable. The name and number of configuration files has changed from
307 previous versions, and is subject to change as development progresses.
311 The installed defaults provide a reasonable starting point. For the
312 time being, there are only three default configuration files (this will
321 The main configuration file is named <filename>config</filename>
322 on Linux and Unix, and <filename>junkbustr.txt</filename> on Windows.
328 The <filename>actionsfile</filename> file is used to define various
329 actions relating to images, banners, pop-ups, banners and cookies.
335 The <filename>re_filterfile</filename> file can be used to rewrite the raw
336 page content, including text as well as embedded HTML and JavaScript.
344 <filename>actionsfile</filename> and <filename>re_filterfile</filename>
345 can use Perl style regular expressions for maximum flexibility. All files use
346 the <quote><literal>#</literal></quote> character to denote a comment. Such
347 lines are not processed by <application>Junkbuster</application>. After
348 making any changes, restart <application>Junkbuster</application> in order
349 for the changes to take effect.
353 <!-- ~~~~~ New section ~~~~~ -->
356 <title>The Main Configuration File</title>
358 Again, the main configuration file is named <filename>config</filename> on
359 Linux and Unix, and <filename>junkbustr.txt</filename> on Windows.
360 Configuration lines consist of an initial keyword followed by a list of
361 values, all separated by whitespace (any number of spaces or tabs). For
369 <emphasis>blockfile blocklist.ini</emphasis>
376 Indicates that the blockfile is named <quote>blocklist.ini</quote>.
380 The <quote><literal>#</literal></quote> indicates a comment. Any part of a
381 line following a <quote><literal>#</literal></quote> is ignored, except if
382 the <quote><literal>#</literal></quote> is preceded by a
383 <quote><literal>\</literal></quote>.
387 Thus, by placing a <quote><literal>#</literal></quote> at the start of an
388 existing configuration line, you can make it a comment and it will be treated
389 as if it weren't there. This is called <quote>commenting out</quote> an
390 option and can be useful to turn off features: If you comment out the
391 <quote>logfile</quote> line, <application>junkbuster</application> will not
392 log to a file at all. Watch for the <quote>default:</quote> section in each
393 explanation to see what happens if the option is left unset (or commented
398 Long lines can be continued on the next line by using a
399 <quote><literal>\</literal></quote> as the very last character.
403 There are various aspects of <application>Junkbuster</application> behavior
404 that can be adjusted.
408 <!-- ~~~~~ New section ~~~~~ -->
411 <title>Defining Other Configuration Files</title>
414 <application>Junkbuster</application> can use a number of other files to tell it
415 what ads to block, what cookies to accept, etc. This section of the
416 configuration file tells <application>Junkbuster</application> where to find
417 all those other files.
421 On <application>Windows</application>, <application>Junkbuster</application>
422 looks for these files in the same directory as the executable. On Unix,
423 <application>Junkbuster</application> looks for these files in the current
424 working directory. In either case, an absolute path name can be used to
429 When development goes modular and multiuser, the blocker, filter, and
430 per-user config will be stored in subdirectories of <quote>confdir</quote>.
431 For now, only <filename>confdir/templates</filename> is used for storing HTML
432 templates for CGI results.
436 The location of the configuration files:
443 <emphasis>confdir /etc/junkbuster</emphasis> # No trailing /, please.
450 The directory where all logging (i.e. <filename>logfile</filename> and
451 <filename>jarfile</filename>) takes place. No trailing
452 <quote><literal>/</literal></quote>, please:
459 <emphasis>logdir /var/log/junkbuster</emphasis>
466 Note that all file specifications below are relative to
467 the above two directories!
471 The <quote>actionsfile</quote> contains patterns to specify the actions to
472 apply to requests for each site. Default: Cookies to and from all
473 destinations are filtered. Popups are disabled for all sites. All sites are
474 filtered if re_filterfile specified. No sites are blocked. An empty image is
475 displayed for filtered ads and other images (formerly
476 <quote>tinygif</quote>). The syntax of this file is explained in detail
477 <link linkend="actionsfile">below</link>.
484 <emphasis>actionsfile actionsfile</emphasis>
491 The <quote>re_filterfile</quote> file contains content modification rules.
492 These rules permit powerful changes on the content of Web pages, e.g., you
493 could disable your favourite JavaScript annoyances, rewrite the actual
494 content, or just have some fun replacing <quote>Microsoft</quote> with
495 <quote>MicroSuck</quote> wherever it appears on a Web page. Default: No
496 content modification, or whatever the developers are playing with :-/
503 <emphasis>re_filterfile re_filterfile</emphasis>
510 The logfile is where all logging and error messages are written. The logfile
511 can be useful for tracking down a problem with
512 <application>Junkbuster</application> (e.g., it's not blocking an ad you
513 think it should block) but in most cases you probably will never look at it.
517 Your logfile will grow indefinitely, and you will probably want to
518 periodically remove it. On Unix systems, you can do this with a cron job
519 (see <quote>man cron</quote>). For Redhat, a <command>logrotate</command>
520 script has been included.
524 On SuSE Linux systems, you can place a line like <quote>/var/log/junkbuster.*
525 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
526 the effect that cron.daily will automatically archive, gzip, and empty the
527 log, when it exceeds 1M size.
531 Default: Log to the a file named <filename>logfile</filename>.
532 Comment out to disable logging.
539 <emphasis>logfile logfile</emphasis>
546 The <quote>jarfile</quote> defines where
547 <application>Junkbuster</application> stores the cookies it intercepts. Note
548 that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
549 Don't store intercepted cookies.
556 <emphasis>#jarfile jarfile</emphasis>
563 If you specify a <quote>trustfile</quote>,
564 <application>Junkbuster</application> will only allow access to sites that
565 are named in the trustfile. You can also mark sites as trusted referrers,
566 with the effect that access to untrusted sites will be granted, if a link
567 from a trusted referrer was used. The link target will then be added to the
568 <quote>trustfile</quote>. This is a very restrictive feature that typical
569 users most propably want to leave disabled. Default: Disabled, don't use the
577 <emphasis>#trustfile trust</emphasis>
584 If you use the trust mechanism, it is a good idea to write up some online
585 documentation about your blocking policy and to specify the URL(s) here. They
586 will appear on the page that your users receive when they try to access
587 untrusted content. Use multiple times for multiple URLs. Default: Don't
588 display links on the <quote>untrusted</quote> info page.
595 <emphasis>trust-info-url http://www.your-site.com/why_we_block.html</emphasis>
596 <emphasis>trust-info-url http://www.your-site.com/what_we_allow.html</emphasis>
604 <!-- ~ End section ~ -->
608 <!-- ~~~~~ New section ~~~~~ -->
611 <title>Other Configuration Options</title>
614 This part of the configuration file contains options that control how
615 <application>Junkbuster</application> operates.
619 <quote>Admin-address</quote> should be set to the email address of the proxy
620 administrator. It is used in many of the proxy-generated pages. Default:
628 <emphasis>#admin-address fill@me.in.please</emphasis>
635 <quote>Proxy-info-url</quote> can be set to a URL that contains more info
636 about this <application>Junkbuster</application> installation, it's
637 configuration and policies. It is used in many of the proxy-generated pages
638 and its use is highly recommended in multi-user installations, since your
639 users will want to know why certain content is blocked or modified. Default:
640 Don't show a link to online documentation.
647 <emphasis>proxy-info-url http://www.your-site.com/proxy.html</emphasis>
654 <quote>Listen-address</quote> specifies the address and port where
655 <application>Junkbuster</application> will listen for connections from your
656 Web browser. The default is to listen on the localhost port 8000, and
657 this is suitable for most users. (In your web browser, under proxy
658 configuration, list the proxy server as <quote>localhost</quote> and the
659 port as <quote>8000</quote>).
663 If you already have another service running on port 8000, or if you want to
664 serve requests from other machines (e.g. on your local network) as well, you
665 will need to override the default. The syntax is
666 <quote>listen-address [<ip-address>]:<port></quote>. If you leave
667 out the IP adress, <application>junkbuster</application> will bind to all
668 interfaces (addresses) on your machine and may become reachable from the
669 internet. In that case, consider using access control lists (acl's) (see
670 <quote>aclfile</quote> above).
674 For example, suppose you are running <application>Junkbuster</application> on
675 a machine which has the address 192.168.0.1 on your local private network
676 (192.168.0.0) and has another outside connection with a different address.
677 You want it to serve requests from inside only:
684 <emphasis>listen-address 192.168.0.1:8000</emphasis>
691 If you want it to listen on all addresses (including the outside
699 <emphasis>listen-address :8000</emphasis>
706 If you do this, consider using ACLs (see <quote>aclfile</quote> above). Note:
707 you will need to point your browser(s) to the address and port that you have
708 configured here. Default: localhost:8000 (127.0.0.1:8000).
712 The debug option sets the level of debugging information to log in the
713 logfile (and to the console in the Windows version). A debug level of 1 is
714 informative because it will show you each request as it happens. Higher
715 levels of debug are probably only of interest to developers.
722 debug 1 # GPC = show each GET/POST/CONNECT request
723 debug 2 # CONN = show each connection status
724 debug 4 # IO = show I/O status
725 debug 8 # HDR = show header parsing
726 debug 16 # LOG = log all data into the logfile
727 debug 32 # FRC = debug force feature
728 debug 64 # REF = debug regular expression filter
729 debug 128 # = debug fast redirects
730 debug 256 # = debug GIF deanimation
731 debug 512 # CLF = Common Log Format
732 debug 1024 # = debug kill popups
733 debug 4096 # INFO = Startup banner and warnings.
734 debug 8192 # ERROR = Non-fatal errors
741 It is <emphasis>highly recommended</emphasis> that you enable ERROR
742 reporting (debug 8192), at least until the next stable release.
746 The reporting of FATAL errors (i.e. ones which crash
747 <application>JunkBuster</application>) is always on and cannot be disabled.
751 If you want to use CLF (Common Log Format), you should set <quote>debug
752 512</quote> ONLY, do not enable anything else.
756 Multiple <quote>debug</quote> directives, are OK - they're logical-OR'd
764 <emphasis>debug 15 # same as setting the first 4 listed above</emphasis>
778 <emphasis>debug 1 # URLs</emphasis>
779 <emphasis>debug 4096 # Info</emphasis>
780 <emphasis>debug 8192 # Errors - *we highly recommended enabling this*</emphasis>
787 <application>Junkbuster</application> normally uses
788 <quote>multi-threading</quote>, a software technique that permits it to
789 handle many different requests simultaneously. In some cases you may wish to
790 disable this -- particularly if you're trying to debug a problem. The
791 <quote>single-threaded</quote> option forces
792 <application>Junkbuster</application> to handle requests sequentially.
793 Default: Multi-threaded mode.
800 <emphasis>#single-threaded</emphasis>
807 <quote>toggle</quote> allows you to temporarily disable all
808 <application>Junkbuster's</application> filtering. Just set <quote>toggle
813 The Windows version of <application>Junkbuster</application> puts an icon in
814 the system tray, which allows you to change this option without having to
815 edit this file. If you right-click on that icon (or select the
816 <quote>Options</quote> menu), one choice is <quote>Enable</quote>. Clicking
817 on enable toggles <application>Junkbuster</application> on and off. This is
818 useful if you want to temporarily disable
819 <application>Junkbuster</application>, e.g., to access a site that requires
820 cookies which you normally have blocked.
824 <quote>toggle 1</quote> means <application>Junkbuster</application> runs
825 normally, <quote>toggle 0</quote> means that
826 <application>Junkbuster</application> becomes a non-anonymizing non-blocking
834 <emphasis>toggle 1</emphasis>
842 <!-- ~ End section ~ -->
845 <!-- ~~~~~ New section ~~~~~ -->
848 <title>Access Control List (ACL)</title>
850 Access controls are included at the request of some ISPs and systems
851 administrators, and are not usually needed by individual users. Please note
852 the warnings in the FAQ that this proxy is not intended to be a substitute
853 for a firewall or to encourage anyone to defer addressing basic security
858 If no access settings are specified, the proxy talks to anyone that
859 connects. If any access settings file are specified, then the proxy
860 talks only to IP addresses permitted somewhere in this file and not
861 denied later in this file.
865 Summary -- if using an ACL:
870 Client must have permission to receive service.
875 LAST match in ACL wins.
880 Default behavior is to deny service.
885 The syntax for an entry in the Access Control List is:
892 ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
899 Where the individual fields are:
906 <emphasis>ACTION</emphasis> = <quote>permit-access</quote> or <quote>deny-access</quote>
908 <emphasis>SRC_ADDR</emphasis> = client hostname or dotted IP address
909 <emphasis>SRC_MASKLEN</emphasis> = number of bits in the subnet mask for the source
911 <emphasis>DST_ADDR</emphasis> = server or forwarder hostname or dotted IP address
912 <emphasis>DST_MASKLEN</emphasis> = number of bits in the subnet mask for the target
920 The field separator (FS) is whitespace (space or tab).
924 IMPORTANT NOTE: If the <application>junkbuster</application> is using a
925 forwarder (see below) or a gateway for a particular destination URL, the
926 <literal>DST_ADDR</literal> that is examined is the address of the forwarder
927 or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
928 target. This is necessary because it may be impossible for the local
929 <application>Junkbuster</application> to determine the address of the
930 ultimate target (that's often what gateways are used for).
934 Here are a few examples to show how the ACL features work:
938 <quote>localhost</quote> is OK -- no DST_ADDR implies that
939 <emphasis>ALL</emphasis> destination addresses are OK:
946 <emphasis>permit-access localhost</emphasis>
953 A silly example to illustrate permitting any host on the class-C subnet with
954 <application>Junkbuster</application> to go anywhere:
961 <emphasis>permit-access www.junkbusters.com/24</emphasis>
968 Except deny one particular IP address from using it at all:
975 <emphasis>deny-access ident.junkbusters.com</emphasis>
982 You can also specify an explicit network address and subnet mask.
983 Explicit addresses do not have to be resolved to be used.
990 <emphasis>permit-access 207.153.200.0/24</emphasis>
997 A subnet mask of 0 matches anything, so the next line permits everyone.
1004 <emphasis>permit-access 0.0.0.0/0</emphasis>
1011 Note, you <emphasis>cannot</emphasis> say:
1018 <emphasis>permit-access .org</emphasis>
1025 to allow all *.org domains. Every IP address listed must resolve fully.
1029 An ISP may want to provide a <application>Junkbuster</application> that is
1030 accessible by <quote>the world</quote> and yet restrict use of some of their
1031 private content to hosts on its internal network (i.e. its own subscribers).
1032 Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
1033 bit netmask). This is how they could do it:
1040 <emphasis>permit-access 0.0.0.0/0 0.0.0.0/0</emphasis> # other clients can go anywhere
1041 # with the following exceptions:
1043 <emphasis>deny-access</emphasis> 0.0.0.0/0 123.124.0.0/16 # block all external requests for
1044 # sites on the ISP's network
1046 <emphasis>permit 0.0.0.0/0 www.my_isp.com</emphasis> # except for the ISP's main
1049 <emphasis>permit 123.124.0.0/16 0.0.0.0/0</emphasis> # the ISP's clients can go
1057 Note that if some hostnames are listed with multiple IP addresses,
1058 the primary value returned by DNS (via gethostbyname()) is used. Default:
1059 Anyone can access the proxy.
1064 <!-- ~ End section ~ -->
1067 <!-- ~~~~~ New section ~~~~~ -->
1070 <title>Forwarding</title>
1073 This feature allows routing of HTTP requests via multiple proxies.
1074 It can be used to better protect privacy and confidentiality when
1075 accessing specific domains by routing requests to those domains
1076 to a special purpose filtering proxy such as lpwa.com.
1080 It can also be used in an environment with multiple networks to route
1081 requests via multiple gateways allowing transparent access to multiple
1082 networks without having to modify browser configurations.
1086 Also specified here are SOCKS proxies. <application>Junkbuster</application>
1087 SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
1088 hostname using DNS on the SOCKS server, not our local DNS client.
1092 The syntax of each line is:
1099 <emphasis>forward target_domain[:port] http_proxy_host[:port]</emphasis>
1100 <emphasis>forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1101 <emphasis>forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1108 If http_proxy_host is <quote>.</quote>, then requests are not forwarded to a
1109 HTTP proxy but are made directly to the web servers.
1113 Lines are checked in sequence, and the last match wins.
1117 There is an implicit line equivalent to the following, which specifies that
1118 anything not finding a match on the list is to go out without forwarding
1119 or gateway protocol, like so:
1126 <emphasis>forward .* . </emphasis># implicit
1133 In the following common configuration, everything goes to Lucent's LPWA,
1134 except SSL on port 443 (which it doesn't handle):
1141 <emphasis>forward .* lpwa.com:8000</emphasis>
1142 <emphasis>forward :443 .</emphasis>
1149 See the FAQ for instructions on how to automate the login procedure for LPWA.
1150 Some users have reported difficulties related to LPWA's use of
1151 <quote>.</quote> as the last element of the domain, and have said that this
1152 can be fixed with this:
1159 <emphasis>forward lpwa. lpwa.com:8000</emphasis>
1166 (NOTE: the syntax for specifiying target_domain has changed since the
1167 previous paragraph was written -- it will not work now. More information
1172 In this fictitious example, everything goes via an ISP's caching proxy,
1173 except requests to that ISP:
1180 <emphasis>forward .* caching.myisp.net:8000</emphasis>
1181 <emphasis>forward myisp.net .</emphasis>
1188 For the @home network, we're told the forwarding configuration is this:
1196 <emphasis>forward .* proxy:8080</emphasis>
1203 Also, we're told they insist on getting cookies and JavaScript, so you need
1204 to add home.com to the cookie file. We consider JavaScript a security risk.
1205 Java need not be enabled.
1209 In this example direct connections are made to all <quote>internal</quote>
1210 domains, but everything else goes through Lucent's LPWA by way of the
1211 company's SOCKS gateway to the Internet.
1218 <emphasis>forward_socks4 .* lpwa.com:8000 firewall.my_company.com:1080</emphasis>
1219 <emphasis>forward my_company.com .</emphasis>
1226 This is how you could set up a site that always uses SOCKS but no forwarders:
1233 <emphasis>forward_socks4a .* . firewall.my_company.com:1080</emphasis>
1240 An advanced example for network administrators:
1244 If you have links to multiple ISPs that provide various special content to
1245 their subscribers, you can configure forwarding to pass requests to the
1246 specific host that's connected to that ISP so that everybody can see all
1247 of the content on all of the ISPs.
1251 This is a bit tricky, but here's an example:
1256 host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
1257 isp-b.com. host-a can run a <application>Junkbuster</application> proxy with
1258 forwarding like this:
1265 <emphasis>forward .* .</emphasis>
1266 <emphasis>forward isp-b.com host-b:8000</emphasis>
1273 host-b can run a <application>Junkbuster</application> proxy with forwarding
1281 <emphasis>forward .* .</emphasis>
1282 <emphasis>forward isp-a.com host-a:8000</emphasis>
1289 Now, <emphasis>anyone</emphasis> on the Internet (including users on host-a
1290 and host-b) can set their browser's proxy to <emphasis>either</emphasis>
1291 host-a or host-b and be able to browse the content on isp-a or isp-b.
1295 Here's another practical example, for University of Kent at
1296 Canterbury students with a network connection in their room, who
1297 need to use the University's Squid web cache.
1304 <emphasis>forward *. ssbcache.ukc.ac.uk:3128</emphasis> # Use the proxy, except for:
1305 <emphasis>forward .ukc.ac.uk . </emphasis> # Anything on the same domain as us
1306 <emphasis>forward * . </emphasis> # Host with no domain specified
1307 <emphasis>forward 129.12.*.* . </emphasis> # A dotted IP on our /16 network.
1308 <emphasis>forward 127.*.*.* . </emphasis> # Loopback address
1309 <emphasis>forward localhost.localdomain . </emphasis> # Loopback address
1310 <emphasis>forward www.ukc.mirror.ac.uk . </emphasis> # Specific host
1317 If you intend to chain <application>Junkbuster</application> and
1318 <application>squid</application> locally, then chain as
1319 <literal>browser -> squid -> junkbuster</literal> is the recommended way.
1323 Your squid configuration could then look like this:
1330 # Define junkbuster as parent cache
1331 cache_peer 127.0.0.1 8000 parent 0 no-query
1333 # Define ACL for protocol FTP
1336 # Do not forward ACL FTP to junkbuster
1337 always_direct allow FTP
1339 # Do not forward ACL CONNECT (https) to junkbuster
1340 always_direct allow CONNECT
1342 # Forward the rest to junkbuster
1343 never_direct allow all
1351 <!-- ~ End section ~ -->
1354 <!-- ~~~~~ New section ~~~~~ -->
1357 <title>Windows GUI Options</title>
1359 Removed references to Win32. HB 09/23/01
1362 <application>Junkbuster</application> has a number of options specific to the
1363 Windows GUI interface:
1367 If <quote>activity-animation</quote> is set to 1, the
1368 <application>Junkbuster</application> icon will animate when
1369 <quote>Junkbuster</quote> is active. To turn off, set to 0.
1376 <emphasis>activity-animation 1</emphasis>
1383 If <quote>log-messages</quote> is set to 1,
1384 <application>Junkbuster</application> will log messages to the console
1392 <emphasis>log-messages 1</emphasis>
1399 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
1400 i.e. the amount of memory used for the log messages displayed in the
1401 console window, will be limited to <quote>log-max-lines</quote> (see below).
1405 Warning: Setting this to 0 will result in the buffer to grow infinitely and
1406 eat up all your memory!
1413 <emphasis>log-buffer-size 1</emphasis>
1420 <application>log-max-lines</application> is the maximum number of lines held
1421 in the log buffer. See above.
1428 <emphasis>log-max-lines 200</emphasis>
1435 If <quote>log-highlight-messages</quote> is set to 1,
1436 <application>Junkbuster</application> will highlight portions of the log
1437 messages with a bold-faced font:
1444 <emphasis>log-highlight-messages 1</emphasis>
1451 The font used in the console window:
1458 <emphasis>log-font-name Comic Sans MS</emphasis>
1465 Font size used in the console window:
1472 <emphasis>log-font-size 8</emphasis>
1479 <quote>show-on-task-bar</quote> controls whether or not
1480 <application>Junkbuster</application> will appear as a button on the Task bar
1488 <emphasis>show-on-task-bar 0</emphasis>
1495 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
1496 button will minimize <application>Junkbuster</application> instead of closing
1497 the program (close with the exit option on the File menu).
1504 <emphasis>close-button-minimizes 1</emphasis>
1511 The <quote>hide-console</quote> option is specific to the MS-Win console
1512 version of <application>JunkBuster</application>. If this option is used,
1513 <application>Junkbuster</application> will disconnect from and hide the
1530 <!-- ~ End section ~ -->
1533 <!-- ~~~~~ New section ~~~~~ -->
1534 <sect2 id="actionsfile">
1535 <title>The Actions File</title>
1538 The <quote>actionsfile</quote> is used to define what actions
1539 <application>Junkbuster</application> takes, and thus determines how images,
1540 cookies and various other aspects of HTTP content and transactions are
1541 handled. Images can be anything you want, including ads, banners, or just
1542 some obnoxious image that you would rather not see. Cookies can be accepted
1543 or rejected. The default file is in fact named <filename>actionsfile</filename>.
1547 To determine which actions apply to a request, the URL of the request is
1548 compared to all patterns in this file. Every time it matches, the list of
1549 applicable actions for the URL is incrementally updated. You can trace
1550 this process by visiting <ulink
1551 url="http://i.j.b/show-url-info">http://i.j.b/show-url-info</ulink>.
1555 There are four types of lines in this file: comments (begin with a
1556 <quote>#</quote> character), actions, aliases and patterns, all of which are
1561 <!-- ~~~~~ New section ~~~~~ -->
1563 <title>URL Domain and Path Syntax</title>
1565 Generally, a pattern has the form <domain>/<path>, where both the
1566 <domain> and <path> part are optional. If you only specify a
1567 domain part, the <quote>/</quote> can be left out:
1571 <emphasis>www.example.com</emphasis> - is a domain only pattern and will match any request to
1572 <quote>www.example.com</quote>.
1576 <emphasis>www.example.com/</emphasis> - means exactly the same.
1580 <emphasis>www.example.com/index.html</emphasis> - matches only the single
1581 document <quote>/index.html</quote> on <quote>www.example.com</quote>.
1585 <emphasis>/index.html</emphasis> - matches the document <quote>/index.html</quote>, regardless of
1590 <emphasis>index.html</emphasis> - matches nothing, since it would be
1591 interpreted as a domain name and there is no top-level domain called
1592 <quote>.html</quote>.
1596 The matching of the domain part offers some flexible options: if the
1597 domain starts or ends with a dot, it becomes unanchored at that end.
1602 <emphasis>.example.com</emphasis> - matches any domain that <emphasis>ENDS</emphasis> in
1603 <quote>.example.com</quote>.
1607 <emphasis>www.</emphasis> - matches any domain that <emphasis>STARTS</emphasis> with
1612 Additionally, there are wildcards that you can use in the domain names
1613 themselves. They work pretty similar to shell wildcards: <quote>*</quote>
1614 stands for zero or more arbitrary characters, <quote>?</quote> stands for
1615 any single character. And you can define charachter classes in square
1616 brackets and they can be freely mixed:
1620 <emphasis>ad*.example.com</emphasis> - matches <quote>adserver.example.com</quote>,
1621 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>.
1625 <emphasis>*ad*.example.com</emphasis> - matches all of the above, and then some.
1629 <emphasis>.?pix.com</emphasis> - matches <quote>www.ipix.com</quote>,
1630 <quote>pictures.epix.com</quote>, <quote>a.b.c.d.e.upix.com</quote>, etc.
1634 <emphasis>www[1-9a-ez].example.com</emphasis> - matches <quote>www1.example.com</quote>,
1635 <quote>www4.example.com</quote>, <quote>wwwd.example.com</quote>,
1636 <quote>wwwz.example.com</quote>, etc., but <emphasis>not</emphasis>
1637 <quote>wwww.example.com</quote>.
1641 If <application>Junkbuster</application> was compiled with
1642 <quote>pcre</quote> support (default), Perl compatible regular expressions
1643 can be used. See the <filename>pcre/docs/</filename> direcory or <quote>man
1644 perlre</quote> (also available on <ulink
1645 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>)
1646 for details. A brief discussion of regular expressions is in the
1647 <link linkend="regex">Appendix</link>. For instance:
1651 <emphasis>/.*/advert[0-9]+\.jpe?g</emphasis> - would match a URL from any
1652 domain, with any path that includes <quote>advert</quote> followed
1653 immediately by one or more digits, then a <quote>.</quote> and ending in
1654 either <quote>jpeg</quote> or <quote>jpg</quote>. So we match
1655 <quote>example.com/ads/advert2.jpg</quote>, and
1656 <quote>www.example.com/ads/banners/advert39.jpeg</quote>, but not
1657 <quote>www.example.com/ads/banners/advert39.gif</quote> (no gifs in the
1662 Please note that matching in the path is case
1663 <emphasis>INSENSITIVE</emphasis> by default, but you can switch to case
1664 sensitive at any point in the pattern by using the
1665 <quote>(?-i)</quote> switch:
1669 <emphasis>www.example.com/(?-i)PaTtErN.*</emphasis> - will match only
1670 documents whose path starts with <quote>PaTtErN</quote> in
1671 <emphasis>exactly</emphasis> this capitalization.
1676 <!-- ~ End section ~ -->
1680 <!-- ~~~~~ New section ~~~~~ -->
1683 <title>Actions</title>
1685 Actions are enabled if preceded with a <quote>+</quote>, and disabled if
1686 preceded with a <quote>-</quote>. Actions are invoked by enclosing the
1687 action name in curly braces (e.g. {+some_action}), followed by a list of
1688 URLs to which the action applies. There are three classes of actions:
1696 Boolean (e.g. <quote>+/-block</quote>):
1702 <emphasis>{+name}</emphasis> # enable this action
1703 <emphasis>{-name}</emphasis> # disable this action
1713 Parameterized (e.g. <quote>+/-hide-user-agent</quote>):
1719 <emphasis>{+name{param}}</emphasis> # enable action and set parameter to <quote>param</quote>
1720 <emphasis>{-name}</emphasis> # disable action
1729 Multi-value (e.g. <quote>{+/-add-header{Name: value}}</quote>, <quote>{+/-wafer{name=value}}</quote>):
1735 <emphasis>{+name{param}}</emphasis> # enable action and add parameter <quote>param</quote>
1736 <emphasis>{-name{param}}</emphasis> # remove the parameter <quote>param</quote>
1737 <emphasis>{-name}</emphasis> # disable this action totally
1748 If nothing is specified in this file, no <quote>actions</quote> are taken.
1749 So in this case <application>JunkBuster</application> would just be a
1750 normal, non-blocking, non-anonymizing proxy. You must specifically
1751 enable the privacy and blocking features you need (although the
1752 provided default <filename>actionsfile</filename> file will
1753 give a good starting point).
1757 Later defined actions always over-ride earlier ones. For multi-valued
1758 actions, the actions are applied in the order they are specified.
1762 The list of valid <application>Junkbuster</application> <quote>actions</quote> are:
1770 Add the specified HTTP header, which is not checked for validity.
1771 You may specify this many times to specify many different headers:
1777 <emphasis>+add-header{Name: value}</emphasis>
1787 Block this URL totally.
1793 <emphasis>+block</emphasis>
1803 De-animate all animated GIF images, i.e. reduce them to their last frame.
1804 This will also shrink the images considerably (in bytes, not pixels!). If
1805 the option <quote>first</quote> is given, the first frame of the animation
1806 is used as the replacement. If <quote>last</quote> is given, the last frame
1807 of the animation is used instead, which propably makes more sense for most
1808 banner animations, but also has the risk of not showing the entire last
1809 frame (if it is only a delta to an earlier frame).
1815 <emphasis>+deanimate-gifs{last}</emphasis>
1816 <emphasis>+deanimate-gifs{first}</emphasis>
1825 Many sites, like yahoo.com, don't just link to other sites. Instead, they
1826 will link to some script on their own server, giving the destination as a
1827 parameter, which will then redirect you to the final target. URLs resulting
1828 from this scheme typically look like:
1829 http://some.place/some_script?http://some.where-else.
1832 Sometimes, there are even multiple consecutive redirects encoded in the
1833 URL. These redirections via scripts make your web browing more traceable,
1834 since the server from which you follow such a link can see where you go to.
1835 Apart from that, valuable bandwidth and time is wasted, while your browser
1836 ask the server for one redirect after the other. Plus, it feeds the
1840 The <quote>+fast-redirects</quote> option enables interception of these
1841 requests by <application>Junkbuster</application>, who will cut off all but
1842 the last valid URL in the request and send a local redirect back to your
1843 browser without contacting the remote site.
1849 <emphasis>+fast-redirects</emphasis>
1858 Filter the website through the re_filterfile:
1864 <emphasis>+filter{filename}</emphasis>
1873 Block any existing X-Forwarded-for header, and do not add a new one:
1879 <emphasis>+hide-forwarded</emphasis>
1888 If the browser sends a <quote>From:</quote> header containing your e-mail
1889 address, this either completely removes the header (<quote>block</quote>), or
1890 changes it to the specified e-mail address.
1896 <emphasis>+hide-from{block}</emphasis>
1897 <emphasis>+hide-from{spam@sittingduck.xqq}</emphasis>
1906 Don't send the <quote>Referer:</quote> (sic) header to the web site. You
1907 can block it, forge a URL to the same server as the request (which is
1908 preferred because some sites will not send images otherwise) or set it to a
1909 constant string of your choice.
1915 <emphasis>+hide-referer{block}</emphasis>
1916 <emphasis>+hide-referer{forge}</emphasis>
1917 <emphasis>+hide-referer{http://nowhere.com}</emphasis>
1926 Alternative spelling of <quote>+hide-referer</quote>. It has the same
1927 parameters, and can be freely mixed with, <quote>+hide-referer</quote>.
1928 (<quote>referrer</quote> is the correct English spelling, however the HTTP
1929 specification has a bug - it requires it to be spelled <quote>referer</quote>.)
1935 <emphasis>+hide-referrer{...}</emphasis>
1944 Change the <quote>User-Agent:</quote> header so web servers can't tell your
1945 browser type. Warning! This breaks many web sites. Specify the
1946 user-agent value you want. Example, pretend to be using Netscape on
1953 <emphasis>+hide-user-agent{Mozilla (X11; I; Linux 2.0.32 i586)}</emphasis>
1960 Or to identify yourself explicitly as a <quote>Junkbuster</quote> user:
1966 <emphasis>+hide-user-agent{JunkBuster/1.0}</emphasis>
1971 (Don't change the version number from 1.0 - after all, why tell them?)
1978 <emphasis>+hide-user-agent{browser-type}</emphasis>
1988 Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
1989 in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
1990 See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
1996 <emphasis>+image</emphasis>
2005 Decides what to do with URLs that end up tagged with <quote>{+block
2006 +image}</quote>. There are 4 options. <quote>-image-blocker</quote> will
2007 send a HTML <quote>blocked</quote> page, usually resulting in a
2008 <quote>broken image</quote> icon. <quote>+image-blocker{logo}</quote> will
2009 send a <quote>JunkBuster</quote> image.
2010 <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF image.
2011 And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a HTTP
2012 temporary redirect to the specified image. This has the advantage of the
2013 icon being being cached by the browser, which will speed up the display.
2019 <emphasis>+image-blocker{logo}</emphasis>
2020 <emphasis>+image-blocker{blank}</emphasis>
2021 <emphasis>+image-blocker{http://i.j.b/send-banner}</emphasis>
2030 Prevent the website from reading cookies:
2036 <emphasis>+no-cookies-read</emphasis>
2045 Prevent the website from setting cookies:
2051 <emphasis>+no-cookies-set</emphasis>
2060 Filter the website through a built-in filter to disable those obnoxious
2061 JavaScript pop-up windows via window.open(), etc. The two alternative
2062 spellings are equivalent.
2068 <emphasis>+no-popup</emphasis>
2069 <emphasis>+no-popups</emphasis>
2078 This action only applies if you are using a <filename>jarfile</filename>
2079 for saving cookies. It sends a cookie to every site stating that you do not
2080 accept any copyright on cookies sent to you, and asking them not to track
2081 you. Of course, this is a (relatively) unique header they could use to
2088 <emphasis>+vanilla-wafer</emphasis>
2097 This allows you to add an arbitrary cookie. It can be specified multiple
2098 times in order to add as many cookies as you like.
2104 <emphasis>+wafer{name=value}</emphasis>
2115 The meaning of any of the above is reversed by preceding the action with a
2116 <quote>-</quote>, in place of the <quote>+</quote>.
2124 Turn off cookies by default, then allow a few through for specified sites:
2131 # Turn off all cookies
2132 { +no-cookies-read }
2135 # Execeptions to the above, sites that need cookies
2136 { -no-cookies-read }
2144 # Alternative way of saying the same thing
2145 {-no-cookies-set -no-cookies-read}
2154 Now turn off <quote>fast redirects</quote>, and then we allow two exceptions:
2164 # Reverse it for these two sites, which don't work right without it.
2166 www.ukc.ac.uk/cgi-bin/wac\.cgi\?
2174 Turn on page filtering, with one exception for sourceforge:
2181 # Run everything through the default filter file (<filename>re_filterfile</filename>):
2184 # But please don't re_filter code from sourceforge!
2186 .cvs.sourceforge.net
2193 Now some URLs that we want <quote>blocked</quote>, ie we won't see them.
2194 Many of these use regular expressions that will expand to match multiple
2204 /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g))
2205 /.*/(.*[-_.])?count(er)?(\.cgi|\.dll|\.exe|[?/])
2206 /.*/(ng)?adclient\.cgi
2207 /.*/(plain|live|rotate)[-_.]?ads?/
2208 /.*/(sponsor)s?[0-9]?/
2209 /.*/_?(plain|live)?ads?(-banners)?/
2211 /.*/ad(sdna_image|gifs?)/
2212 /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe)
2216 /.*/adv((er)?ts?|ertis(ing|ements?))?/
2220 /.*/cgi-bin/centralad/getimage
2221 /.*/images/addver\.gif
2222 /.*/images/marketing/.*\.(gif|jpe?g)
2226 /.*/sponsors?[0-9]?/
2227 /.*/advert[0-9]+\.jpg
2234 /graphics/defaultAd/
2236 /image\.ng/transactionID
2237 /images/.*/.*_anim\.gif # alvin brattli
2238 /ip_img/.*\.(gif|jpe?g)
2242 /cgi-bin/nph-adclick.exe/
2243 /.*/Image/BannerAdvertising/
2245 /.*/adlib/server\.cgi
2254 <!-- ~ End section ~ -->
2257 <!-- ~~~~~ New section ~~~~~ -->
2259 <title>Aliases</title>
2261 Custom <quote>actions</quote>, known to <application>Junkbuster</application>
2262 as <quote>aliases</quote>, can be defined by combing other <quote>actions</quote>.
2263 These can in turn be invoked just like the built-in <quote>actions</quote>.
2264 Currently, an alias can contain any character except space, tab, <quote>=</quote>,
2265 <quote>{</quote> or <quote>}</quote>. But please use only <quote>a</quote>-
2266 <quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
2267 <quote>-</quote>. Alias names are not case sensitive, and must be defined
2268 before they are used.
2272 Now let's define a few aliases:
2283 +no-cookies = +no-cookies-set +no-cookies-read
2284 -no-cookies = -no-cookies-set -no-cookies-read
2285 fragile = -block -no-cookies -filter -fast-redirects -hide-referer -no-popups
2286 shop = -no-cookies -filter -fast-redirects
2287 +imageblock = +block +image
2289 #For people who don't like to type too much: ;-)
2292 c2 = -no-cookies-set +no-cookies-read
2293 c3 = +no-cookies-set -no-cookies-read
2294 #... etc. Customize to your heart's content.
2301 Some examples using our <quote>shop</quote> and <quote>fragile</quote>
2309 # These sites are very complex and require
2310 # minimal interference.
2312 .office.microsoft.com
2313 .windowsupdate.microsoft.com
2315 # Shopping sites - still want to block ads.
2318 .worldpay.com # for quietpc.com
2322 # These shops require pop-ups
2334 <!-- ~ End section ~ -->
2337 <!-- ~~~~~ New section ~~~~~ -->
2338 <sect2 id="filterfile">
2339 <title>The Filter File</title>
2341 The filter file defines what filtering of web pages
2342 <application>Junkbuster</application> does. The default filter file is
2343 <filename>re_filterfile</filename>, located in the config directory. In this
2344 file, <emphasis>any document content</emphasis>, whether viewable text or
2345 embedded non-visible content, can be changed.
2349 This file uses regular expressions to alter or remove any string in the
2350 target page. Some examples from the included default <filename>re_filterfile</filename>:
2354 Stop web pages from displaying annoying messages in the status bar by
2355 deleting such references:
2362 # The status bar is for displaying link targets, not pointless buzzwords.
2363 # Again, check it out on http://www.airport-cgn.de/.
2364 s/status='.*?';*//ig
2371 Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
2372 <quote>MicroSuck</quote>:
2379 s/microsoft(?!.com)/MicroSuck/ig
2386 Kill those auto-refresh tags:
2393 # Kill refresh tags. I like to refresh myself. Manually.
2394 # check it out on http://www.airport-cgn.de/ and go to the arrivals page.
2396 s/<meta[^>]*http-equiv[^>]*refresh.*URL=([^>]*?)"?>/<link rev="x-refresh" href=$1>/i
2397 s/<meta[^>]*http-equiv="?page-enter"?[^>]*content=[^>]*>/<!--no page enter for me-->/i
2407 <!-- ~~~~~ New section ~~~~~ -->
2408 <sect1 id="quickstart"><title>Quickstart to Using Junkbuster</title>
2414 <!-- ~~~~~ New section ~~~~~ -->
2415 <sect1 id="contact"><title>Contact the developers</title>
2416 <para>To be filled. mention the support forums as the primary channel of
2417 communication (bugs, feature requests, etc.)
2421 <!-- ~~~~~ New section ~~~~~ -->
2422 <sect1 id="copyright"><title>Copyright and History</title>
2427 <!-- ~~~~~ New section ~~~~~ -->
2428 <sect1 id="seealso"><title>See also</title>
2435 <!-- ~~~~~ New section ~~~~~ -->
2436 <sect1 id="appendix"><title>Appendix</title>
2439 <!-- ~~~~~ New section ~~~~~ -->
2441 <title>Regular Expressions</title>
2452 This program is free software; you can redistribute it
2453 and/or modify it under the terms of the GNU General
2454 Public License as published by the Free Software
2455 Foundation; either version 2 of the License, or (at
2456 your option) any later version.
2458 This program is distributed in the hope that it will
2459 be useful, but WITHOUT ANY WARRANTY; without even the
2460 implied warranty of MERCHANTABILITY or FITNESS FOR A
2461 PARTICULAR PURPOSE. See the GNU General Public
2462 License for more details.
2464 The GNU General Public License should be included with
2465 this file. If not, you can view it at
2466 http://www.gnu.org/copyleft/gpl.html
2467 or write to the Free Software Foundation, Inc., 59
2468 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
2470 $Log: user-manual.sgml,v $
2471 Revision 1.2 2001/09/13 15:27:40 swa
2474 Revision 1.1 2001/09/12 15:36:41 swa
2475 source files for junkbuster documentation
2477 Revision 1.3 2001/09/10 17:43:59 swa
2478 first proposal of a structure.
2480 Revision 1.2 2001/06/13 14:28:31 swa
2481 docs should have an author.
2483 Revision 1.1 2001/06/13 14:20:37 swa
2484 first import of project's documentation for the webserver.