1 # Sample Configuration file for the Internet Junkbuster 2.0
4 # $Id: config,v 1.11 2001/06/03 18:38:11 oes Exp $
10 # 2. FORMAT OF THE CONFIGURATION FILE
11 # 3. OTHER CONFIGURATION FILES
13 # 5. WINDOWS GUI OPTIONS
17 # This file holds the Junkbuster configuration. If you modify this
18 # file, you will need to stop & restart Junkbuster, or use the
19 # "Reload Config" option (Windows) before any changes take effect.
21 # When starting Junkbuster on Unix systems, give the name of this
22 # file as an argument. On Windows systems, Junkbuster will look for
23 # this file with the name 'junkbustr.txt' in the same directory where
24 # Junkbuster is installed.
26 # 2. FORMAT OF THE CONFIGURATION FILE
28 # Configuration lines consist of an initial keyword followed by a list
29 # of values, all separated by whitespace (any number of spaces or
32 # blockfile blocklist.ini
34 # Indicates that the blockfile is named 'blocklist.ini'.
36 # The '#' indicates a comment. Any part of a line following a '#' is
37 # ignored, except if the '#' is preceded by a '\'.
39 # Thus, by placing a # at the start of an existing configuration line,
40 # you can make it a comment and it will be treated as if it weren't there.
41 # This is called "commenting out" an option and can be useful to turn
42 # off features: If you comment out the "logfile" line, junkbuster will
43 # not log at all. Watch for the "default:" section in each explanation
44 # to see what happens if the option is left unset (or commented out).
46 # Long lines can be continued on the next line by using a `\' as
47 # the last character. This also works if comments are present in
52 # 3. OTHER CONFIGURATION FILES
54 # Junkbuster uses a number of other files to tell it what ads to
55 # block, what cookies to accept, etc. This section of the
56 # configuration file tells Junkbuster where to find all those other
59 # On Windows, Junkbuster looks for these files in the same
60 # directory as the executable. On Unix, Junkbuster looks for these
61 # files in the current working directory. In either case, an
62 # absolute path name can be used to avoid problems.
64 # While we go modular and multiuser, the blocker, filter, and
65 # per-user config will be stored in subdirectories of confdir.
66 # Now, only confdir/templates is used for storing HTML templates
69 confdir /home/swa/sourceforge/current
71 # The permissions file contains patterns to specify the
72 # filtering rules to apply to each site.
74 # Default: Cookies to and from all destinations are filtered.
75 # Popups are disabled for all sites.
76 # All sites are filtered if re_filterfile specified.
77 # No sites are blocked. Nothing is an image.
79 permissionsfile ./permissionsfile
82 # The re_filterfile contains content modification rules. These rules
83 # permit powerful changes on the content of Web pages, e.g., you
84 # could disable your favourite JavaScript annoyances, rewrite the
85 # actual content, or just have some fun replacing "Microsoft"
86 # with "Microsuck" wherever it appears on a Web page.
88 # Default: No content modification.
90 re_filterfile ./re_filterfile
93 # The logfile is where all logging and error messages are written.
94 # The logfile can be useful for tracking down a problem with
95 # Junkbuster (e.g., it's not blocking an ad you think it should
96 # block) but in most cases you probably will never look at it.
98 # Your logfile will grow indefinitely, and you will probably want to
99 # periodically remove it. On Unix systems, you can do this with a
100 # cron job (see 'man cron').
102 # On SuSE Linux systems, you can place a line like
103 # "/var/log/junkbuster.* +1024k 644 nobody.nogroup" in /etc/logfiles,
104 # with the effect that cron.daily will automatically archive, gzip,
105 # and empty the log, when it exceeds 1M size.
107 # Default: Log to the standard error channel, not to a file
109 logfile ./junkbuster.log
112 # The jarfile defines where Junkbuster stores the cookies it
113 # intercepts. Note that if you use a jarfile, it may grow quite
116 # Default: Don't store intercepted cookies
121 # The forwardfile defines domain-specific forwarding of HTTP
122 # requests. In some cases, you may want Junkbuster to forward your
123 # request to another proxy instead of trying to fetch the request
124 # itself. In those cases, you can use the forwardfile to indicate
125 # which requests should be forwarded and to where.
127 # Default: Make all connections directly.
129 forwardfile ./forward
132 # Generally, Junkbuster is used as a personal proxy. The default
133 # behaviour of Junkbuster is to listen on port 8000 on the "loopback"
134 # interface, so that it will only listen to local requests from the
135 # same machine. Using 'listen-address' (see below) you can serve
136 # requests from other machines as well.
138 # In that case, it is a wise thing to define access control lists
139 # (acls), which state who can connect to your proxy and what service
140 # they will be given. Note that setting the listen-address to an IP
141 # address that is only internally reachable from your local network
142 # might already do the trick.
144 # Default: No access control. Everybody that can reach junkbuster
152 # This part of the configuration file contains options that control
153 # how Junkbuster operates.
157 # Listen-address specifies the address and port where Junkbuster will
158 # listen for connections from your Web browser. The default is to
159 # listen on the local host on port 8000, and this is suitable for
160 # most users. (In your web browser, under proxy configuration, list
161 # the proxy server as 'localhost' and the port as '8000').
163 # If you already have another service running on port 8000, or if you
164 # want to serve requests from other machines (e.g. on your local
165 # network) as well, you will need to override the default. The syntax
166 # is "listen-address [<ip-address>]:<port>" If you leave out the ip
167 # adress, junkbuster will bind to all interfaces (addresses) on your
168 # machine and may become reachable from the internet. In that case,
169 # consider using access control lists (acl's) (see "aclfile" above).
171 # For example, suppose you are running Junkbuster on a machine which
172 # has the address 192.168.0.1 on your local private network
173 # (192.168.0.0) and has another outside connection with a different
174 # address. You want it to serve requests from inside only:
176 # listen-address 192.168.0.1:8000
178 # If you want it to listen on all addresses (including the outside
181 # listen-address :8000
183 # If you do this, consider using acls (see "aclfile" above).
185 # Note: you will need to point your browser(s) to the address
186 # and port that you have configured here.
188 # Default: listen-address localhost:8000
189 # listen-address 127.0.0.1:8000
194 # The debug option sets the level of debugging information to log in
195 # the logfile (and to the console in the Windows version). A debug
196 # level of 1 is informative because it will show you each request as
197 # it happens. Higher levels of debug are probably only of interest
200 # debug 1 # GPC = show each GET/POST/CONNECT request
201 # debug 2 # CONN = show each connection status
202 # debug 4 # IO = show I/O status
203 # debug 8 # HDR = show header parsing
204 # debug 16 # LOG = log all data into the logfile
205 # debug 32 # FRC = debug force feature
206 # debug 64 # REF = debug regular expression filter
207 # debug 128 # RED = debug fast redirects
208 # debug 256 # CLF = Common Log Format
209 # debug 4096 # INFO = Startup banner and warnings.
210 # debug 8192 # ERROR = Non-fatal errors
212 # It is *highly recommended* that you enable ERROR
213 # reporting. (debug 8192).
215 # The reporting of FATAL errors (i.e. ones which crash
216 # JunkBuster) is always on and cannot be disabled.
218 # If you want to use CLF, you should set "debug 256" ONLY,
219 # do not enable anything else.
221 # Multiple "debug" directives, are OK - they're logical-OR'd
224 # debug 15 # same as setting the first 4 listed above
226 # Default: 0, i.e. log nothing but fatal errors
230 debug 8192 # Errors - *we highly recommended enabling this*
233 # Junkbuster normally uses "multi-threading", a software technique
234 # that permits it to handle many different requests simultaneously.
235 # In some cases you may wish to disable this -- particularly if
236 # you're trying to debug a problem. The 'single-threaded' option
237 # forces Junkbuster to handle requests sequentially.
239 # Default: Multithreaded mode
244 # 'toggle' allows you to temporarily disable all Junkbuster's
245 # filtering. Just set "toggle 0".
247 # The Windows version of Junkbuster puts an icon in the system
248 # tray, which allows you to change this option without having
249 # to edit this file. If you right-click on that icon (or select
250 # the 'Options' menu), one choice is "Enable". Clicking on enable
251 # toggles Junkbuster on and off. This is useful if you want to
252 # temporarily disable Junkbuster, e.g., to access a site that
253 # requires cookies which you normally have blocked.
255 # 'toggle 1' means Junkbuster runs normally, 'toggle 0' means
256 # that Junkbuster becomes a non-anonymizing non-blocking
264 # 5. WINDOWS GUI OPTIONS
266 # Junkbuster has a number of options specific to the Windows GUI
269 # activity-animation {1 or 0}
271 # If set to 1, the Junkbuster icon will animate when Junkbuster is
274 #Win32-only: activity-animation 1
276 # log-messages {1 or 0}
278 # If set to 1, Junkbuster will log messages to the console window.
280 #Win32-only: log-messages 1
282 # log-buffer-size {1 or 0}?
284 # If log-buffer-size is set to 1, the size of the log buffer, that
285 # is the amount of memory used for the log messages displayed in
286 # the console window, will be limited to 'log-max-lines' (see below).
288 # Warning: Setting this to 0 will result in the buffer to grow
289 # infinitely and eat up all your memory!
291 #Win32-only: log-buffer-size 1
293 # log-max-lines {number of lines, e.g., '200'}
295 # Maximum number of lines held in the log buffer. See above.
297 #Win32-only: log-max-lines 200
299 # log-highlight-messages {1 or 0}
301 # If set to 1, Junkbuster will highlight portions of the log
302 # messages with a bold-faced font.
304 #Win32-only: log-highlight-messages 1
306 # log-font-name {font name, e.g., 'Comic Sans MS'}
308 # The font used in the console window.
310 #Win32-only: log-font-name Comic Sans MS
312 # log-font-size {font size in points, e.g., '8'}
314 # Font size used in the console window.
316 #Win32-only: log-font-size 8
318 # show-on-task-bar {1 or 0}
320 # Controls whether or not Junkbuster will appear as a button on the Task
321 # bar when minimized.
323 #Win32-only: show-on-task-bar 0
326 # close-button-minimizes 1
328 # If set, the Windows close button will minimize Junkbuster instead
329 # of closing the program (close with the exit option on the File
332 #Win32-only: close-button-minimizes 1
336 # If this option is used, Junkbuster will disconnect from and hide
337 # the command console.
339 #Win32-only: #hide-console
341 # Note: Junkbuster is distributed under the GNU General Public License (GPL)
342 # For details, see http://www.gnu.org/copyleft/gpl.html