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.7 2001/09/24 14:31:36 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.7 2001/09/24 14:31:36 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/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. The target release date for stable v3.0 is
86 Since this is a development version, there <emphasis>are</emphasis> bugs!
92 <!-- ~ End section ~ -->
95 <!-- ~~~~~ New section ~~~~~ -->
96 <sect1 id="installation"><title>Installation</title>
98 <application>Junkbuster</application> is available as raw source code, or
99 pre-compiled binaries. See the <ulink
100 url="http://sourceforge.net/projects/ijbswa/">Junkbuster Home Page</ulink>
101 for current releases. <application>Junkbuster</application> is also available
103 url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
104 This is the recommended approach at this time. But please be aware that CVS
105 is constantly changing, and it may break in mysterious ways.
108 <!-- ~~~~~ New section ~~~~~ -->
109 <sect2 id="installation-source"><title>Source</title>
111 For gzipped tar archives, unpack the source:
116 tar zxvf ijb_source_2.9*
122 For retrieving the current CVS sources, you'll need the CVS
123 package installed first. To download CVS source:
128 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
129 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
135 This will create a directory named <filename>current/</filename>, which will
136 contain the source tree.
140 Then, in either case, to build from source:
153 For Redhat and SuSE Linux RPM packages, see below.
159 <!-- ~~~~~ New section ~~~~~ -->
160 <sect2 id="installation-rh"><title>Red Hat</title>
162 To build Redhat RPM packages, install source as above. Then:
173 This will create both binary and src RPMs in the usual places. Example:
177 /usr/src/redhat/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
180 /usr/src/redhat/SRPMS/junkbuster-2.9.8-1.src.rpm
184 To install, of course:
189 rpm -Uvv /usr/src/redhat/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
194 This will place the <application>Junkbuster</application> configuration
195 files in <filename>/etc/junkbuster/</filename>, and log files in
196 <filename>/var/log/junkbuster/</filename>.
201 <!-- ~~~~~ New section ~~~~~ -->
202 <sect2 id="installation-suse"><title>SuSE</title>
204 To build SuSE RPM packages, install source as above. Then:
215 This will create both binary and src RPMs in the usual places. Example:
219 /usr/src/suse/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
222 /usr/src/suse/SRPMS/junkbuster-2.9.8-1.src.rpm
226 To install, of course:
231 rpm -Uvv /usr/src/suse/RPMS/i686/junkbuster-2.9.8-1.i686.rpm
236 This will place the <application>Junkbuster</application> configuration
237 files in <filename>/etc/junkbuster/</filename>, and log files in
238 <filename>/var/log/junkbuster/</filename>.
244 <!-- ~~~~~ New section ~~~~~ -->
245 <sect2 id="installation-os2"><title>OS/2</title>
252 The OS/2 version of <application>Junkbuster</application> requires the EMX
253 runtime library to be installed. The EMX runtime library is available on
254 the hobbes OS/2 archive, among many other locations:
255 <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>
259 <application>Junkbuster</application> is packaged in a WarpIN self-
260 installing archive. The self-installing program will be named depending
261 on the release version, something like:
262 <filename>ijbos123.exe</filename>. In order to install it, simply run
263 this executable or double-click on its icon and follow the WarpIN
264 installation panels. A shadow of the <application>Junkbuster</application>
265 executable will be placed in your startup folder so it will start
266 automatically whenever OS/2 starts.
270 The directory you choose to install <application>Junkbuster</application>
271 into will contain all of the configuration files.
275 If you would like to build binary images on OS/2 yourself, you will need
276 a working EMX/GCC environment, plus several Unix-like tools. The Hobbes
277 OS/2 archive is a good place to start when building such an environment.
278 A set of Unix-like tools named gnupack is located here:
279 <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>
282 Once you have the source code unpacked as above, you can build the binaries
283 from the <filename>current/</filename> directory:
297 <!-- ~~~~~ New section ~~~~~ -->
298 <sect2 id="installation-win"><title>Windows</title>
299 <para>I need help on this. Not a clue here. Also for
300 configuration section below.
304 <!-- ~~~~~ New section ~~~~~ -->
305 <sect2 id="installation-other"><title>Other</title>
307 Some quick notes on other Operating Systems.
311 For FreeBSD (and other *BSDs?), the build will need <command>gmake</command>
312 instead of the included <command>make</command>. <command>gmake</command> is
313 available from <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>.
314 The rest should be the same as above for Linux/Unix.
321 <!-- ~ End section ~ -->
324 <!-- ~~~~~ New section ~~~~~ -->
325 <sect1 id="configuration"><title>Junkbuster Configuration</title>
327 For Unix and Linux, all configuraton files are located in
328 <filename>/etc/junkbuster/</filename> by default. For MS Windows and OS/2,
329 these are all in the same directory as the
330 <application>Junkbuster</application> executable. The name and number of
331 configuration files has changed from previous versions, and is subject to
332 change as development progresses.
336 The installed defaults provide a reasonable starting point. For the
337 time being, there are only three default configuration files (this will
346 The main configuration file is named <filename>config</filename>
347 on Linux, Unix, and OS/2, and <filename>junkbustr.txt</filename> on
354 The <filename>actionsfile</filename> file is used to define various
355 actions relating to images, banners, pop-ups, banners and cookies.
361 The <filename>re_filterfile</filename> file can be used to rewrite the raw
362 page content, including text as well as embedded HTML and JavaScript.
370 <filename>actionsfile</filename> and <filename>re_filterfile</filename>
371 can use Perl style regular expressions for maximum flexibility. All files use
372 the <quote><literal>#</literal></quote> character to denote a comment. Such
373 lines are not processed by <application>Junkbuster</application>. After
374 making any changes, restart <application>Junkbuster</application> in order
375 for the changes to take effect.
379 <!-- ~~~~~ New section ~~~~~ -->
382 <title>The Main Configuration File</title>
384 Again, the main configuration file is named <filename>config</filename> on
385 Linux/Unix and OS/2, and <filename>junkbustr.txt</filename> on Windows.
386 Configuration lines consist of an initial keyword followed by a list of
387 values, all separated by whitespace (any number of spaces or tabs). For
395 <emphasis>blockfile blocklist.ini</emphasis>
402 Indicates that the blockfile is named <quote>blocklist.ini</quote>.
406 The <quote><literal>#</literal></quote> indicates a comment. Any part of a
407 line following a <quote><literal>#</literal></quote> is ignored, except if
408 the <quote><literal>#</literal></quote> is preceded by a
409 <quote><literal>\</literal></quote>.
413 Thus, by placing a <quote><literal>#</literal></quote> at the start of an
414 existing configuration line, you can make it a comment and it will be treated
415 as if it weren't there. This is called <quote>commenting out</quote> an
416 option and can be useful to turn off features: If you comment out the
417 <quote>logfile</quote> line, <application>junkbuster</application> will not
418 log to a file at all. Watch for the <quote>default:</quote> section in each
419 explanation to see what happens if the option is left unset (or commented
424 Long lines can be continued on the next line by using a
425 <quote><literal>\</literal></quote> as the very last character.
429 There are various aspects of <application>Junkbuster</application> behavior
430 that can be adjusted.
434 <!-- ~~~~~ New section ~~~~~ -->
437 <title>Defining Other Configuration Files</title>
440 <application>Junkbuster</application> can use a number of other files to tell it
441 what ads to block, what cookies to accept, etc. This section of the
442 configuration file tells <application>Junkbuster</application> where to find
443 all those other files.
447 On <application>Windows</application>, <application>Junkbuster</application>
448 looks for these files in the same directory as the executable. On Unix and
449 OS/2, <application>Junkbuster</application> looks for these files in the current
450 working directory. In either case, an absolute path name can be used to
455 When development goes modular and multiuser, the blocker, filter, and
456 per-user config will be stored in subdirectories of <quote>confdir</quote>.
457 For now, only <filename>confdir/templates</filename> is used for storing HTML
458 templates for CGI results.
462 The location of the configuration files:
469 <emphasis>confdir /etc/junkbuster</emphasis> # No trailing /, please.
476 The directory where all logging (i.e. <filename>logfile</filename> and
477 <filename>jarfile</filename>) takes place. No trailing
478 <quote><literal>/</literal></quote>, please:
485 <emphasis>logdir /var/log/junkbuster</emphasis>
492 Note that all file specifications below are relative to
493 the above two directories!
497 The <quote>actionsfile</quote> contains patterns to specify the actions to
498 apply to requests for each site. Default: Cookies to and from all
499 destinations are filtered. Popups are disabled for all sites. All sites are
500 filtered if re_filterfile specified. No sites are blocked. An empty image is
501 displayed for filtered ads and other images (formerly
502 <quote>tinygif</quote>). The syntax of this file is explained in detail
503 <link linkend="actionsfile">below</link>.
510 <emphasis>actionsfile actionsfile</emphasis>
517 The <quote>re_filterfile</quote> file contains content modification rules.
518 These rules permit powerful changes on the content of Web pages, e.g., you
519 could disable your favourite JavaScript annoyances, rewrite the actual
520 content, or just have some fun replacing <quote>Microsoft</quote> with
521 <quote>MicroSuck</quote> wherever it appears on a Web page. Default: No
522 content modification, or whatever the developers are playing with :-/
529 <emphasis>re_filterfile re_filterfile</emphasis>
536 The logfile is where all logging and error messages are written. The logfile
537 can be useful for tracking down a problem with
538 <application>Junkbuster</application> (e.g., it's not blocking an ad you
539 think it should block) but in most cases you probably will never look at it.
543 Your logfile will grow indefinitely, and you will probably want to
544 periodically remove it. On Unix systems, you can do this with a cron job
545 (see <quote>man cron</quote>). For Redhat, a <command>logrotate</command>
546 script has been included.
550 On SuSE Linux systems, you can place a line like <quote>/var/log/junkbuster.*
551 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
552 the effect that cron.daily will automatically archive, gzip, and empty the
553 log, when it exceeds 1M size.
557 Default: Log to the a file named <filename>logfile</filename>.
558 Comment out to disable logging.
565 <emphasis>logfile logfile</emphasis>
572 The <quote>jarfile</quote> defines where
573 <application>Junkbuster</application> stores the cookies it intercepts. Note
574 that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
575 Don't store intercepted cookies.
582 <emphasis>#jarfile jarfile</emphasis>
589 If you specify a <quote>trustfile</quote>,
590 <application>Junkbuster</application> will only allow access to sites that
591 are named in the trustfile. You can also mark sites as trusted referrers,
592 with the effect that access to untrusted sites will be granted, if a link
593 from a trusted referrer was used. The link target will then be added to the
594 <quote>trustfile</quote>. This is a very restrictive feature that typical
595 users most propably want to leave disabled. Default: Disabled, don't use the
603 <emphasis>#trustfile trust</emphasis>
610 If you use the trust mechanism, it is a good idea to write up some online
611 documentation about your blocking policy and to specify the URL(s) here. They
612 will appear on the page that your users receive when they try to access
613 untrusted content. Use multiple times for multiple URLs. Default: Don't
614 display links on the <quote>untrusted</quote> info page.
621 <emphasis>trust-info-url http://www.your-site.com/why_we_block.html</emphasis>
622 <emphasis>trust-info-url http://www.your-site.com/what_we_allow.html</emphasis>
630 <!-- ~ End section ~ -->
634 <!-- ~~~~~ New section ~~~~~ -->
637 <title>Other Configuration Options</title>
640 This part of the configuration file contains options that control how
641 <application>Junkbuster</application> operates.
645 <quote>Admin-address</quote> should be set to the email address of the proxy
646 administrator. It is used in many of the proxy-generated pages. Default:
654 <emphasis>#admin-address fill@me.in.please</emphasis>
661 <quote>Proxy-info-url</quote> can be set to a URL that contains more info
662 about this <application>Junkbuster</application> installation, it's
663 configuration and policies. It is used in many of the proxy-generated pages
664 and its use is highly recommended in multi-user installations, since your
665 users will want to know why certain content is blocked or modified. Default:
666 Don't show a link to online documentation.
673 <emphasis>proxy-info-url http://www.your-site.com/proxy.html</emphasis>
680 <quote>Listen-address</quote> specifies the address and port where
681 <application>Junkbuster</application> will listen for connections from your
682 Web browser. The default is to listen on the localhost port 8000, and
683 this is suitable for most users. (In your web browser, under proxy
684 configuration, list the proxy server as <quote>localhost</quote> and the
685 port as <quote>8000</quote>).
689 If you already have another service running on port 8000, or if you want to
690 serve requests from other machines (e.g. on your local network) as well, you
691 will need to override the default. The syntax is
692 <quote>listen-address [<ip-address>]:<port></quote>. If you leave
693 out the IP adress, <application>junkbuster</application> will bind to all
694 interfaces (addresses) on your machine and may become reachable from the
695 internet. In that case, consider using access control lists (acl's) (see
696 <quote>aclfile</quote> above).
700 For example, suppose you are running <application>Junkbuster</application> on
701 a machine which has the address 192.168.0.1 on your local private network
702 (192.168.0.0) and has another outside connection with a different address.
703 You want it to serve requests from inside only:
710 <emphasis>listen-address 192.168.0.1:8000</emphasis>
717 If you want it to listen on all addresses (including the outside
725 <emphasis>listen-address :8000</emphasis>
732 If you do this, consider using ACLs (see <quote>aclfile</quote> above). Note:
733 you will need to point your browser(s) to the address and port that you have
734 configured here. Default: localhost:8000 (127.0.0.1:8000).
738 The debug option sets the level of debugging information to log in the
739 logfile (and to the console in the Windows version). A debug level of 1 is
740 informative because it will show you each request as it happens. Higher
741 levels of debug are probably only of interest to developers.
748 debug 1 # GPC = show each GET/POST/CONNECT request
749 debug 2 # CONN = show each connection status
750 debug 4 # IO = show I/O status
751 debug 8 # HDR = show header parsing
752 debug 16 # LOG = log all data into the logfile
753 debug 32 # FRC = debug force feature
754 debug 64 # REF = debug regular expression filter
755 debug 128 # = debug fast redirects
756 debug 256 # = debug GIF deanimation
757 debug 512 # CLF = Common Log Format
758 debug 1024 # = debug kill popups
759 debug 4096 # INFO = Startup banner and warnings.
760 debug 8192 # ERROR = Non-fatal errors
767 It is <emphasis>highly recommended</emphasis> that you enable ERROR
768 reporting (debug 8192), at least until the next stable release.
772 The reporting of FATAL errors (i.e. ones which crash
773 <application>JunkBuster</application>) is always on and cannot be disabled.
777 If you want to use CLF (Common Log Format), you should set <quote>debug
778 512</quote> ONLY, do not enable anything else.
782 Multiple <quote>debug</quote> directives, are OK - they're logical-OR'd
790 <emphasis>debug 15 # same as setting the first 4 listed above</emphasis>
804 <emphasis>debug 1 # URLs</emphasis>
805 <emphasis>debug 4096 # Info</emphasis>
806 <emphasis>debug 8192 # Errors - *we highly recommended enabling this*</emphasis>
813 <application>Junkbuster</application> normally uses
814 <quote>multi-threading</quote>, a software technique that permits it to
815 handle many different requests simultaneously. In some cases you may wish to
816 disable this -- particularly if you're trying to debug a problem. The
817 <quote>single-threaded</quote> option forces
818 <application>Junkbuster</application> to handle requests sequentially.
819 Default: Multi-threaded mode.
826 <emphasis>#single-threaded</emphasis>
833 <quote>toggle</quote> allows you to temporarily disable all
834 <application>Junkbuster's</application> filtering. Just set <quote>toggle
839 The Windows version of <application>Junkbuster</application> puts an icon in
840 the system tray, which allows you to change this option without having to
841 edit this file. If you right-click on that icon (or select the
842 <quote>Options</quote> menu), one choice is <quote>Enable</quote>. Clicking
843 on enable toggles <application>Junkbuster</application> on and off. This is
844 useful if you want to temporarily disable
845 <application>Junkbuster</application>, e.g., to access a site that requires
846 cookies which you normally have blocked.
850 <quote>toggle 1</quote> means <application>Junkbuster</application> runs
851 normally, <quote>toggle 0</quote> means that
852 <application>Junkbuster</application> becomes a non-anonymizing non-blocking
860 <emphasis>toggle 1</emphasis>
868 <!-- ~ End section ~ -->
871 <!-- ~~~~~ New section ~~~~~ -->
874 <title>Access Control List (ACL)</title>
876 Access controls are included at the request of some ISPs and systems
877 administrators, and are not usually needed by individual users. Please note
878 the warnings in the FAQ that this proxy is not intended to be a substitute
879 for a firewall or to encourage anyone to defer addressing basic security
884 If no access settings are specified, the proxy talks to anyone that
885 connects. If any access settings file are specified, then the proxy
886 talks only to IP addresses permitted somewhere in this file and not
887 denied later in this file.
891 Summary -- if using an ACL:
896 Client must have permission to receive service.
901 LAST match in ACL wins.
906 Default behavior is to deny service.
911 The syntax for an entry in the Access Control List is:
918 ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
925 Where the individual fields are:
932 <emphasis>ACTION</emphasis> = <quote>permit-access</quote> or <quote>deny-access</quote>
934 <emphasis>SRC_ADDR</emphasis> = client hostname or dotted IP address
935 <emphasis>SRC_MASKLEN</emphasis> = number of bits in the subnet mask for the source
937 <emphasis>DST_ADDR</emphasis> = server or forwarder hostname or dotted IP address
938 <emphasis>DST_MASKLEN</emphasis> = number of bits in the subnet mask for the target
946 The field separator (FS) is whitespace (space or tab).
950 IMPORTANT NOTE: If the <application>junkbuster</application> is using a
951 forwarder (see below) or a gateway for a particular destination URL, the
952 <literal>DST_ADDR</literal> that is examined is the address of the forwarder
953 or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
954 target. This is necessary because it may be impossible for the local
955 <application>Junkbuster</application> to determine the address of the
956 ultimate target (that's often what gateways are used for).
960 Here are a few examples to show how the ACL features work:
964 <quote>localhost</quote> is OK -- no DST_ADDR implies that
965 <emphasis>ALL</emphasis> destination addresses are OK:
972 <emphasis>permit-access localhost</emphasis>
979 A silly example to illustrate permitting any host on the class-C subnet with
980 <application>Junkbuster</application> to go anywhere:
987 <emphasis>permit-access www.junkbusters.com/24</emphasis>
994 Except deny one particular IP address from using it at all:
1001 <emphasis>deny-access ident.junkbusters.com</emphasis>
1008 You can also specify an explicit network address and subnet mask.
1009 Explicit addresses do not have to be resolved to be used.
1016 <emphasis>permit-access 207.153.200.0/24</emphasis>
1023 A subnet mask of 0 matches anything, so the next line permits everyone.
1030 <emphasis>permit-access 0.0.0.0/0</emphasis>
1037 Note, you <emphasis>cannot</emphasis> say:
1044 <emphasis>permit-access .org</emphasis>
1051 to allow all *.org domains. Every IP address listed must resolve fully.
1055 An ISP may want to provide a <application>Junkbuster</application> that is
1056 accessible by <quote>the world</quote> and yet restrict use of some of their
1057 private content to hosts on its internal network (i.e. its own subscribers).
1058 Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
1059 bit netmask). This is how they could do it:
1066 <emphasis>permit-access 0.0.0.0/0 0.0.0.0/0</emphasis> # other clients can go anywhere
1067 # with the following exceptions:
1069 <emphasis>deny-access</emphasis> 0.0.0.0/0 123.124.0.0/16 # block all external requests for
1070 # sites on the ISP's network
1072 <emphasis>permit 0.0.0.0/0 www.my_isp.com</emphasis> # except for the ISP's main
1075 <emphasis>permit 123.124.0.0/16 0.0.0.0/0</emphasis> # the ISP's clients can go
1083 Note that if some hostnames are listed with multiple IP addresses,
1084 the primary value returned by DNS (via gethostbyname()) is used. Default:
1085 Anyone can access the proxy.
1090 <!-- ~ End section ~ -->
1093 <!-- ~~~~~ New section ~~~~~ -->
1096 <title>Forwarding</title>
1099 This feature allows routing of HTTP requests via multiple proxies.
1100 It can be used to better protect privacy and confidentiality when
1101 accessing specific domains by routing requests to those domains
1102 to a special purpose filtering proxy such as lpwa.com.
1106 It can also be used in an environment with multiple networks to route
1107 requests via multiple gateways allowing transparent access to multiple
1108 networks without having to modify browser configurations.
1112 Also specified here are SOCKS proxies. <application>Junkbuster</application>
1113 SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
1114 hostname using DNS on the SOCKS server, not our local DNS client.
1118 The syntax of each line is:
1125 <emphasis>forward target_domain[:port] http_proxy_host[:port]</emphasis>
1126 <emphasis>forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1127 <emphasis>forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1134 If http_proxy_host is <quote>.</quote>, then requests are not forwarded to a
1135 HTTP proxy but are made directly to the web servers.
1139 Lines are checked in sequence, and the last match wins.
1143 There is an implicit line equivalent to the following, which specifies that
1144 anything not finding a match on the list is to go out without forwarding
1145 or gateway protocol, like so:
1152 <emphasis>forward .* . </emphasis># implicit
1159 In the following common configuration, everything goes to Lucent's LPWA,
1160 except SSL on port 443 (which it doesn't handle):
1167 <emphasis>forward .* lpwa.com:8000</emphasis>
1168 <emphasis>forward :443 .</emphasis>
1175 See the FAQ for instructions on how to automate the login procedure for LPWA.
1176 Some users have reported difficulties related to LPWA's use of
1177 <quote>.</quote> as the last element of the domain, and have said that this
1178 can be fixed with this:
1185 <emphasis>forward lpwa. lpwa.com:8000</emphasis>
1192 (NOTE: the syntax for specifiying target_domain has changed since the
1193 previous paragraph was written -- it will not work now. More information
1198 In this fictitious example, everything goes via an ISP's caching proxy,
1199 except requests to that ISP:
1206 <emphasis>forward .* caching.myisp.net:8000</emphasis>
1207 <emphasis>forward myisp.net .</emphasis>
1214 For the @home network, we're told the forwarding configuration is this:
1222 <emphasis>forward .* proxy:8080</emphasis>
1229 Also, we're told they insist on getting cookies and JavaScript, so you need
1230 to add home.com to the cookie file. We consider JavaScript a security risk.
1231 Java need not be enabled.
1235 In this example direct connections are made to all <quote>internal</quote>
1236 domains, but everything else goes through Lucent's LPWA by way of the
1237 company's SOCKS gateway to the Internet.
1244 <emphasis>forward_socks4 .* lpwa.com:8000 firewall.my_company.com:1080</emphasis>
1245 <emphasis>forward my_company.com .</emphasis>
1252 This is how you could set up a site that always uses SOCKS but no forwarders:
1259 <emphasis>forward_socks4a .* . firewall.my_company.com:1080</emphasis>
1266 An advanced example for network administrators:
1270 If you have links to multiple ISPs that provide various special content to
1271 their subscribers, you can configure forwarding to pass requests to the
1272 specific host that's connected to that ISP so that everybody can see all
1273 of the content on all of the ISPs.
1277 This is a bit tricky, but here's an example:
1282 host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
1283 isp-b.com. host-a can run a <application>Junkbuster</application> proxy with
1284 forwarding like this:
1291 <emphasis>forward .* .</emphasis>
1292 <emphasis>forward isp-b.com host-b:8000</emphasis>
1299 host-b can run a <application>Junkbuster</application> proxy with forwarding
1307 <emphasis>forward .* .</emphasis>
1308 <emphasis>forward isp-a.com host-a:8000</emphasis>
1315 Now, <emphasis>anyone</emphasis> on the Internet (including users on host-a
1316 and host-b) can set their browser's proxy to <emphasis>either</emphasis>
1317 host-a or host-b and be able to browse the content on isp-a or isp-b.
1321 Here's another practical example, for University of Kent at
1322 Canterbury students with a network connection in their room, who
1323 need to use the University's Squid web cache.
1330 <emphasis>forward *. ssbcache.ukc.ac.uk:3128</emphasis> # Use the proxy, except for:
1331 <emphasis>forward .ukc.ac.uk . </emphasis> # Anything on the same domain as us
1332 <emphasis>forward * . </emphasis> # Host with no domain specified
1333 <emphasis>forward 129.12.*.* . </emphasis> # A dotted IP on our /16 network.
1334 <emphasis>forward 127.*.*.* . </emphasis> # Loopback address
1335 <emphasis>forward localhost.localdomain . </emphasis> # Loopback address
1336 <emphasis>forward www.ukc.mirror.ac.uk . </emphasis> # Specific host
1343 If you intend to chain <application>Junkbuster</application> and
1344 <application>squid</application> locally, then chain as
1345 <literal>browser -> squid -> junkbuster</literal> is the recommended way.
1349 Your squid configuration could then look like this:
1356 # Define junkbuster as parent cache
1357 cache_peer 127.0.0.1 8000 parent 0 no-query
1359 # Define ACL for protocol FTP
1362 # Do not forward ACL FTP to junkbuster
1363 always_direct allow FTP
1365 # Do not forward ACL CONNECT (https) to junkbuster
1366 always_direct allow CONNECT
1368 # Forward the rest to junkbuster
1369 never_direct allow all
1377 <!-- ~ End section ~ -->
1380 <!-- ~~~~~ New section ~~~~~ -->
1383 <title>Windows GUI Options</title>
1385 Removed references to Win32. HB 09/23/01
1388 <application>Junkbuster</application> has a number of options specific to the
1389 Windows GUI interface:
1393 If <quote>activity-animation</quote> is set to 1, the
1394 <application>Junkbuster</application> icon will animate when
1395 <quote>Junkbuster</quote> is active. To turn off, set to 0.
1402 <emphasis>activity-animation 1</emphasis>
1409 If <quote>log-messages</quote> is set to 1,
1410 <application>Junkbuster</application> will log messages to the console
1418 <emphasis>log-messages 1</emphasis>
1425 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
1426 i.e. the amount of memory used for the log messages displayed in the
1427 console window, will be limited to <quote>log-max-lines</quote> (see below).
1431 Warning: Setting this to 0 will result in the buffer to grow infinitely and
1432 eat up all your memory!
1439 <emphasis>log-buffer-size 1</emphasis>
1446 <application>log-max-lines</application> is the maximum number of lines held
1447 in the log buffer. See above.
1454 <emphasis>log-max-lines 200</emphasis>
1461 If <quote>log-highlight-messages</quote> is set to 1,
1462 <application>Junkbuster</application> will highlight portions of the log
1463 messages with a bold-faced font:
1470 <emphasis>log-highlight-messages 1</emphasis>
1477 The font used in the console window:
1484 <emphasis>log-font-name Comic Sans MS</emphasis>
1491 Font size used in the console window:
1498 <emphasis>log-font-size 8</emphasis>
1505 <quote>show-on-task-bar</quote> controls whether or not
1506 <application>Junkbuster</application> will appear as a button on the Task bar
1514 <emphasis>show-on-task-bar 0</emphasis>
1521 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
1522 button will minimize <application>Junkbuster</application> instead of closing
1523 the program (close with the exit option on the File menu).
1530 <emphasis>close-button-minimizes 1</emphasis>
1537 The <quote>hide-console</quote> option is specific to the MS-Win console
1538 version of <application>JunkBuster</application>. If this option is used,
1539 <application>Junkbuster</application> will disconnect from and hide the
1556 <!-- ~ End section ~ -->
1559 <!-- ~~~~~ New section ~~~~~ -->
1560 <sect2 id="actionsfile">
1561 <title>The Actions File</title>
1564 The <quote>actionsfile</quote> is used to define what actions
1565 <application>Junkbuster</application> takes, and thus determines how images,
1566 cookies and various other aspects of HTTP content and transactions are
1567 handled. Images can be anything you want, including ads, banners, or just
1568 some obnoxious image that you would rather not see. Cookies can be accepted
1569 or rejected. The default file is in fact named <filename>actionsfile</filename>.
1573 To determine which actions apply to a request, the URL of the request is
1574 compared to all patterns in this file. Every time it matches, the list of
1575 applicable actions for the URL is incrementally updated. You can trace
1576 this process by visiting <ulink
1577 url="http://i.j.b/show-url-info">http://i.j.b/show-url-info</ulink>.
1581 There are four types of lines in this file: comments (begin with a
1582 <quote>#</quote> character), actions, aliases and patterns, all of which are
1587 <!-- ~~~~~ New section ~~~~~ -->
1589 <title>URL Domain and Path Syntax</title>
1591 Generally, a pattern has the form <domain>/<path>, where both the
1592 <domain> and <path> part are optional. If you only specify a
1593 domain part, the <quote>/</quote> can be left out:
1597 <emphasis>www.example.com</emphasis> - is a domain only pattern and will match any request to
1598 <quote>www.example.com</quote>.
1602 <emphasis>www.example.com/</emphasis> - means exactly the same.
1606 <emphasis>www.example.com/index.html</emphasis> - matches only the single
1607 document <quote>/index.html</quote> on <quote>www.example.com</quote>.
1611 <emphasis>/index.html</emphasis> - matches the document <quote>/index.html</quote>, regardless of
1616 <emphasis>index.html</emphasis> - matches nothing, since it would be
1617 interpreted as a domain name and there is no top-level domain called
1618 <quote>.html</quote>.
1622 The matching of the domain part offers some flexible options: if the
1623 domain starts or ends with a dot, it becomes unanchored at that end.
1628 <emphasis>.example.com</emphasis> - matches any domain that <emphasis>ENDS</emphasis> in
1629 <quote>.example.com</quote>.
1633 <emphasis>www.</emphasis> - matches any domain that <emphasis>STARTS</emphasis> with
1638 Additionally, there are wildcards that you can use in the domain names
1639 themselves. They work pretty similar to shell wildcards: <quote>*</quote>
1640 stands for zero or more arbitrary characters, <quote>?</quote> stands for
1641 any single character. And you can define charachter classes in square
1642 brackets and they can be freely mixed:
1646 <emphasis>ad*.example.com</emphasis> - matches <quote>adserver.example.com</quote>,
1647 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>.
1651 <emphasis>*ad*.example.com</emphasis> - matches all of the above, and then some.
1655 <emphasis>.?pix.com</emphasis> - matches <quote>www.ipix.com</quote>,
1656 <quote>pictures.epix.com</quote>, <quote>a.b.c.d.e.upix.com</quote>, etc.
1660 <emphasis>www[1-9a-ez].example.com</emphasis> - matches <quote>www1.example.com</quote>,
1661 <quote>www4.example.com</quote>, <quote>wwwd.example.com</quote>,
1662 <quote>wwwz.example.com</quote>, etc., but <emphasis>not</emphasis>
1663 <quote>wwww.example.com</quote>.
1667 If <application>Junkbuster</application> was compiled with
1668 <quote>pcre</quote> support (default), Perl compatible regular expressions
1669 can be used. See the <filename>pcre/docs/</filename> direcory or <quote>man
1670 perlre</quote> (also available on <ulink
1671 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>)
1672 for details. A brief discussion of regular expressions is in the
1673 <link linkend="regex">Appendix</link>. For instance:
1677 <emphasis>/.*/advert[0-9]+\.jpe?g</emphasis> - would match a URL from any
1678 domain, with any path that includes <quote>advert</quote> followed
1679 immediately by one or more digits, then a <quote>.</quote> and ending in
1680 either <quote>jpeg</quote> or <quote>jpg</quote>. So we match
1681 <quote>example.com/ads/advert2.jpg</quote>, and
1682 <quote>www.example.com/ads/banners/advert39.jpeg</quote>, but not
1683 <quote>www.example.com/ads/banners/advert39.gif</quote> (no gifs in the
1688 Please note that matching in the path is case
1689 <emphasis>INSENSITIVE</emphasis> by default, but you can switch to case
1690 sensitive at any point in the pattern by using the
1691 <quote>(?-i)</quote> switch:
1695 <emphasis>www.example.com/(?-i)PaTtErN.*</emphasis> - will match only
1696 documents whose path starts with <quote>PaTtErN</quote> in
1697 <emphasis>exactly</emphasis> this capitalization.
1702 <!-- ~ End section ~ -->
1706 <!-- ~~~~~ New section ~~~~~ -->
1709 <title>Actions</title>
1711 Actions are enabled if preceded with a <quote>+</quote>, and disabled if
1712 preceded with a <quote>-</quote>. Actions are invoked by enclosing the
1713 action name in curly braces (e.g. {+some_action}), followed by a list of
1714 URLs to which the action applies. There are three classes of actions:
1722 Boolean (e.g. <quote>+/-block</quote>):
1728 <emphasis>{+name}</emphasis> # enable this action
1729 <emphasis>{-name}</emphasis> # disable this action
1739 Parameterized (e.g. <quote>+/-hide-user-agent</quote>):
1745 <emphasis>{+name{param}}</emphasis> # enable action and set parameter to <quote>param</quote>
1746 <emphasis>{-name}</emphasis> # disable action
1755 Multi-value (e.g. <quote>{+/-add-header{Name: value}}</quote>, <quote>{+/-wafer{name=value}}</quote>):
1761 <emphasis>{+name{param}}</emphasis> # enable action and add parameter <quote>param</quote>
1762 <emphasis>{-name{param}}</emphasis> # remove the parameter <quote>param</quote>
1763 <emphasis>{-name}</emphasis> # disable this action totally
1774 If nothing is specified in this file, no <quote>actions</quote> are taken.
1775 So in this case <application>JunkBuster</application> would just be a
1776 normal, non-blocking, non-anonymizing proxy. You must specifically
1777 enable the privacy and blocking features you need (although the
1778 provided default <filename>actionsfile</filename> file will
1779 give a good starting point).
1783 Later defined actions always over-ride earlier ones. For multi-valued
1784 actions, the actions are applied in the order they are specified.
1788 The list of valid <application>Junkbuster</application> <quote>actions</quote> are:
1796 Add the specified HTTP header, which is not checked for validity.
1797 You may specify this many times to specify many different headers:
1803 <emphasis>+add-header{Name: value}</emphasis>
1813 Block this URL totally.
1819 <emphasis>+block</emphasis>
1829 De-animate all animated GIF images, i.e. reduce them to their last frame.
1830 This will also shrink the images considerably (in bytes, not pixels!). If
1831 the option <quote>first</quote> is given, the first frame of the animation
1832 is used as the replacement. If <quote>last</quote> is given, the last frame
1833 of the animation is used instead, which propably makes more sense for most
1834 banner animations, but also has the risk of not showing the entire last
1835 frame (if it is only a delta to an earlier frame).
1841 <emphasis>+deanimate-gifs{last}</emphasis>
1842 <emphasis>+deanimate-gifs{first}</emphasis>
1851 Many sites, like yahoo.com, don't just link to other sites. Instead, they
1852 will link to some script on their own server, giving the destination as a
1853 parameter, which will then redirect you to the final target. URLs resulting
1854 from this scheme typically look like:
1855 http://some.place/some_script?http://some.where-else.
1858 Sometimes, there are even multiple consecutive redirects encoded in the
1859 URL. These redirections via scripts make your web browing more traceable,
1860 since the server from which you follow such a link can see where you go to.
1861 Apart from that, valuable bandwidth and time is wasted, while your browser
1862 ask the server for one redirect after the other. Plus, it feeds the
1866 The <quote>+fast-redirects</quote> option enables interception of these
1867 requests by <application>Junkbuster</application>, who will cut off all but
1868 the last valid URL in the request and send a local redirect back to your
1869 browser without contacting the remote site.
1875 <emphasis>+fast-redirects</emphasis>
1884 Filter the website through the re_filterfile:
1890 <emphasis>+filter{filename}</emphasis>
1899 Block any existing X-Forwarded-for header, and do not add a new one:
1905 <emphasis>+hide-forwarded</emphasis>
1914 If the browser sends a <quote>From:</quote> header containing your e-mail
1915 address, this either completely removes the header (<quote>block</quote>), or
1916 changes it to the specified e-mail address.
1922 <emphasis>+hide-from{block}</emphasis>
1923 <emphasis>+hide-from{spam@sittingduck.xqq}</emphasis>
1932 Don't send the <quote>Referer:</quote> (sic) header to the web site. You
1933 can block it, forge a URL to the same server as the request (which is
1934 preferred because some sites will not send images otherwise) or set it to a
1935 constant string of your choice.
1941 <emphasis>+hide-referer{block}</emphasis>
1942 <emphasis>+hide-referer{forge}</emphasis>
1943 <emphasis>+hide-referer{http://nowhere.com}</emphasis>
1952 Alternative spelling of <quote>+hide-referer</quote>. It has the same
1953 parameters, and can be freely mixed with, <quote>+hide-referer</quote>.
1954 (<quote>referrer</quote> is the correct English spelling, however the HTTP
1955 specification has a bug - it requires it to be spelled <quote>referer</quote>.)
1961 <emphasis>+hide-referrer{...}</emphasis>
1970 Change the <quote>User-Agent:</quote> header so web servers can't tell your
1971 browser type. Warning! This breaks many web sites. Specify the
1972 user-agent value you want. Example, pretend to be using Netscape on
1979 <emphasis>+hide-user-agent{Mozilla (X11; I; Linux 2.0.32 i586)}</emphasis>
1986 Or to identify yourself explicitly as a <quote>Junkbuster</quote> user:
1992 <emphasis>+hide-user-agent{JunkBuster/1.0}</emphasis>
1997 (Don't change the version number from 1.0 - after all, why tell them?)
2004 <emphasis>+hide-user-agent{browser-type}</emphasis>
2014 Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
2015 in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
2016 See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
2022 <emphasis>+image</emphasis>
2031 Decides what to do with URLs that end up tagged with <quote>{+block
2032 +image}</quote>. There are 4 options. <quote>-image-blocker</quote> will
2033 send a HTML <quote>blocked</quote> page, usually resulting in a
2034 <quote>broken image</quote> icon. <quote>+image-blocker{logo}</quote> will
2035 send a <quote>JunkBuster</quote> image.
2036 <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF image.
2037 And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a HTTP
2038 temporary redirect to the specified image. This has the advantage of the
2039 icon being being cached by the browser, which will speed up the display.
2045 <emphasis>+image-blocker{logo}</emphasis>
2046 <emphasis>+image-blocker{blank}</emphasis>
2047 <emphasis>+image-blocker{http://i.j.b/send-banner}</emphasis>
2056 Prevent the website from reading cookies:
2062 <emphasis>+no-cookies-read</emphasis>
2071 Prevent the website from setting cookies:
2077 <emphasis>+no-cookies-set</emphasis>
2086 Filter the website through a built-in filter to disable those obnoxious
2087 JavaScript pop-up windows via window.open(), etc. The two alternative
2088 spellings are equivalent.
2094 <emphasis>+no-popup</emphasis>
2095 <emphasis>+no-popups</emphasis>
2104 This action only applies if you are using a <filename>jarfile</filename>
2105 for saving cookies. It sends a cookie to every site stating that you do not
2106 accept any copyright on cookies sent to you, and asking them not to track
2107 you. Of course, this is a (relatively) unique header they could use to
2114 <emphasis>+vanilla-wafer</emphasis>
2123 This allows you to add an arbitrary cookie. It can be specified multiple
2124 times in order to add as many cookies as you like.
2130 <emphasis>+wafer{name=value}</emphasis>
2141 The meaning of any of the above is reversed by preceding the action with a
2142 <quote>-</quote>, in place of the <quote>+</quote>.
2150 Turn off cookies by default, then allow a few through for specified sites:
2157 # Turn off all cookies
2158 { +no-cookies-read }
2161 # Execeptions to the above, sites that need cookies
2162 { -no-cookies-read }
2170 # Alternative way of saying the same thing
2171 {-no-cookies-set -no-cookies-read}
2180 Now turn off <quote>fast redirects</quote>, and then we allow two exceptions:
2190 # Reverse it for these two sites, which don't work right without it.
2192 www.ukc.ac.uk/cgi-bin/wac\.cgi\?
2200 Turn on page filtering, with one exception for sourceforge:
2207 # Run everything through the default filter file (<filename>re_filterfile</filename>):
2210 # But please don't re_filter code from sourceforge!
2212 .cvs.sourceforge.net
2219 Now some URLs that we want <quote>blocked</quote>, ie we won't see them.
2220 Many of these use regular expressions that will expand to match multiple
2230 /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g))
2231 /.*/(.*[-_.])?count(er)?(\.cgi|\.dll|\.exe|[?/])
2232 /.*/(ng)?adclient\.cgi
2233 /.*/(plain|live|rotate)[-_.]?ads?/
2234 /.*/(sponsor)s?[0-9]?/
2235 /.*/_?(plain|live)?ads?(-banners)?/
2237 /.*/ad(sdna_image|gifs?)/
2238 /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe)
2242 /.*/adv((er)?ts?|ertis(ing|ements?))?/
2246 /.*/cgi-bin/centralad/getimage
2247 /.*/images/addver\.gif
2248 /.*/images/marketing/.*\.(gif|jpe?g)
2252 /.*/sponsors?[0-9]?/
2253 /.*/advert[0-9]+\.jpg
2260 /graphics/defaultAd/
2262 /image\.ng/transactionID
2263 /images/.*/.*_anim\.gif # alvin brattli
2264 /ip_img/.*\.(gif|jpe?g)
2268 /cgi-bin/nph-adclick.exe/
2269 /.*/Image/BannerAdvertising/
2271 /.*/adlib/server\.cgi
2280 <!-- ~ End section ~ -->
2283 <!-- ~~~~~ New section ~~~~~ -->
2285 <title>Aliases</title>
2287 Custom <quote>actions</quote>, known to <application>Junkbuster</application>
2288 as <quote>aliases</quote>, can be defined by combing other <quote>actions</quote>.
2289 These can in turn be invoked just like the built-in <quote>actions</quote>.
2290 Currently, an alias can contain any character except space, tab, <quote>=</quote>,
2291 <quote>{</quote> or <quote>}</quote>. But please use only <quote>a</quote>-
2292 <quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
2293 <quote>-</quote>. Alias names are not case sensitive, and must be defined
2294 before they are used.
2298 Now let's define a few aliases:
2309 +no-cookies = +no-cookies-set +no-cookies-read
2310 -no-cookies = -no-cookies-set -no-cookies-read
2311 fragile = -block -no-cookies -filter -fast-redirects -hide-referer -no-popups
2312 shop = -no-cookies -filter -fast-redirects
2313 +imageblock = +block +image
2315 #For people who don't like to type too much: ;-)
2318 c2 = -no-cookies-set +no-cookies-read
2319 c3 = +no-cookies-set -no-cookies-read
2320 #... etc. Customize to your heart's content.
2327 Some examples using our <quote>shop</quote> and <quote>fragile</quote>
2335 # These sites are very complex and require
2336 # minimal interference.
2338 .office.microsoft.com
2339 .windowsupdate.microsoft.com
2341 # Shopping sites - still want to block ads.
2344 .worldpay.com # for quietpc.com
2348 # These shops require pop-ups
2360 <!-- ~ End section ~ -->
2363 <!-- ~~~~~ New section ~~~~~ -->
2364 <sect2 id="filterfile">
2365 <title>The Filter File</title>
2367 The filter file defines what filtering of web pages
2368 <application>Junkbuster</application> does. The default filter file is
2369 <filename>re_filterfile</filename>, located in the config directory. In this
2370 file, <emphasis>any document content</emphasis>, whether viewable text or
2371 embedded non-visible content, can be changed.
2375 This file uses regular expressions to alter or remove any string in the
2376 target page. Some examples from the included default <filename>re_filterfile</filename>:
2380 Stop web pages from displaying annoying messages in the status bar by
2381 deleting such references:
2388 # The status bar is for displaying link targets, not pointless buzzwords.
2389 # Again, check it out on http://www.airport-cgn.de/.
2390 s/status='.*?';*//ig
2397 Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
2398 <quote>MicroSuck</quote>:
2405 s/microsoft(?!.com)/MicroSuck/ig
2412 Kill those auto-refresh tags:
2419 # Kill refresh tags. I like to refresh myself. Manually.
2420 # check it out on http://www.airport-cgn.de/ and go to the arrivals page.
2422 s/<meta[^>]*http-equiv[^>]*refresh.*URL=([^>]*?)"?>/<link rev="x-refresh" href=$1>/i
2423 s/<meta[^>]*http-equiv="?page-enter"?[^>]*content=[^>]*>/<!--no page enter for me-->/i
2433 <!-- ~~~~~ New section ~~~~~ -->
2434 <sect1 id="quickstart"><title>Quickstart to Using Junkbuster</title>
2436 Install package, then run and enjoy! Be sure your browser is set to use
2437 the proxy which is by default at localhost, port 8000. With
2438 <application>Netscape</application> (and <application>Mozilla</application>),
2439 this can be set under <literal>Edit -> Preferences -> Advanced ->
2440 Proxies -> HTTP Proxy</literal>. For <application>Internet
2441 Explorer</application>: <literal>Internet Properties -> Connections ->
2442 LAN Setting</literal>. Then, check <quote>Use Proxy</quote> and fill in the
2443 appropriate info (Address: localhost, Port: 8000).
2447 The included default configuration files should give a reasonable starting
2448 point, though may be aggressive in blocking junk. You will probably want to
2449 keep an eye out for sites that require cookies, and add these to
2450 <filename>actionsfile</filename> as needed. By default, most of these will be
2451 blocked until you add them to the configuration. If you want the browser to
2452 handle this, you will need to edit <filename>actionsfile</filename> and
2453 disable this feature.
2457 If you enter counter problems, please verify it is a
2458 <application>Junkbuster</application> bug, by disabling
2459 <application>Junkbuster</application>, and then trying the same page.
2460 Before reporting it as a bug, see if there is not a configuration
2461 option that is enabled that is causing the page not to load. You can
2462 then add an exception for that page or site. If a bug, please report it to
2463 the developers (see below).
2469 <!-- ~~~~~ New section ~~~~~ -->
2470 <sect1 id="contact"><title>Contact the Developers</title>
2473 To be filled. mention the support forums as the primary channel of
2474 communication (bugs, feature requests, etc.)
2476 Feature requests and other questions should be posted to the <ulink
2477 url="http://sourceforge.net/forum/?group_id=11118">Support Forums</ulink> at
2478 SourceForge. There is also an archive there.
2482 Anyone interested in actively participating in development and related
2483 discussions can join the appropriate mailing list
2484 <ulink url="http://sourceforge.net/mail/?group_id=11118">here</ulink>.
2485 Archives are available here too.
2489 Please report bugs, using the form at
2490 <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge</ulink>.
2496 <!-- ~~~~~ New section ~~~~~ -->
2497 <sect1 id="copyright"><title>Copyright and History</title>
2500 <title>License</title>
2502 <application>Internet Junkbuster</application> is free software; you can
2503 redistribute it and/or modify it under the terms of the GNU General Public
2504 License as published by the Free Software Foundation; either version 2 of the
2505 License, or (at your option) any later version.
2509 This program is distributed in the hope that it will be useful, but WITHOUT
2510 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
2511 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
2512 details, which is available from <ulink
2513 url="http://www.gnu.org/copyleft/gpl.html">the Free Software Foundation,
2514 Inc</ulink>, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
2519 <!-- ~ End section ~ -->
2522 <!-- ~~~~~ New section ~~~~~ -->
2525 <title>History</title>
2527 <application>Junkbuster</application> was originally written by Anonymous
2529 url="http://www.junkbusters.com/ht/en/ijbfaq.html">JunkBusters
2530 Corporation</ulink>, and was released as free open-source software under the
2531 GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
2532 Waldherr</ulink> made many improvements, and started the <ulink
2533 url="http://sourceforge.net/projects/ijbswa/">SourceForge project</ulink> to
2534 rekindle development. The last stable release was v2.0.2, which has now
2542 <!-- ~~~~~ New section ~~~~~ -->
2543 <sect1 id="seealso"><title>See also</title>
2544 <para>To be filled. What should go here :/
2550 <!-- ~~~~~ New section ~~~~~ -->
2551 <sect1 id="appendix"><title>Appendix</title>
2554 <!-- ~~~~~ New section ~~~~~ -->
2556 <title>Regular Expressions</title>
2558 Some expressions are regular, and some are not.
2567 This program is free software; you can redistribute it
2568 and/or modify it under the terms of the GNU General
2569 Public License as published by the Free Software
2570 Foundation; either version 2 of the License, or (at
2571 your option) any later version.
2573 This program is distributed in the hope that it will
2574 be useful, but WITHOUT ANY WARRANTY; without even the
2575 implied warranty of MERCHANTABILITY or FITNESS FOR A
2576 PARTICULAR PURPOSE. See the GNU General Public
2577 License for more details.
2579 The GNU General Public License should be included with
2580 this file. If not, you can view it at
2581 http://www.gnu.org/copyleft/gpl.html
2582 or write to the Free Software Foundation, Inc., 59
2583 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
2585 $Log: user-manual.sgml,v $
2587 Revision 1.7 2001/09/24 14:31:36 hal9
2590 Revision 1.6 2001/09/24 14:10:32 hal9
2591 Including David's OS/2 installation instructions.
2593 Revision 1.2 2001/09/13 15:27:40 swa
2596 Revision 1.1 2001/09/12 15:36:41 swa
2597 source files for junkbuster documentation
2599 Revision 1.3 2001/09/10 17:43:59 swa
2600 first proposal of a structure.
2602 Revision 1.2 2001/06/13 14:28:31 swa
2603 docs should have an author.
2605 Revision 1.1 2001/06/13 14:20:37 swa
2606 first import of project's documentation for the webserver.