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.26 2002/01/09 20:02:50 hal9 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.26 2002/01/09 20:02:50 hal9 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/user-manual/">http://ijbswa.sourceforge.net/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, controlling access, and removing ads, banners, pop-ups and
69 other obnoxious Internet Junk. <application>Junkbuster</application> has a
70 very flexible configuration and can be customized to suit individual needs
71 and tastes. <application>Internet Junkbuster</application> has application
72 for both 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 many significant changes and
81 enhancements over earlier verions. The target release date for stable v3.0 is
86 Since this is a development version, some features are in the process of
87 being implemented. This documentation may be slightly out of sync as a
88 result. And there <emphasis>are</emphasis> bugs, though hopefully not many!
92 <!-- ~~~~~ New section ~~~~~ -->
94 <title>New Features</title>
96 In addition to <application>Junkbuster's</application> traditional features
97 of ad and banner blocking and cookie management, this is a list of new
98 features currently under development:
106 A browser based configuration utility (WIP at
107 <ulink url="http://i.j.b">http://i.j.b</ulink>).
113 Modularized configuration that will allow for system wide settings, and
114 individual user settings. (not implemented yet, probably a 3.1 feature)
120 Blocking of annoying pop-up browser windows (previously available as a
127 Support for HTTP/1.1 (partially implemented at this point).
133 Support for Perl Compatible Regular Expressions in the configuration files, and
134 generally a more sophisticated configuration syntax over previous versions.
140 Web page content filtering.
152 Auto-detection of config file changes.
161 In addition, the configuration is much more versatile overall.
168 <!-- ~ End section ~ -->
171 <!-- ~~~~~ New section ~~~~~ -->
172 <sect1 id="installation"><title>Installation</title>
174 <application>Junkbuster</application> is available as raw source code, or
175 pre-compiled binaries. See the <ulink
176 url="http://sourceforge.net/projects/ijbswa/">Junkbuster Home Page</ulink>
177 for current release info. <application>Junkbuster</application> is also available
179 url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
180 This is the recommended approach at this time. But please be aware that CVS
181 is constantly changing, and it may break in mysterious ways.
184 <!-- ~~~~~ New section ~~~~~ -->
185 <sect2 id="installation-source"><title>Source</title>
187 For gzipped tar archives, unpack the source:
192 tar xzvf ijb_source_* [.tgz or .tar.gz]
193 cd ijb_source_2.9.10_beta
198 For retrieving the current CVS sources, you'll need the CVS
199 package installed first. To download CVS source:
204 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
205 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
211 This will create a directory named <filename>current/</filename>, which will
212 contain the source tree.
216 Then, in either case, to build from tarball/CVS source:
221 ./configure (--help to see options)
222 make (the make from gnu, gmake for *BSD)
224 make -n install (to see where all the files will go)
225 make install (to really install)
230 For Redhat and SuSE Linux RPM packages, see below.
236 <!-- ~~~~~ New section ~~~~~ -->
237 <sect2 id="installation-rh"><title>Red Hat</title>
239 To build Redhat RPM packages, install source as above. Then:
244 autoheader [suggested for CVS source]
245 autoconf [suggested for CVS source]
252 This will create both binary and src RPMs in the usual places. Example:
256 /usr/src/redhat/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
259 /usr/src/redhat/SRPMS/junkbuster-2.9.10-1.src.rpm
263 To install, of course:
268 rpm -Uvv /usr/src/redhat/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
273 This will place the <application>Junkbuster</application> configuration
274 files in <filename>/etc/junkbuster/</filename>, and log files in
275 <filename>/var/log/junkbuster/</filename>.
280 <!-- ~~~~~ New section ~~~~~ -->
281 <sect2 id="installation-suse"><title>SuSE</title>
283 To build SuSE RPM packages, install source as above. Then:
288 autoheader [suggested for CVS source]
289 autoconf [suggested for CVS source]
296 This will create both binary and src RPMs in the usual places. Example:
300 /usr/src/packages/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
303 /usr/src/packages/SRPMS/junkbuster-2.9.10-1.src.rpm
307 To install, of course:
312 rpm -Uvv /usr/src/packages/RPMS/i686/junkbuster-2.9.10-1.i686.rpm
317 This will place the <application>Junkbuster</application> configuration
318 files in <filename>/etc/junkbuster/</filename>, and log files in
319 <filename>/var/log/junkbuster/</filename>.
325 <!-- ~~~~~ New section ~~~~~ -->
326 <sect2 id="installation-os2"><title>OS/2</title>
333 The OS/2 version of <application>Junkbuster</application> requires the EMX
334 runtime library to be installed. The EMX runtime library is available on
335 the hobbes OS/2 archive, among many other locations:
336 <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>
340 <application>Junkbuster</application> is packaged in a WarpIN self-
341 installing archive. The self-installing program will be named depending
342 on the release version, something like:
343 <filename>ijbos123.exe</filename>. In order to install it, simply run
344 this executable or double-click on its icon and follow the WarpIN
345 installation panels. A shadow of the <application>Junkbuster</application>
346 executable will be placed in your startup folder so it will start
347 automatically whenever OS/2 starts.
351 The directory you choose to install <application>Junkbuster</application>
352 into will contain all of the configuration files.
356 If you would like to build binary images on OS/2 yourself, you will need
357 a working EMX/GCC environment, plus several Unix-like tools. The Hobbes
358 OS/2 archive is a good place to start when building such an environment.
359 A set of Unix-like tools named gnupack is located here:
360 <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>
363 Once you have the source code unpacked as above, you can build the binaries
364 from the <filename>current/</filename> directory:
378 <!-- ~~~~~ New section ~~~~~ -->
379 <sect2 id="installation-win"><title>Windows</title>
380 <para>Click-click. (I need help on this. Not a clue here. Also for
381 configuration section below. HB.)
385 <!-- ~~~~~ New section ~~~~~ -->
386 <sect2 id="installation-other"><title>Other</title>
388 Some quick notes on other Operating Systems.
392 For FreeBSD (and other *BSDs?), the build will require <command>gmake</command>
393 instead of the included <command>make</command>. <command>gmake</command> is
394 available from <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>.
395 The rest should be the same as above for Linux/Unix.
402 <!-- ~ End section ~ -->
405 <!-- ~~~~~ New section ~~~~~ -->
406 <sect1 id="configuration"><title>Junkbuster Configuration</title>
408 For Unix, *BSD and Linux, all configuraton files are located in
409 <filename>/etc/junkbuster/</filename> by default. For MS Windows and OS/2,
410 these are all in the same directory as the
411 <application>Junkbuster</application> executable. The name and number of
412 configuration files has changed from previous versions, and is subject to
413 change as development progresses.
417 The installed defaults provide a reasonable starting point, though possibly
418 aggressive by some standards. For the time being, there are only three
419 default configuration files (this will change in time):
427 The main configuration file is named <filename>config</filename>
428 on Linux, Unix, BSD, and OS/2, and <filename>config.txt</filename> on
429 Windows. On Amiga, it is
430 <filename>AmiTCP:db/junkbuster/config</filename>.
436 The <filename>ijb.action</filename> file is used to define various
437 <quote>actions</quote> relating to images, banners, pop-ups, access
438 restrictions, banners and cookies. There is a CGI based editor for this
439 file that can be accessed via <ulink
440 url="http://i.j.b">http://i.j.b</ulink>. This is the easiest method of
441 configuring actions. (Still under active development. Other actions
442 files are included as well with differing levels of filtering
443 and blocking, e.g. <filename>ijb-basic.action</filename>.)
449 The <filename>re_filterfile</filename> file can be used to rewrite the raw
450 page content, including text as well as embedded HTML and JavaScript.
458 <filename>ijb.action</filename> and <filename>re_filterfile</filename>
459 can use Perl style regular expressions for maximum flexibility. All files use
460 the <quote><literal>#</literal></quote> character to denote a comment. Such
461 lines are not processed by <application>Junkbuster</application>. After
462 making any changes, there is no need to restart
463 <application>Junkbuster</application> in order for the changes to take
464 effect. <application>Junkbuster</application> should detect such changes
469 While under development, the configuration content is subject to change.
470 The below documentation may not be accurate by the time you read this.
471 Also, what constitutes a <quote>default</quote> setting, may change, so
472 please check all your configuration files on important issues.
475 <!-- ~~~~~ New section ~~~~~ -->
478 <title>The Main Configuration File</title>
480 Again, the main configuration file is named <filename>config</filename> on
481 Linux/Unix/BSD and OS/2, and <filename>config.txt</filename> on Windows.
482 Configuration lines consist of an initial keyword followed by a list of
483 values, all separated by whitespace (any number of spaces or tabs). For
491 <emphasis>blockfile blocklist.ini</emphasis>
498 Indicates that the blockfile is named <quote>blocklist.ini</quote>.
502 A <quote><literal>#</literal></quote> indicates a comment. Any part of a
503 line following a <quote><literal>#</literal></quote> is ignored, except if
504 the <quote><literal>#</literal></quote> is preceded by a
505 <quote><literal>\</literal></quote>.
509 Thus, by placing a <quote><literal>#</literal></quote> at the start of an
510 existing configuration line, you can make it a comment and it will be treated
511 as if it weren't there. This is called <quote>commenting out</quote> an
512 option and can be useful to turn off features: If you comment out the
513 <quote>logfile</quote> line, <application>junkbuster</application> will not
514 log to a file at all. Watch for the <quote>default:</quote> section in each
515 explanation to see what happens if the option is left unset (or commented
520 Long lines can be continued on the next line by using a
521 <quote><literal>\</literal></quote> as the very last character.
525 There are various aspects of <application>Junkbuster</application> behavior
530 <!-- ~~~~~ New section ~~~~~ -->
533 <title>Defining Other Configuration Files</title>
536 <application>Junkbuster</application> can use a number of other files to tell it
537 what ads to block, what cookies to accept, etc. This section of the
538 configuration file tells <application>Junkbuster</application> where to find
539 all those other files.
543 On <application>Windows</application>, <application>Junkbuster</application>
544 looks for these files in the same directory as the executable. On Unix and
545 OS/2, <application>Junkbuster</application> looks for these files in the current
546 working directory. In either case, an absolute path name can be used to
551 When development goes modular and multiuser, the blocker, filter, and
552 per-user config will be stored in subdirectories of <quote>confdir</quote>.
553 For now, only <filename>confdir/templates</filename> is used for storing HTML
554 templates for CGI results.
558 The location of the configuration files:
565 <emphasis>confdir /etc/junkbuster</emphasis> # No trailing /, please.
572 The directory where all logging (i.e. <filename>logfile</filename> and
573 <filename>jarfile</filename>) takes place. No trailing
574 <quote><literal>/</literal></quote>, please:
581 <emphasis>logdir /var/log/junkbuster</emphasis>
588 Note that all file specifications below are relative to
589 the above two directories!
593 The <quote>ijb.action</quote> file contains patterns to specify the actions to
594 apply to requests for each site. Default: Cookies to and from all
595 destinations are kept only during the current browser session (i.e. they
596 are not saved to disk). Popups are disabled for all sites. All sites are
597 filtered if <quote>re_filterfile</quote> specified. No sites are blocked. An
598 empty image is displayed for filtered ads and other images (formerly
599 <quote>tinygif</quote>). The syntax of this file is explained in detail <link
600 linkend="actionsfile">below</link>.
607 <emphasis>actionsfile ijb.action</emphasis>
614 The <quote>re_filterfile</quote> file contains content modification rules.
615 These rules permit powerful changes on the content of Web pages, e.g., you
616 could disable your favourite JavaScript annoyances, rewrite the actual
617 content, or just have some fun replacing <quote>Microsoft</quote> with
618 <quote>MicroSuck</quote> wherever it appears on a Web page. Default: No
619 content modification, or whatever the developers are playing with :-/
626 <emphasis>re_filterfile re_filterfile</emphasis>
633 The logfile is where all logging and error messages are written. The logfile
634 can be useful for tracking down a problem with
635 <application>Junkbuster</application> (e.g., it's not blocking an ad you
636 think it should block) but in most cases you probably will never look at it.
640 Your logfile will grow indefinitely, and you will probably want to
641 periodically remove it. On Unix systems, you can do this with a cron job
642 (see <quote>man cron</quote>). For Redhat, a <command>logrotate</command>
643 script has been included.
647 On SuSE Linux systems, you can place a line like <quote>/var/log/junkbuster.*
648 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
649 the effect that cron.daily will automatically archive, gzip, and empty the
650 log, when it exceeds 1M size.
654 Default: Log to the a file named <filename>logfile</filename>.
655 Comment out to disable logging.
662 <emphasis>logfile logfile</emphasis>
669 The <quote>jarfile</quote> defines where
670 <application>Junkbuster</application> stores the cookies it intercepts. Note
671 that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
672 Don't store intercepted cookies.
679 <emphasis>#jarfile jarfile</emphasis>
686 If you specify a <quote>trustfile</quote>,
687 <application>Junkbuster</application> will only allow access to sites that
688 are named in the trustfile. You can also mark sites as trusted referrers,
689 with the effect that access to untrusted sites will be granted, if a link
690 from a trusted referrer was used. The link target will then be added to the
691 <quote>trustfile</quote>. This is a very restrictive feature that typical
692 users most propably want to leave disabled. Default: Disabled, don't use the
700 <emphasis>#trustfile trust</emphasis>
707 If you use the trust mechanism, it is a good idea to write up some online
708 documentation about your blocking policy and to specify the URL(s) here. They
709 will appear on the page that your users receive when they try to access
710 untrusted content. Use multiple times for multiple URLs. Default: Don't
711 display links on the <quote>untrusted</quote> info page.
718 <emphasis>trust-info-url http://www.your-site.com/why_we_block.html</emphasis>
719 <emphasis>trust-info-url http://www.your-site.com/what_we_allow.html</emphasis>
727 <!-- ~ End section ~ -->
731 <!-- ~~~~~ New section ~~~~~ -->
734 <title>Other Configuration Options</title>
737 This part of the configuration file contains options that control how
738 <application>Junkbuster</application> operates.
742 <quote>Admin-address</quote> should be set to the email address of the proxy
743 administrator. It is used in many of the proxy-generated pages. Default:
751 <emphasis>#admin-address fill@me.in.please</emphasis>
758 <quote>Proxy-info-url</quote> can be set to a URL that contains more info
759 about this <application>Junkbuster</application> installation, it's
760 configuration and policies. It is used in many of the proxy-generated pages
761 and its use is highly recommended in multi-user installations, since your
762 users will want to know why certain content is blocked or modified. Default:
763 Don't show a link to online documentation.
770 <emphasis>proxy-info-url http://www.your-site.com/proxy.html</emphasis>
777 <quote>Listen-address</quote> specifies the address and port where
778 <application>Junkbuster</application> will listen for connections from your
779 Web browser. The default is to listen on the localhost port 8000, and
780 this is suitable for most users. (In your web browser, under proxy
781 configuration, list the proxy server as <quote>localhost</quote> and the
782 port as <quote>8000</quote>).
786 If you already have another service running on port 8000, or if you want to
787 serve requests from other machines (e.g. on your local network) as well, you
788 will need to override the default. The syntax is
789 <quote>listen-address [<ip-address>]:<port></quote>. If you leave
790 out the IP address, <application>junkbuster</application> will bind to all
791 interfaces (addresses) on your machine and may become reachable from the
792 Internet. In that case, consider using access control lists (acl's) (see
793 <quote>aclfile</quote> above), or a firewall.
797 For example, suppose you are running <application>Junkbuster</application> on
798 a machine which has the address 192.168.0.1 on your local private network
799 (192.168.0.0) and has another outside connection with a different address.
800 You want it to serve requests from inside only:
807 <emphasis>listen-address 192.168.0.1:8000</emphasis>
814 If you want it to listen on all addresses (including the outside
822 <emphasis>listen-address :8000</emphasis>
829 If you do this, consider using ACLs (see <quote>aclfile</quote> above). Note:
830 you will need to point your browser(s) to the address and port that you have
831 configured here. Default: localhost:8000 (127.0.0.1:8000).
835 The debug option sets the level of debugging information to log in the
836 logfile (and to the console in the Windows version). A debug level of 1 is
837 informative because it will show you each request as it happens. Higher
838 levels of debug are probably only of interest to developers.
845 debug 1 # GPC = show each GET/POST/CONNECT request
846 debug 2 # CONN = show each connection status
847 debug 4 # IO = show I/O status
848 debug 8 # HDR = show header parsing
849 debug 16 # LOG = log all data into the logfile
850 debug 32 # FRC = debug force feature
851 debug 64 # REF = debug regular expression filter
852 debug 128 # = debug fast redirects
853 debug 256 # = debug GIF deanimation
854 debug 512 # CLF = Common Log Format
855 debug 1024 # = debug kill popups
856 debug 4096 # INFO = Startup banner and warnings.
857 debug 8192 # ERROR = Non-fatal errors
864 It is <emphasis>highly recommended</emphasis> that you enable ERROR
865 reporting (debug 8192), at least until the next stable release.
869 The reporting of FATAL errors (i.e. ones which crash
870 <application>JunkBuster</application>) is always on and cannot be disabled.
874 If you want to use CLF (Common Log Format), you should set <quote>debug
875 512</quote> ONLY, do not enable anything else.
879 Multiple <quote>debug</quote> directives, are OK - they're logical-OR'd
887 <emphasis>debug 15 # same as setting the first 4 listed above</emphasis>
901 <emphasis>debug 1 # URLs</emphasis>
902 <emphasis>debug 4096 # Info</emphasis>
903 <emphasis>debug 8192 # Errors - *we highly recommended enabling this*</emphasis>
910 <application>Junkbuster</application> normally uses
911 <quote>multi-threading</quote>, a software technique that permits it to
912 handle many different requests simultaneously. In some cases you may wish to
913 disable this -- particularly if you're trying to debug a problem. The
914 <quote>single-threaded</quote> option forces
915 <application>Junkbuster</application> to handle requests sequentially.
916 Default: Multi-threaded mode.
923 <emphasis>#single-threaded</emphasis>
930 <quote>toggle</quote> allows you to temporarily disable all
931 <application>Junkbuster's</application> filtering. Just set <quote>toggle
936 The Windows version of <application>Junkbuster</application> puts an icon in
937 the system tray, which also allows you to change this option. If you
938 right-click on that icon (or select the <quote>Options</quote> menu), one
939 choice is <quote>Enable</quote>. Clicking on enable toggles
940 <application>Junkbuster</application> on and off. This is useful if you want
941 to temporarily disable <application>Junkbuster</application>, e.g., to access
942 a site that requires cookies which you would otherwise have blocked. This can also
943 be toggled via a web browser at the <application>Junkbuster</application>
944 internal address of <ulink url="http://i.j.b">http://i.j.b</ulink> on
949 <quote>toggle 1</quote> means <application>Junkbuster</application> runs
950 normally, <quote>toggle 0</quote> means that
951 <application>Junkbuster</application> becomes a non-anonymizing non-blocking
952 proxy. Default: 1 (on).
959 <emphasis>toggle 1</emphasis>
966 For content filtering, i.e. the <quote>+filter</quote> and
967 <quote>+deanimate-gif</quote> actions, it is neccessary that
968 <application>Junkbuster</application> buffers the entire document body.
969 This can be potentially dangerous, since a server could just keep sending
970 data indefinitely and wait for your RAM to exhaust. With nasty consequences.
974 The <application>buffer-limit</application> option lets you set the maximum
975 size in Kbytes that each buffer may use. When the documents buffer exceeds
976 this size, it is flushed to the client unfiltered and no further attempt to
977 filter the rest of it is made. Remember that there may multiple threads
978 running, which might require increasing the <quote>buffer-limit</quote>
979 Kbytes <emphasis>each</emphasis>, unless you have enabled
980 <quote>single-threaded</quote> above.
987 <emphasis>buffer-limit 4069</emphasis>
994 To enable the web-based <filename>ijb.action</filename> file editor set
995 <application>enable-edit-actions</application> to 1, or 0 to disable. Note
996 that you must have compiled <application>JunkBuster</application> with
997 support for this feature, otherwise this option has no effect. This
998 internal page can be reached at <ulink
999 url="http://i.j.b">http://i.j.b</ulink>.
1003 Security note: If this is enabled, anyone who can use the proxy
1004 can edit the actions file, and their changes will affect all users.
1005 For shared proxies, you probably want to disable this. Default: enabled.
1012 <emphasis>enable-edit-actions 1</emphasis>
1019 Allow <application>JunkBuster</application> to be toggled on and off
1020 remotely, using your web browser. Set <quote>enable-remote-toggle</quote>to
1021 1 to enable, and 0 to disable. Note that you must have compiled
1022 <application>JunkBuster</application> with support for this feature,
1023 otherwise this option has no effect.
1027 Security note: If this is enabled, anyone who can use the proxy can toggle
1028 it on or off (see <ulink url="http://i.j.b">http://i.j.b</ulink>), and
1029 their changes will affect all users. For shared proxies, you probably want to
1030 disable this. Default: enabled.
1037 <emphasis>enable-remote-toggle 1</emphasis>
1045 <!-- ~ End section ~ -->
1048 <!-- ~~~~~ New section ~~~~~ -->
1051 <title>Access Control List (ACL)</title>
1053 Access controls are included at the request of some ISPs and systems
1054 administrators, and are not usually needed by individual users. Please note
1055 the warnings in the FAQ that this proxy is not intended to be a substitute
1056 for a firewall or to encourage anyone to defer addressing basic security
1061 If no access settings are specified, the proxy talks to anyone that
1062 connects. If any access settings file are specified, then the proxy
1063 talks only to IP addresses permitted somewhere in this file and not
1064 denied later in this file.
1068 Summary -- if using an ACL:
1073 Client must have permission to receive service.
1078 LAST match in ACL wins.
1083 Default behavior is to deny service.
1088 The syntax for an entry in the Access Control List is:
1095 ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
1102 Where the individual fields are:
1109 <emphasis>ACTION</emphasis> = <quote>permit-access</quote> or <quote>deny-access</quote>
1111 <emphasis>SRC_ADDR</emphasis> = client hostname or dotted IP address
1112 <emphasis>SRC_MASKLEN</emphasis> = number of bits in the subnet mask for the source
1114 <emphasis>DST_ADDR</emphasis> = server or forwarder hostname or dotted IP address
1115 <emphasis>DST_MASKLEN</emphasis> = number of bits in the subnet mask for the target
1123 The field separator (FS) is whitespace (space or tab).
1127 IMPORTANT NOTE: If the <application>junkbuster</application> is using a
1128 forwarder (see below) or a gateway for a particular destination URL, the
1129 <literal>DST_ADDR</literal> that is examined is the address of the forwarder
1130 or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
1131 target. This is necessary because it may be impossible for the local
1132 <application>Junkbuster</application> to determine the address of the
1133 ultimate target (that's often what gateways are used for).
1137 Here are a few examples to show how the ACL features work:
1141 <quote>localhost</quote> is OK -- no DST_ADDR implies that
1142 <emphasis>ALL</emphasis> destination addresses are OK:
1149 <emphasis>permit-access localhost</emphasis>
1156 A silly example to illustrate permitting any host on the class-C subnet with
1157 <application>Junkbuster</application> to go anywhere:
1164 <emphasis>permit-access www.junkbusters.com/24</emphasis>
1171 Except deny one particular IP address from using it at all:
1178 <emphasis>deny-access ident.junkbusters.com</emphasis>
1185 You can also specify an explicit network address and subnet mask.
1186 Explicit addresses do not have to be resolved to be used.
1193 <emphasis>permit-access 207.153.200.0/24</emphasis>
1200 A subnet mask of 0 matches anything, so the next line permits everyone.
1207 <emphasis>permit-access 0.0.0.0/0</emphasis>
1214 Note, you <emphasis>cannot</emphasis> say:
1221 <emphasis>permit-access .org</emphasis>
1228 to allow all *.org domains. Every IP address listed must resolve fully.
1232 An ISP may want to provide a <application>Junkbuster</application> that is
1233 accessible by <quote>the world</quote> and yet restrict use of some of their
1234 private content to hosts on its internal network (i.e. its own subscribers).
1235 Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
1236 bit netmask). This is how they could do it:
1243 <emphasis>permit-access 0.0.0.0/0 0.0.0.0/0</emphasis> # other clients can go anywhere
1244 # with the following exceptions:
1246 <emphasis>deny-access</emphasis> 0.0.0.0/0 123.124.0.0/16 # block all external requests for
1247 # sites on the ISP's network
1249 <emphasis>permit 0.0.0.0/0 www.my_isp.com</emphasis> # except for the ISP's main
1252 <emphasis>permit 123.124.0.0/16 0.0.0.0/0</emphasis> # the ISP's clients can go
1260 Note that if some hostnames are listed with multiple IP addresses,
1261 the primary value returned by DNS (via gethostbyname()) is used. Default:
1262 Anyone can access the proxy.
1267 <!-- ~ End section ~ -->
1270 <!-- ~~~~~ New section ~~~~~ -->
1273 <title>Forwarding</title>
1276 This feature allows chaining of HTTP requests via multiple proxies.
1277 It can be used to better protect privacy and confidentiality when
1278 accessing specific domains by routing requests to those domains
1279 to a special purpose filtering proxy such as lpwa.com. Or to use
1280 a caching proxy to speed up browsing.
1284 It can also be used in an environment with multiple networks to route
1285 requests via multiple gateways allowing transparent access to multiple
1286 networks without having to modify browser configurations.
1290 Also specified here are SOCKS proxies. <application>Junkbuster</application>
1291 SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
1292 hostname using DNS on the SOCKS server, not our local DNS client.
1296 The syntax of each line is:
1303 <emphasis>forward target_domain[:port] http_proxy_host[:port]</emphasis>
1304 <emphasis>forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1305 <emphasis>forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1312 If http_proxy_host is <quote>.</quote>, then requests are not forwarded to a
1313 HTTP proxy but are made directly to the web servers.
1317 Lines are checked in sequence, and the last match wins.
1321 There is an implicit line equivalent to the following, which specifies that
1322 anything not finding a match on the list is to go out without forwarding
1323 or gateway protocol, like so:
1330 <emphasis>forward .* . </emphasis># implicit
1337 In the following common configuration, everything goes to Lucent's LPWA,
1338 except SSL on port 443 (which it doesn't handle):
1345 <emphasis>forward .* lpwa.com:8000</emphasis>
1346 <emphasis>forward :443 .</emphasis>
1353 See the FAQ for instructions on how to automate the login procedure for LPWA.
1354 Some users have reported difficulties related to LPWA's use of
1355 <quote>.</quote> as the last element of the domain, and have said that this
1356 can be fixed with this:
1363 <emphasis>forward lpwa. lpwa.com:8000</emphasis>
1370 (NOTE: the syntax for specifiying target_domain has changed since the
1371 previous paragraph was written -- it will not work now. More information
1376 In this fictitious example, everything goes via an ISP's caching proxy,
1377 except requests to that ISP:
1384 <emphasis>forward .* caching.myisp.net:8000</emphasis>
1385 <emphasis>forward myisp.net .</emphasis>
1392 For the @home network, we're told the forwarding configuration is this:
1400 <emphasis>forward .* proxy:8080</emphasis>
1407 Also, we're told they insist on getting cookies and JavaScript, so you should
1408 add home.com to the cookie file. We consider JavaScript a security risk.
1409 Java need not be enabled.
1413 In this example direct connections are made to all <quote>internal</quote>
1414 domains, but everything else goes through Lucent's LPWA by way of the
1415 company's SOCKS gateway to the Internet.
1422 <emphasis>forward-socks4 .* lpwa.com:8000 firewall.my_company.com:1080</emphasis>
1423 <emphasis>forward my_company.com .</emphasis>
1430 This is how you could set up a site that always uses SOCKS but no forwarders:
1437 <emphasis>forward-socks4a .* . firewall.my_company.com:1080</emphasis>
1444 An advanced example for network administrators:
1448 If you have links to multiple ISPs that provide various special content to
1449 their subscribers, you can configure forwarding to pass requests to the
1450 specific host that's connected to that ISP so that everybody can see all
1451 of the content on all of the ISPs.
1455 This is a bit tricky, but here's an example:
1460 host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
1461 isp-b.com. host-a can run a <application>Junkbuster</application> proxy with
1462 forwarding like this:
1469 <emphasis>forward .* .</emphasis>
1470 <emphasis>forward isp-b.com host-b:8000</emphasis>
1477 host-b can run a <application>Junkbuster</application> proxy with forwarding
1485 <emphasis>forward .* .</emphasis>
1486 <emphasis>forward isp-a.com host-a:8000</emphasis>
1493 Now, <emphasis>anyone</emphasis> on the Internet (including users on host-a
1494 and host-b) can set their browser's proxy to <emphasis>either</emphasis>
1495 host-a or host-b and be able to browse the content on isp-a or isp-b.
1499 Here's another practical example, for University of Kent at
1500 Canterbury students with a network connection in their room, who
1501 need to use the University's Squid web cache.
1508 <emphasis>forward *. ssbcache.ukc.ac.uk:3128</emphasis> # Use the proxy, except for:
1509 <emphasis>forward .ukc.ac.uk . </emphasis> # Anything on the same domain as us
1510 <emphasis>forward * . </emphasis> # Host with no domain specified
1511 <emphasis>forward 129.12.*.* . </emphasis> # A dotted IP on our /16 network.
1512 <emphasis>forward 127.*.*.* . </emphasis> # Loopback address
1513 <emphasis>forward localhost.localdomain . </emphasis> # Loopback address
1514 <emphasis>forward www.ukc.mirror.ac.uk . </emphasis> # Specific host
1521 If you intend to chain <application>Junkbuster</application> and
1522 <application>squid</application> locally, then chain as
1523 <literal>browser -> squid -> junkbuster</literal> is the recommended way.
1527 Your squid configuration could then look like this:
1534 # Define junkbuster as parent cache
1535 <!-- per feedback from user...
1536 cache_peer 127.0.0.1 8000 parent 0 no-query
1538 cache_peer 127.0.0.1 parent 8000 0 no-query
1540 # Define ACL for protocol FTP
1543 # Do not forward ACL FTP to junkbuster
1544 always_direct allow FTP
1546 # Do not forward ACL CONNECT (https) to junkbuster
1547 always_direct allow CONNECT
1549 # Forward the rest to junkbuster
1550 never_direct allow all
1558 <!-- ~ End section ~ -->
1561 <!-- ~~~~~ New section ~~~~~ -->
1564 <title>Windows GUI Options</title>
1566 Removed references to Win32. HB 09/23/01
1569 <application>Junkbuster</application> has a number of options specific to the
1570 Windows GUI interface:
1574 If <quote>activity-animation</quote> is set to 1, the
1575 <application>Junkbuster</application> icon will animate when
1576 <quote>Junkbuster</quote> is active. To turn off, set to 0.
1583 <emphasis>activity-animation 1</emphasis>
1590 If <quote>log-messages</quote> is set to 1,
1591 <application>Junkbuster</application> will log messages to the console
1599 <emphasis>log-messages 1</emphasis>
1606 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
1607 i.e. the amount of memory used for the log messages displayed in the
1608 console window, will be limited to <quote>log-max-lines</quote> (see below).
1612 Warning: Setting this to 0 will result in the buffer to grow infinitely and
1613 eat up all your memory!
1620 <emphasis>log-buffer-size 1</emphasis>
1627 <application>log-max-lines</application> is the maximum number of lines held
1628 in the log buffer. See above.
1635 <emphasis>log-max-lines 200</emphasis>
1642 If <quote>log-highlight-messages</quote> is set to 1,
1643 <application>Junkbuster</application> will highlight portions of the log
1644 messages with a bold-faced font:
1651 <emphasis>log-highlight-messages 1</emphasis>
1658 The font used in the console window:
1665 <emphasis>log-font-name Comic Sans MS</emphasis>
1672 Font size used in the console window:
1679 <emphasis>log-font-size 8</emphasis>
1686 <quote>show-on-task-bar</quote> controls whether or not
1687 <application>Junkbuster</application> will appear as a button on the Task bar
1695 <emphasis>show-on-task-bar 0</emphasis>
1702 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
1703 button will minimize <application>Junkbuster</application> instead of closing
1704 the program (close with the exit option on the File menu).
1711 <emphasis>close-button-minimizes 1</emphasis>
1718 The <quote>hide-console</quote> option is specific to the MS-Win console
1719 version of <application>JunkBuster</application>. If this option is used,
1720 <application>Junkbuster</application> will disconnect from and hide the
1737 <!-- ~ End section ~ -->
1740 <!-- ~~~~~ New section ~~~~~ -->
1741 <sect2 id="actionsfile">
1742 <title>The Actions File</title>
1745 The <quote>ijb.action</quote> file (formerly
1746 <filename>actionsfile</filename>) is used to define what actions
1747 <application>Junkbuster</application> takes, and thus determines how images,
1748 cookies and various other aspects of HTTP content and transactions are
1749 handled. Images can be anything you want, including ads, banners, or just
1750 some obnoxious image that you would rather not see. Cookies can be accepted
1751 or rejected, or accepted only during the current browser session (i.e.
1752 not written to disk). Changes to <filename>ijb.action</filename> should
1753 be immediately visible to <application>Junkbuster</application> without
1754 the need to restart.
1758 To determine which actions apply to a request, the URL of the request is
1759 compared to all patterns in this file. Every time it matches, the list of
1760 applicable actions for the URL is incrementally updated. You can trace
1761 this process by visiting <ulink
1762 url="http://i.j.b/show-url-info">http://i.j.b/show-url-info</ulink>.
1766 The actions file can be edited with a browser by loading
1767 <ulink url="http://i.j.b/">http://i.j.b/</ulink>, and then select
1768 <quote>Edit Actions</quote>.
1772 There are four types of lines in this file: comments (begin with a
1773 <quote>#</quote> character), actions, aliases and patterns, all of which are
1774 explained below, as well as the configuration file syntax that
1775 <application>Junkbuster</application> understands.
1780 <!-- ~~~~~ New section ~~~~~ -->
1782 <title>URL Domain and Path Syntax</title>
1784 Generally, a pattern has the form <domain>/<path>, where both the
1785 <domain> and <path> part are optional. If you only specify a
1786 domain part, the <quote>/</quote> can be left out:
1790 <emphasis>www.example.com</emphasis> - is a domain only pattern and will match any request to
1791 <quote>www.example.com</quote>.
1795 <emphasis>www.example.com/</emphasis> - means exactly the same.
1799 <emphasis>www.example.com/index.html</emphasis> - matches only the single
1800 document <quote>/index.html</quote> on <quote>www.example.com</quote>.
1804 <emphasis>/index.html</emphasis> - matches the document <quote>/index.html</quote>, regardless of
1809 <emphasis>index.html</emphasis> - matches nothing, since it would be
1810 interpreted as a domain name and there is no top-level domain called
1811 <quote>.html</quote>.
1815 The matching of the domain part offers some flexible options: if the
1816 domain starts or ends with a dot, it becomes unanchored at that end.
1821 <emphasis>.example.com</emphasis> - matches any domain that <emphasis>ENDS</emphasis> in
1822 <quote>.example.com</quote>.
1826 <emphasis>www.</emphasis> - matches any domain that <emphasis>STARTS</emphasis> with
1831 Additionally, there are wildcards that you can use in the domain names
1832 themselves. They work pretty similar to shell wildcards: <quote>*</quote>
1833 stands for zero or more arbitrary characters, <quote>?</quote> stands for
1834 any single character. And you can define charachter classes in square
1835 brackets and they can be freely mixed:
1839 <emphasis>ad*.example.com</emphasis> - matches <quote>adserver.example.com</quote>,
1840 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>.
1844 <emphasis>*ad*.example.com</emphasis> - matches all of the above, and then some.
1848 <emphasis>.?pix.com</emphasis> - matches <quote>www.ipix.com</quote>,
1849 <quote>pictures.epix.com</quote>, <quote>a.b.c.d.e.upix.com</quote>, etc.
1853 <emphasis>www[1-9a-ez].example.com</emphasis> - matches <quote>www1.example.com</quote>,
1854 <quote>www4.example.com</quote>, <quote>wwwd.example.com</quote>,
1855 <quote>wwwz.example.com</quote>, etc., but <emphasis>not</emphasis>
1856 <quote>wwww.example.com</quote>.
1860 If <application>Junkbuster</application> was compiled with
1861 <quote>pcre</quote> support (default), Perl compatible regular expressions
1862 can be used. See the <filename>pcre/docs/</filename> direcory or <quote>man
1863 perlre</quote> (also available on <ulink
1864 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>)
1865 for details. A brief discussion of regular expressions is in the
1866 <link linkend="regex">Appendix</link>. For instance:
1870 <emphasis>/.*/advert[0-9]+\.jpe?g</emphasis> - would match a URL from any
1871 domain, with any path that includes <quote>advert</quote> followed
1872 immediately by one or more digits, then a <quote>.</quote> and ending in
1873 either <quote>jpeg</quote> or <quote>jpg</quote>. So we match
1874 <quote>example.com/ads/advert2.jpg</quote>, and
1875 <quote>www.example.com/ads/banners/advert39.jpeg</quote>, but not
1876 <quote>www.example.com/ads/banners/advert39.gif</quote> (no gifs in the
1881 Please note that matching in the path is case
1882 <emphasis>INSENSITIVE</emphasis> by default, but you can switch to case
1883 sensitive at any point in the pattern by using the
1884 <quote>(?-i)</quote> switch:
1888 <emphasis>www.example.com/(?-i)PaTtErN.*</emphasis> - will match only
1889 documents whose path starts with <quote>PaTtErN</quote> in
1890 <emphasis>exactly</emphasis> this capitalization.
1895 <!-- ~ End section ~ -->
1899 <!-- ~~~~~ New section ~~~~~ -->
1902 <title>Actions</title>
1904 Actions are enabled if preceded with a <quote>+</quote>, and disabled if
1905 preceded with a <quote>-</quote>. Actions are invoked by enclosing the
1906 action name in curly braces (e.g. {+some_action}), followed by a list of
1907 URLs to which the action applies. There are three classes of actions:
1915 Boolean (e.g. <quote>+/-block</quote>):
1921 <emphasis>{+name}</emphasis> # enable this action
1922 <emphasis>{-name}</emphasis> # disable this action
1932 Parameterized (e.g. <quote>+/-hide-user-agent</quote>):
1938 <emphasis>{+name{param}}</emphasis> # enable action and set parameter to <quote>param</quote>
1939 <emphasis>{-name}</emphasis> # disable action
1948 Multi-value (e.g. <quote>{+/-add-header{Name: value}}</quote>, <quote>{+/-wafer{name=value}}</quote>):
1954 <emphasis>{+name{param}}</emphasis> # enable action and add parameter <quote>param</quote>
1955 <emphasis>{-name{param}}</emphasis> # remove the parameter <quote>param</quote>
1956 <emphasis>{-name}</emphasis> # disable this action totally
1967 If nothing is specified in this file, no <quote>actions</quote> are taken.
1968 So in this case <application>JunkBuster</application> would just be a
1969 normal, non-blocking, non-anonymizing proxy. You must specifically
1970 enable the privacy and blocking features you need (although the
1971 provided default <filename>ijb.action</filename> file will
1972 give a good starting point).
1976 Later defined actions always over-ride earlier ones. For multi-valued
1977 actions, the actions are applied in the order they are specified.
1981 The list of valid <application>Junkbuster</application> <quote>actions</quote> are:
1989 Add the specified HTTP header, which is not checked for validity.
1990 You may specify this many times to specify many different headers:
1996 <emphasis>+add-header{Name: value}</emphasis>
2006 Block this URL totally.
2012 <emphasis>+block</emphasis>
2022 De-animate all animated GIF images, i.e. reduce them to their last frame.
2023 This will also shrink the images considerably (in bytes, not pixels!). If
2024 the option <quote>first</quote> is given, the first frame of the animation
2025 is used as the replacement. If <quote>last</quote> is given, the last frame
2026 of the animation is used instead, which propably makes more sense for most
2027 banner animations, but also has the risk of not showing the entire last
2028 frame (if it is only a delta to an earlier frame).
2034 <emphasis>+deanimate-gifs{last}</emphasis>
2035 <emphasis>+deanimate-gifs{first}</emphasis>
2044 <quote>+downgrade</quote> will downgrade HTTP/1.1 client requests to
2045 HTTP/1.0 and downgrade the responses as well. Use this action for servers
2046 that use HTTP/1.1 protocol features that
2047 <application>Junkbuster</application> doesn't handle well yet. HTTP/1.1
2048 is only partially implemented. Default is not to downgrade requests.
2054 <emphasis>+downgrade</emphasis>
2063 Many sites, like yahoo.com, don't just link to other sites. Instead, they
2064 will link to some script on their own server, giving the destination as a
2065 parameter, which will then redirect you to the final target. URLs resulting
2066 from this scheme typically look like:
2067 http://some.place/some_script?http://some.where-else.
2070 Sometimes, there are even multiple consecutive redirects encoded in the
2071 URL. These redirections via scripts make your web browing more traceable,
2072 since the server from which you follow such a link can see where you go to.
2073 Apart from that, valuable bandwidth and time is wasted, while your browser
2074 ask the server for one redirect after the other. Plus, it feeds the
2078 The <quote>+fast-redirects</quote> option enables interception of these
2079 requests by <application>Junkbuster</application>, who will cut off all but
2080 the last valid URL in the request and send a local redirect back to your
2081 browser without contacting the remote site.
2087 <emphasis>+fast-redirects</emphasis>
2096 Filter the website through the re_filterfile:
2102 <emphasis>+filter{filename}</emphasis>
2111 Block any existing X-Forwarded-for header, and do not add a new one:
2117 <emphasis>+hide-forwarded</emphasis>
2126 If the browser sends a <quote>From:</quote> header containing your e-mail
2127 address, this either completely removes the header (<quote>block</quote>), or
2128 changes it to the specified e-mail address.
2134 <emphasis>+hide-from{block}</emphasis>
2135 <emphasis>+hide-from{spam@sittingduck.xqq}</emphasis>
2144 Don't send the <quote>Referer:</quote> (sic) header to the web site. You
2145 can block it, forge a URL to the same server as the request (which is
2146 preferred because some sites will not send images otherwise) or set it to a
2147 constant string of your choice.
2153 <emphasis>+hide-referer{block}</emphasis>
2154 <emphasis>+hide-referer{forge}</emphasis>
2155 <emphasis>+hide-referer{http://nowhere.com}</emphasis>
2164 Alternative spelling of <quote>+hide-referer</quote>. It has the same
2165 parameters, and can be freely mixed with, <quote>+hide-referer</quote>.
2166 (<quote>referrer</quote> is the correct English spelling, however the HTTP
2167 specification has a bug - it requires it to be spelled <quote>referer</quote>.)
2173 <emphasis>+hide-referrer{...}</emphasis>
2182 Change the <quote>User-Agent:</quote> header so web servers can't tell your
2183 browser type. Warning! This breaks many web sites. Specify the
2184 user-agent value you want. Example, pretend to be using Netscape on
2191 <emphasis>+hide-user-agent{Mozilla (X11; I; Linux 2.0.32 i586)}</emphasis>
2198 Or to identify yourself explicitly as a <quote>Junkbuster</quote> user:
2204 <emphasis>+hide-user-agent{JunkBuster/1.0}</emphasis>
2209 (Don't change the version number from 1.0 - after all, why tell them?)
2216 <emphasis>+hide-user-agent{browser-type}</emphasis>
2226 Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
2227 in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
2228 See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
2234 <emphasis>+image</emphasis>
2243 Decides what to do with URLs that end up tagged with <quote>{+block
2244 +image}</quote>. There are 4 options. <quote>-image-blocker</quote> will
2245 send a HTML <quote>blocked</quote> page, usually resulting in a
2246 <quote>broken image</quote> icon. <quote>+image-blocker{logo}</quote> will
2247 send a <quote>JunkBuster</quote> image.
2248 <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF image.
2249 And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a HTTP
2250 temporary redirect to the specified image. This has the advantage of the
2251 icon being being cached by the browser, which will speed up the display.
2257 <emphasis>+image-blocker{logo}</emphasis>
2258 <emphasis>+image-blocker{blank}</emphasis>
2259 <emphasis>+image-blocker{http://i.j.b/send-banner}</emphasis>
2268 By default (i.e. in the absence of a <quote>+limit-connect</quote>
2269 action), <application>Junkbuster</application> will only allow CONNECT
2270 requests to port 443, which is the standard port for https as a
2275 The CONNECT methods exists in HTTP to allow access to secure websites
2276 (https:// URLs) through proxies. It works very simply: the proxy
2277 connects to the server on the specified port, and then short-circuits
2278 its connections to the client <emphasis>and</emphasis> to the remote proxy.
2279 This can be a big security hole, since CONNECT-enabled proxies can
2280 be abused as TCP relays very easily.
2284 If you want to allow CONNECT for more ports than this, or want to forbid
2285 CONNECT altogether, you can specify a comma separated list of ports and
2286 port ranges (the latter using dashes, with the minimum defaulting to 0 and
2294 <emphasis>+limit-connect{443} # This is the default and need no be specified.</emphasis>
2295 <emphasis>+limit-connect{80,443} # Ports 80 and 443 are OK.</emphasis>
2296 <emphasis>+limit-connect{-3, 7, 20-100, 500-} # Port less than 3, 7, 20 to 100</emphasis>
2297 <emphasis> #and above 500 are OK.</emphasis>
2307 <quote>+no-compression</quote> prevents the website from compressing the
2308 data. Some websites do this, which can be a problem for
2309 <application>Junkbuster</application>, since <quote>+filter</quote>,
2310 <quote>+no-popup</quote> and <quote>+gif-deanimate</quote> will not work on
2311 compressed data. This will slow down connections to those websites,
2312 though. Default is <quote>nocompression</quote> is turned on.
2319 <emphasis>+nocompression</emphasis>
2328 If the website sets cookies, <quote>no-cookies-keep</quote> will make sure
2329 they are erased when you exit and restart your web browser. This makes
2330 profiling cookies useless, but won't break sites which require cookies so
2331 that you can log in for transactions. Default: on.
2337 <emphasis>+no-cookies-keep</emphasis>
2346 Prevent the website from reading cookies:
2352 <emphasis>+no-cookies-read</emphasis>
2361 Prevent the website from setting cookies:
2367 <emphasis>+no-cookies-set</emphasis>
2376 Filter the website through a built-in filter to disable those obnoxious
2377 JavaScript pop-up windows via window.open(), etc. The two alternative
2378 spellings are equivalent.
2384 <emphasis>+no-popup</emphasis>
2385 <emphasis>+no-popups</emphasis>
2394 This action only applies if you are using a <filename>jarfile</filename>
2395 for saving cookies. It sends a cookie to every site stating that you do not
2396 accept any copyright on cookies sent to you, and asking them not to track
2397 you. Of course, this is a (relatively) unique header they could use to
2404 <emphasis>+vanilla-wafer</emphasis>
2413 This allows you to add an arbitrary cookie. It can be specified multiple
2414 times in order to add as many cookies as you like.
2420 <emphasis>+wafer{name=value}</emphasis>
2431 The meaning of any of the above is reversed by preceding the action with a
2432 <quote>-</quote>, in place of the <quote>+</quote>.
2440 Turn off cookies by default, then allow a few through for specified sites:
2447 # Turn off all persistant cookies
2448 { +no-cookies-read }
2450 # Allow cookies for this browser session ONLY
2451 { +no-cookies-keep }
2453 # Execeptions to the above, sites that benefit from persistant cookies
2454 { -no-cookies-read }
2456 { -no-cookies-keep }
2463 # Alternative way of saying the same thing
2464 {-no-cookies-set -no-cookies-read -no-cookies-keep}
2473 Now turn off <quote>fast redirects</quote>, and then we allow two exceptions:
2483 # Reverse it for these two sites, which don't work right without it.
2485 www.ukc.ac.uk/cgi-bin/wac\.cgi\?
2493 Turn on page filtering, with one exception for sourceforge:
2500 # Run everything through the default filter file (<filename>re_filterfile</filename>):
2503 # But please don't re_filter code from sourceforge!
2505 .cvs.sourceforge.net
2512 Now some URLs that we want <quote>blocked</quote>, ie we won't see them.
2513 Many of these use regular expressions that will expand to match multiple
2523 /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g))
2524 /.*/(.*[-_.])?count(er)?(\.cgi|\.dll|\.exe|[?/])
2525 /.*/(ng)?adclient\.cgi
2526 /.*/(plain|live|rotate)[-_.]?ads?/
2527 /.*/(sponsor)s?[0-9]?/
2528 /.*/_?(plain|live)?ads?(-banners)?/
2530 /.*/ad(sdna_image|gifs?)/
2531 /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe)
2535 /.*/adv((er)?ts?|ertis(ing|ements?))?/
2539 /.*/cgi-bin/centralad/getimage
2540 /.*/images/addver\.gif
2541 /.*/images/marketing/.*\.(gif|jpe?g)
2545 /.*/sponsors?[0-9]?/
2546 /.*/advert[0-9]+\.jpg
2553 /graphics/defaultAd/
2555 /image\.ng/transactionID
2556 /images/.*/.*_anim\.gif # alvin brattli
2557 /ip_img/.*\.(gif|jpe?g)
2561 /cgi-bin/nph-adclick.exe/
2562 /.*/Image/BannerAdvertising/
2564 /.*/adlib/server\.cgi
2573 <!-- ~ End section ~ -->
2576 <!-- ~~~~~ New section ~~~~~ -->
2578 <title>Aliases</title>
2580 Custom <quote>actions</quote>, known to <application>Junkbuster</application>
2581 as <quote>aliases</quote>, can be defined by combining other <quote>actions</quote>.
2582 These can in turn be invoked just like the built-in <quote>actions</quote>.
2583 Currently, an alias can contain any character except space, tab, <quote>=</quote>,
2584 <quote>{</quote> or <quote>}</quote>. But please use only <quote>a</quote>-
2585 <quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
2586 <quote>-</quote>. Alias names are not case sensitive, and
2587 <emphasis>must be defined before anything</emphasis> else in the
2588 <filename>ijb.action</filename>file ! And there can only be one set of
2589 <quote>aliases</quote> defined.
2593 Now let's define a few aliases:
2600 # Useful customer aliases we can use later. These must come first!
2602 +no-cookies = +no-cookies-set +no-cookies-read
2603 -no-cookies = -no-cookies-set -no-cookies-read
2604 fragile = -block -no-cookies -filter -fast-redirects -hide-referer -no-popups
2605 shop = -no-cookies -filter -fast-redirects
2606 +imageblock = +block +image
2608 #For people who don't like to type too much: ;-)
2611 c2 = -no-cookies-set +no-cookies-read
2612 c3 = +no-cookies-set -no-cookies-read
2613 #... etc. Customize to your heart's content.
2620 Some examples using our <quote>shop</quote> and <quote>fragile</quote>
2628 # These sites are very complex and require
2629 # minimal interference.
2631 .office.microsoft.com
2632 .windowsupdate.microsoft.com
2635 # Shopping sites - still want to block ads.
2638 .worldpay.com # for quietpc.com
2642 # These shops require pop-ups
2654 <!-- ~ End section ~ -->
2657 <!-- ~~~~~ New section ~~~~~ -->
2658 <sect2 id="filterfile">
2659 <title>The Filter File</title>
2661 The filter file defines what filtering of web pages
2662 <application>Junkbuster</application> does. The default filter file is
2663 <filename>re_filterfile</filename>, located in the config directory. In this
2664 file, <emphasis>any document content</emphasis>, whether viewable text or
2665 embedded non-visible content, can be changed.
2669 This file uses regular expressions to alter or remove any string in the
2670 target page. Some examples from the included default <filename>re_filterfile</filename>:
2674 Stop web pages from displaying annoying messages in the status bar by
2675 deleting such references:
2682 # The status bar is for displaying link targets, not pointless buzzwords.
2683 # Again, check it out on http://www.airport-cgn.de/.
2684 s/status='.*?';*//ig
2691 Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
2692 <quote>MicroSuck</quote>:
2699 s/microsoft(?!.com)/MicroSuck/ig
2706 Kill those auto-refresh tags:
2713 # Kill refresh tags. I like to refresh myself. Manually.
2714 # check it out on http://www.airport-cgn.de/ and go to the arrivals page.
2716 s/<meta[^>]*http-equiv[^>]*refresh.*URL=([^>]*?)"?>/<link rev="x-refresh" href=$1>/i
2717 s/<meta[^>]*http-equiv="?page-enter"?[^>]*content=[^>]*>/<!--no page enter for me-->/i
2725 <!-- ~ End section ~ -->
2729 <!-- ~~~~~ New section ~~~~~ -->
2732 <title>Templates</title>
2734 When <application>Junkbuster</application> displays one of its internal
2735 pages, such as a 404 Not Found error page, it uses the appropriate template.
2736 On Linux, BSD, and Unix, these are locate in
2737 <filename>/etc/junkbuster/templates</filename> by default. These may be
2738 customized, if desired.
2745 <!-- ~ End section ~ -->
2749 <!-- ~~~~~ New section ~~~~~ -->
2750 <sect1 id="quickstart"><title>Quickstart to Using Junkbuster</title>
2752 Install package, then run and enjoy! <application>Junbuster</application>
2753 accepts only one command line option -- the configuration file to be
2754 used. Example Unix startup command:
2760 # /usr/sbin/junkbuster /etc/junkbuster/config
2766 An init script is provided for SuSE and Redhat.
2770 For for SuSE: /etc/rc.d/junkbuster start
2774 For RedHat: /etc/rc.d/init.d/junkbuster start
2779 If no configuration file is specified on the command line,
2780 <application>Junkbuster</application> will look for a file named
2781 <filename>config</filename> in the current directory. Except on Amiga where
2782 it will look for <filename>AmiTCP:db/junkbuster/config</filename> and Win32
2783 where it will try <filename>config.txt</filename>. If no file is specified
2784 on the command line and no default configuration file can be found,
2785 <application>Junkbuster</application> will fail to start.
2789 Be sure your browser is set to use the proxy which is by default at
2790 localhost, port 8000. With <application>Netscape</application> (and
2791 <application>Mozilla</application>), this can be set under <literal>Edit
2792 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</literal>.
2793 For <application>Internet Explorer</application>: <literal>Tools >
2794 Internet Properties -> Connections -> LAN Setting</literal>. Then,
2795 check <quote>Use Proxy</quote> and fill in the appropriate info (Address:
2796 localhost, Port: 8000). Include if HTTPS proxy support too.
2800 The included default configuration files should give a reasonable starting
2801 point, though may be somewhat aggressive in blocking junk. You will probably
2802 want to keep an eye out for sites that require persistant cookies, and add these to
2803 <filename>ijb.action</filename> as needed. By default, most of these will
2804 be accepted only during the current browser session, until you add them to
2805 the configuration. If you want the browser to handle this instead, you will
2806 need to edit <filename>ijb.action</filename> and disable this feature. If you
2807 use more than one browser, it would make more sense to let
2808 <application>Junkbuster</application> handle this. In which case, the
2809 browser(s) should be set to accept all cookies.
2813 If a particular site shows problems loading properly, try adding it
2814 to the <literal>{fragile}</literal> section of
2815 <filename>ijb.action</filename>. This will turn off most actions for
2820 HTTP/1.1 support is not fully implemented. If browsers that
2821 support HTTP/1.1 (like <application>Mozilla</application> or recent versions
2822 of I.E.) experience problems, you might try to force HTTP/1.0 compatiblity.
2823 For Mozilla, look under <literal>Edit -> Preferences -> Debug ->
2824 Networking</literal>. Or set the <quote>+downgrade</quote> config option in
2825 <filename>ijb.action</filename>.
2829 After running <application>Junkbuster</application> for a while, you can
2830 start to fine tune the configuration to suit your personal, or site,
2831 preferences and requirements. There are many, many aspects that can
2832 be customized. <quote>Actions</quote> (as specified in <filename>ijb.action</filename>)
2833 can be adjusted by pointing your browser to
2834 <ulink url="http://i.j.b/">http://i.j.b/</ulink>,
2835 and then follow the link to <quote>edit the actions list</quote>.
2836 (This is an internal page and does not require Internet access.)
2840 In fact, various aspects of <application>Junkbuster</application>
2841 configuration can be viewed from this page, including
2842 current configuration parameters, source code version numbers,
2843 the browser's request headers, and <quote>actions</quote> that apply
2844 to a given URL. In addition to the <filename>ijb.action</filename> file
2845 editor mentioned above, <application>Junkbuster</application> can also
2846 be turned <quote>on</quote> and <quote>off</quote> from this page.
2850 If you encounter problems, please verify it is a
2851 <application>Junkbuster</application> bug, by disabling
2852 <application>Junkbuster</application>, and then trying the same page.
2853 Also, try another browser if possible to eliminate browser or site
2854 problems. Before reporting it as a bug, see if there is not a configuration
2855 option that is enabled that is causing the page not to load. You can
2856 then add an exception for that page or site. If a bug, please report it to
2857 the developers (see below).
2863 <!-- ~~~~~ New section ~~~~~ -->
2864 <sect1 id="contact"><title>Contact the Developers</title>
2867 To be filled. mention the support forums as the primary channel of
2868 communication (bugs, feature requests, etc.)
2870 Feature requests and other questions should be posted to the <ulink
2871 url="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse">Feature
2872 request page</ulink> at SourceForge. There is also an archive there.
2876 Anyone interested in actively participating in development and related
2877 discussions can join the appropriate mailing list
2878 <ulink url="http://sourceforge.net/mail/?group_id=11118">here</ulink>.
2879 Archives are available here too.
2883 Please report bugs, using the form at
2884 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge</ulink>.
2885 Please try to verify that it is a <application>Junkbuster</application> bug,
2886 and not a browser or site bug first. Also, check to make sure this is not
2887 already a known bug.
2893 <!-- ~~~~~ New section ~~~~~ -->
2894 <sect1 id="copyright"><title>Copyright and History</title>
2897 <title>License</title>
2899 <application>Internet Junkbuster</application> is free software; you can
2900 redistribute it and/or modify it under the terms of the GNU General Public
2901 License as published by the Free Software Foundation; either version 2 of the
2902 License, or (at your option) any later version.
2906 This program is distributed in the hope that it will be useful, but WITHOUT
2907 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
2908 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
2909 details, which is available from <ulink
2910 url="http://www.gnu.org/copyleft/gpl.html">the Free Software Foundation,
2911 Inc</ulink>, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
2916 <!-- ~ End section ~ -->
2919 <!-- ~~~~~ New section ~~~~~ -->
2922 <title>History</title>
2924 <application>Junkbuster</application> was originally written by Anonymous
2926 url="http://www.junkbusters.com/ht/en/ijbfaq.html">JunkBusters
2927 Corporation</ulink>, and was released as free open-source software under the
2928 GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
2929 Waldherr</ulink> made many improvements, and started the <ulink
2930 url="http://sourceforge.net/projects/ijbswa/">SourceForge project</ulink> to
2931 rekindle development. The last stable release was v2.0.2, which has now
2939 <!-- ~~~~~ New section ~~~~~ -->
2940 <sect1 id="seealso"><title>See also</title>
2945 <ulink url="http://sourceforge.net/projects/ijbswa">http://sourceforge.net/projects/ijbswa</ulink>
2950 <ulink url="http://ijbswa.sourceforge.net/">http://ijbswa.sourceforge.net/</ulink>
2955 <ulink url="http://i.j.b/">http://i.j.b/</ulink>
2960 <ulink url="http://www.junkbusters.com/ht/en/cookies.html">http://www.junkbusters.com/ht/en/cookies.html</ulink>
2965 <ulink url="http://www.waldherr.org/junkbuster/">http://www.waldherr.org/junkbuster/</ulink>
2970 <ulink url="http://privacy.net/analyze/">http://privacy.net/analyze/</ulink>
2975 <ulink url="http://www.squid-cache.org/">http://www.squid-cache.org/</ulink>
2984 <!-- ~~~~~ New section ~~~~~ -->
2985 <sect1 id="appendix"><title>Appendix</title>
2988 <!-- ~~~~~ New section ~~~~~ -->
2990 <title>Regular Expressions</title>
2992 <application>Junkbuster</application> can use <quote>regular expressions</quote>
2993 in various config files. Assuming support for <quote>pcre</quote> (Perl
2994 Compatible Regular Expressions) is compiled in, which is the default. Such
2995 configuration directives do not require regular expressions, but they can be
2996 used to increase flexibility by matching a pattern with wildcards against
3001 If you are reading this, you probably don't understand what <quote>regular
3002 expressions</quote> are, or what they can do. So this will be a very brief
3003 introduction only. A full explanation would require a book ;-)
3007 <quote>Regular expressions</quote> is a way of matching one character
3008 expression against another to see if it matches or not. One of the
3009 <quote>expressions</quote> is a literal string of readable characters
3010 (letter, numbers, etc), and the other is a complex string of literal
3011 characters combined with wildcards, and other special characters, called
3012 metacharacters. The <quote>metacharacters</quote> have special meanings and
3013 are used to build the complex pattern to be matched against. Perl Compatible
3014 Regular Expressions is an enhanced form of the regular expression language
3015 with backward compatibility.
3019 To make a simple analogy, we do something similar when we use wildcard
3020 characters when listing files with the <command>dir</command> command in DOS.
3021 <literal>*.*</literal> matches all filenames. The <quote>special</quote>
3022 character here is the asterik which matches any and all characters. We can be
3023 more specific and use <literal>?</literal> to match just individual
3024 characters. So <quote>dir file?.text</quote> would match
3025 <quote>file1.txt</quote>, <quote>file2.txt</quote>, etc. We are pattern
3026 matching, using a similar technique to <quote>regular expressions</quote>!
3030 Regular expressions do essentially the same thing, but are much, much more
3031 powerful. There are many more <quote>special characters</quote> and ways of
3032 building complex patterns however. Let's look at a few of the common ones,
3033 and then some examples:
3038 <emphasis>.</emphasis> - Matches any single character, e.g. <quote>a</quote>,
3039 <quote>A</quote>, <quote>4</quote>, <quote>:</quote>, or <quote>@</quote>.
3045 <emphasis>?</emphasis> - The preceding character or expression is matched ZERO or ONE
3052 <emphasis>+</emphasis> - The preceding character or expression is matched ONE or MORE
3059 <emphasis>*</emphasis> - The preceding character or expression is matched ZERO or MORE
3066 <emphasis>\</emphasis> - The <quote>escape</quote> character denotes that
3067 the following character should be taken literally. This is used where one of the
3068 special characters (e.g. <quote>.</quote>) needs to be taken literally and
3069 not as a special metacharacter.
3075 <emphasis>[]</emphasis> - Characters enclosed in brackets will be matched if
3076 any of the enclosed characters are encountered.
3082 <emphasis>()</emphasis> - Pararentheses are used to group a sub-expression,
3083 or multiple sub-expressions.
3089 <emphasis>|</emphasis> - The <quote>bar</quote> character works like an
3090 <quote>or</quote> conditional statement. A match is successful if the
3091 sub-expression on either side of <quote>|</quote> matches.
3097 <emphasis>s/string1/string2/g</emphasis> - This is used to rewrite strings of text.
3098 <quote>string1</quote> is replaced by <quote>string2</quote> in this
3104 These are just some of the ones you are likely to use when matching URLs with
3105 <application>Junkbuster</application>, and is a long way from a definitive
3106 list. This is enough to get us started with a few simple examples which may
3107 be more illuminating:
3111 <emphasis><literal>/.*/banners/.*</literal></emphasis> - A simple example
3112 that uses the common combination of <quote>.</quote> and <quote>*</quote> to
3113 denote any character, zero or more times. In other words, any string at all.
3114 So we start with a literal forward slash, then our regular expression pattern
3115 (<quote>.*</quote>) another literal forward slash, the string
3116 <quote>banners</quote>, another forward slash, and lastly another
3117 <quote>.*</quote>. We are building
3118 a directory path here. This will match any file with the path that has a
3119 directory named <quote>banners</quote> in it. The <quote>.*</quote> matches
3120 any characters, and this could conceivably be more forward slashes, so it
3121 might expand into a much longer looking path. For example, this could match:
3122 <quote>/eye/hate/spammers/banners/annoy_me_please.gif</quote>, or just
3123 <quote>/banners/annoying.html</quote>, or almost an infinite number of other
3124 possible combinations, just so it has <quote>banners</quote> in the path
3129 A now something a little more complex:
3133 <emphasis><literal>/.*/adv((er)?ts?|ertis(ing|ements?))?/</literal></emphasis> -
3134 We have several literal forward slashes again (<quote>/</quote>), so we are
3135 building another expression that is a file path statement. We have another
3136 <quote>.*</quote>, so we are matching against any conceivable sub-path, just so
3137 it matches our expression. The only true literal that <emphasis>must
3138 match</emphasis> our pattern is <application>adv</application>, together with
3139 the forward slashes. What comes after the <quote>adv</quote> string is the
3144 Remember the <quote>?</quote> means the preceding expression (either a
3145 literal character or anything grouped with <quote>(...)</quote> in this case)
3146 can exist or not, since this means either zero or one match. So
3147 <quote>((er)?ts?|ertis(ing|ements?))</quote> is optional, as are the
3148 individual sub-expressions: <quote>(er)</quote>,
3149 <quote>(ing|ements?)</quote>, and the <quote>s</quote>. The <quote>|</quote>
3150 means <quote>or</quote>. We have two of those. For instance,
3151 <quote>(ing|ements?)</quote>, can expand to match either <quote>ing</quote>
3152 <emphasis>OR</emphasis> <quote>ements?</quote>. What is being done here, is an
3153 attempt at matching as many variations of <quote>advertisement</quote>, and
3154 similar, as possible. So this would expand to match just <quote>adv</quote>,
3155 or <quote>advert</quote>, or <quote>adverts</quote>, or
3156 <quote>advertising</quote>, or <quote>advertisement</quote>, or
3157 <quote>advertisements</quote>. You get the idea. But it would not match
3158 <quote>advertizements</quote> (with a <quote>z</quote>). We could fix that by
3159 changing our regular expression to:
3160 <quote>/.*/adv((er)?ts?|erti(s|z)(ing|ements?))?/</quote>, which would then match
3165 <emphasis><literal>/.*/advert[0-9]+\.(gif|jpe?g)</literal></emphasis> - Again
3166 another path statement with forward slashes. Anything in the square brackets
3167 <quote>[]</quote> can be matched. This is using <quote>0-9</quote> as a
3168 shorthand expression to mean any digit one through nine. It is the same as
3169 saying <quote>0123456789</quote>. So any digit matches. The <quote>+</quote>
3170 means one or more of the preceding expression must be included. The preceding
3171 expression here is what is in the square brackets -- in this case, any digit
3172 one through nine. Then, at the end, we have a grouping: <quote>(gif|jpe?g)</quote>.
3173 This includes a <quote>|</quote>, so this needs to match the expression on
3174 either side of that bar character also. A simple <quote>gif</quote> on one side, and the other
3175 side will in turn match either <quote>jpeg</quote> or <quote>jpg</quote>,
3176 since the <quote>?</quote> means the letter <quote>e</quote> is optional and
3177 can be matched once or not at all. So we are building an expression here to
3178 match image GIF or JPEG type image file. It must include the literal
3179 string <quote>advert</quote>, then one or more digits, and a <quote>.</quote>
3180 (which is now a literal, and not a special character, since it is escaped
3181 with <quote>\</quote>), and lastly either <quote>gif</quote>, or
3182 <quote>jpeg</quote>, or <quote>jpg</quote>. Some possible matches would
3183 include: <quote>//advert1.jpg</quote>,
3184 <quote>/nasty/ads/advert1234.gif</quote>,
3185 <quote>/banners/from/hell/advert99.jpg</quote>. It would not match
3186 <quote>advert1.gif</quote> (no leading slash), or
3187 <quote>/adverts232.jpg</quote> (the expression does not include an
3188 <quote>s</quote>), or <quote>/advert1.jsp</quote> (<quote>jsp</quote> is not
3189 in the expression anywhere).
3193 <emphasis><literal>s/microsoft(?!.com)/MicroSuck/i</literal></emphasis> - This is
3194 a substitution. <quote>MicroSuck</quote> will replace any occurence of
3195 <quote>microsoft</quote>. The <quote>i</quote> at the end of the expression
3196 means ignore case. The <quote>(?!.com)</quote> means
3197 the match should fail if <quote>microsoft</quote> is followed by
3198 <quote>.com</quote>. In other words, this acts like a <quote>NOT</quote>
3199 modifier. In case this is a hyperlink, we don't want to break it ;-).
3203 We are barely scratching the surface of regular expressions here so that you
3204 can understand the default <application>Junkbuster</application>
3205 configuration files, and maybe use this knowledge to customize your own
3206 installation. There is much, much more that can be done with regular
3207 expressions. Now that you know enough to get started, you can learn more on
3212 More reading on Perl Compatible Regular expressions:
3213 <ulink url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>
3222 This program is free software; you can redistribute it
3223 and/or modify it under the terms of the GNU General
3224 Public License as published by the Free Software
3225 Foundation; either version 2 of the License, or (at
3226 your option) any later version.
3228 This program is distributed in the hope that it will
3229 be useful, but WITHOUT ANY WARRANTY; without even the
3230 implied warranty of MERCHANTABILITY or FITNESS FOR A
3231 PARTICULAR PURPOSE. See the GNU General Public
3232 License for more details.
3234 The GNU General Public License should be included with
3235 this file. If not, you can view it at
3236 http://www.gnu.org/copyleft/gpl.html
3237 or write to the Free Software Foundation, Inc., 59
3238 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
3240 $Log: user-manual.sgml,v $
3241 Revision 1.26 2002/01/09 20:02:50 hal9
3242 Fix bug re: auto-detect config file changes.
3244 Revision 1.25 2002/01/09 18:20:30 hal9
3245 Touch ups for *.action files.
3247 Revision 1.24 2001/12/02 01:13:42 hal9
3250 Revision 1.23 2001/12/02 00:20:41 hal9
3251 Updates for recent changes.
3253 Revision 1.22 2001/11/05 23:57:51 hal9
3254 Minor update for startup now daemon mode.
3256 Revision 1.21 2001/10/31 21:11:03 hal9
3257 Correct 2 minor errors
3259 Revision 1.18 2001/10/24 18:45:26 hal9
3260 *** empty log message ***
3262 Revision 1.17 2001/10/24 17:10:55 hal9
3263 Catching up with Jon's recent work, and a few other things.
3265 Revision 1.16 2001/10/21 17:19:21 swa
3266 wrong url in documentation
3268 Revision 1.15 2001/10/14 23:46:24 hal9
3269 Various minor changes. Fleshed out SEE ALSO section.
3271 Revision 1.13 2001/10/10 17:28:33 hal9
3274 Revision 1.12 2001/09/28 02:57:04 hal9
3277 Revision 1.11 2001/09/28 02:25:20 hal9
3280 Revision 1.9 2001/09/27 23:50:29 hal9
3281 A few changes. A short section on regular expression in appendix.
3283 Revision 1.8 2001/09/25 00:34:59 hal9
3284 Some additions, and re-arranging.
3286 Revision 1.7 2001/09/24 14:31:36 hal9
3289 Revision 1.6 2001/09/24 14:10:32 hal9
3290 Including David's OS/2 installation instructions.
3292 Revision 1.2 2001/09/13 15:27:40 swa
3295 Revision 1.1 2001/09/12 15:36:41 swa
3296 source files for junkbuster documentation
3298 Revision 1.3 2001/09/10 17:43:59 swa
3299 first proposal of a structure.
3301 Revision 1.2 2001/06/13 14:28:31 swa
3302 docs should have an author.
3304 Revision 1.1 2001/06/13 14:20:37 swa
3305 first import of project's documentation for the webserver.
projects / privoxy.git / blob