1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
\r
4 See copyright details at end of file
\r
6 After changing this file, please run it through "HTML Tidy"
\r
7 (from http://www.w3.org/People/Raggett/tidy/)
\r
8 It should have no warnings or errors.
\r
13 <title>Internet Junkbuster Frequently Asked Questions</title>
\r
14 <meta name="description" content=
\r
15 "An extensive FAQ on the Internet Junkbuster, free software to removes banner ads, cookies, and other stuff you don't want from your web browser.">
\r
16 <meta name="keywords" content=
\r
17 "stop, junk, busters, junkbusters, junkbuster, mail, email, e-mail, direct, spam, privacy, sharing, names, renting, direct, marketing, database, databases, junk mail, lists, consumer, sending, opt out, privacy, advertising, direct, marketing, targeting, through, click, trails, http_referer, cookie, cutter, iff, internet fast forward, Cookie Management Tool">
\r
18 <style type="text/css">
\r
20 h2 { text-align: Center; font-family: arial, helvetica, sans-serif }
\r
21 p.sans { font-family: arial, helvetica, sans-serif }
\r
22 b.dot { color: #FF0000 }
\r
23 b.eg { font-family: arial, helvetica, sans-serif }
\r
28 <body bgcolor="#f8f8f0" link="#000078" alink="#ff0022" vlink=
\r
30 <p class="sans"><a href="http://ijbswa.sourceforge.net">
\r
31 Website</a> <b class="dot">·</b> <a href="ijbman.html">
\r
32 Manual</a> <b class="dot">·</b> <b>FAQ</b> <b class=
\r
33 "dot">·</b> <a href="gpl.html">GPL</a></p>
\r
35 <h1 align="center"><a name="top_of_page"></a>Internet
\r
36 J<small>UNK<i style="color: #FF0000">BUSTER</i></small>
\r
37 Frequently Asked Questions</h1>
\r
39 <p align="center" class="sans"><a href="#browser">Configuring
\r
40 Browsers</a> <b class="dot">·</b> <a href="#defaulted">
\r
41 IE 5.0</a> <b class="dot">·</b> <a href="#local">
\r
42 Installation</a> <b class="dot">·</b> <a href=
\r
43 "#companies">For Companies</a> <b class="dot">·</b> <a
\r
44 href="#blocking">Blocking Ads</a> <b class="dot">·</b>
\r
45 <a href="#cookies">Cookies</a> <b class="dot">·</b> <a
\r
46 href="#hotmail">Hotmail</a> <b class="dot">·</b> <a
\r
47 href="#children">Children</a> <b class="dot">·</b> <a
\r
48 href="#chain">Forwarding/Chaining</a> <b class="dot">
\r
49 ·</b> <a href="#conceal">IP</a> <b class="dot">
\r
50 ·</b> <a href="#anonymity">Anonymity</a> <b class="dot">
\r
51 ·</b> <a href="#security">Security</a></p>
\r
53 <h1>This document is out of date</h1>
\r
55 <p><b>Development of JunkBuster is ongoing and this document is
\r
56 no longer current. However, it may provide some assistance. If
\r
57 you have problems, please use the <a href=
\r
58 "http://groups.yahoo.com/group/junkbuster-users/">Yahoo Groups
\r
59 mailing list</a> (which includes an archive of mail), the
\r
60 SourceForge.net <a href=
\r
61 "http://sourceforge.net/projects/ijbswa/">project page</a>, or
\r
62 see the project's <a href="http://ijbswa.sourceforge.net/">home
\r
63 page</a>. Please also bear in mind that versions 2.9.x of
\r
64 JunkBuster are development releases, and are not production
\r
67 <h2><a name="top"></a>The Top Ten Questions</h2>
\r
69 <h3><a name="what"></a><img border="0" src="fb.gif" alt="*"
\r
70 width="14" height="14"> What is the Internet Junkbuster
\r
71 Proxy and what does it do for me?</h3>
\r
73 <p>The Internet Junkbuster Proxy <small><sup>TM</sup></small>
\r
74 is free privacy-enhancing software that can be run on your PC
\r
75 or by your ISP or company. It blocks requests for URLs
\r
76 (typically banner ads) that match its blockfile. It also
\r
77 deletes unauthorized cookies and other unwanted identifying
\r
78 header information that is exchanged between web servers and
\r
79 browsers. These headers are not normally accessible to users
\r
80 (even though they may contain information that's important to
\r
81 your privacy), but with the Internet Junkbuster you can see
\r
82 almost <a href="ijbman.html#o_d">anything you want</a> and
\r
83 control everything you're likely to need. Many people publish
\r
84 their blockfiles to help others get started.</p>
\r
86 <h3><a name="free"></a><img border="0" src="fb.gif" alt="*"
\r
87 width="14" height="14"> Is there a license fee / warranty
\r
88 / registration form / expiration?</h3>
\r
90 <p>No, none of these. It's completely free of charge.
\r
91 Junkbusters offers you the software to copy, use, modify and
\r
92 distribute as you wish, forever, at no charge under the GNU
\r
93 General Public License.</p>
\r
95 <p><a name="warranty"></a>It comes with no warranty of any
\r
98 <p><a name="register"></a>You don't have to register, in fact
\r
99 we don't even provide a way to do so: the practice of
\r
100 registering software is usually just an excuse to send you
\r
101 solicitations and sell your name and information about your
\r
102 behavior. You are welcome to obtain and use our software as
\r
103 anonymously you wish. (Your IP address will naturally be
\r
104 disclosed when you download it; use anonymizing software if you
\r
105 want to conceal this. We never want to be given any information
\r
106 that you consider private or confidential.)</p>
\r
108 <p><a name="why"></a>We are often asked why we give away a
\r
109 product that many would happily pay for. The answer is that we
\r
110 are determined to carry out our mission: to free the world from
\r
111 junk communications.</p>
\r
113 <h3><a name="windows"></a><img border="0" src="fb.gif" alt="*"
\r
114 width="14" height="14"> Does it run on Windows? On a Mac?
\r
115 On the AOL browser?</h3>
\r
117 <p>For the latest information on availability, see the
\r
118 Distribution Information page. We don't think it will ever run
\r
119 on Windows 3.1. But you don't need to have it running on your
\r
120 computer if you get your ISP or Systems Administrator at work
\r
123 <h3><a name="isp"></a><img border="0" src="fb.gif" alt="*"
\r
124 width="14" height="14"> How can I get my ISP to run the
\r
125 Internet Junkbuster?</h3>
\r
127 <p>Try their sales or support department (depending on whether
\r
128 you are already a customer). <a name="unaware"></a>You might
\r
129 send them email including the following URL:<br>
\r
130 <code>
\r
131 http://www.junkbusters.com/ht/en/ijbfaq.html#isps</code><br>
\r
132 <a name="switch"></a>You could mention that many other ISPs
\r
133 provide it, and that you regard it as an important part of your
\r
134 decision on where to buy Internet service.</p>
\r
136 <h3><a name="who"></a><img border="0" src="fb.gif" alt="*"
\r
137 width="14" height="14"> Who chooses the options that
\r
138 control what is blocked?</h3>
\r
140 <p>Whoever starts the Internet Junkbuster chooses the options
\r
141 and the blockfile. If your ISP runs it for you, they have to
\r
142 make these decision (though some may give you a choice of
\r
143 proxies, and a way to suggest new URLs to block). If you run it
\r
144 on your computer, you get to choose.</p>
\r
146 <h3><a name="self"></a><img border="0" src="fb.gif" alt="*"
\r
147 width="14" height="14"> How do I download and run the
\r
148 program on my computer?</h3>
\r
150 <p>It depends on your platform. If you are using Windows 95 or
\r
151 NT, see our separate page on installing under Windows. If you
\r
152 have a C compiler and are using almost any flavor of UNIX ®
\r
153 you download it, compile it, start it running, and then
\r
154 configure your browser. Several precompiled packages are also
\r
155 available through links in our distribution page, which lists
\r
156 all available platforms.</p>
\r
158 <p><a name="port"></a>If you are using a platform for which we
\r
159 have no current availability, you are welcome to port the code.
\r
160 If you do this and you would like us to consider publishing
\r
161 your ported version, please tell us.</p>
\r
163 <h3><a name="show"></a><img border="0" src="fb.gif" alt="*"
\r
164 width="14" height="14"> How can I tell which blockfile
\r
165 and options are being used?</h3>
\r
167 <p>Just point your browser to
\r
168 http://internet.junkbuster.com/cgi-bin/show-proxy-args or to
\r
169 any URL ending in <code>show-proxy-args</code> (even if it
\r
170 doesn't exist). It needn't exist because the Internet
\r
171 Junkbuster intercepts the request, blocks it, and returns in
\r
172 its place information about itself. Using the URL above is
\r
173 useful for checking that your browser really is going through
\r
174 an Internet Junkbuster, because the <code>junkbuster.com</code>
\r
175 server returns a warning if the request actually gets to it.
\r
176 Some people set the home page of their browser to such a URL to
\r
177 be sure that it is configured to use the proxy.</p>
\r
179 <p><a name="headers"></a>If you wish to check the header
\r
180 information your proxy is actually sending, a visit to
\r
181 http://internet.junkbuster.com/cgi-bin/show_http_headers will
\r
182 give you the more relevant ones first. You might also like to
\r
183 turn the proxy off and compare the difference. (Don't forget to
\r
184 turn it back on again.)</p>
\r
186 <h3><a name="responding"></a><img border="0" src="fb.gif" alt=
\r
187 "*" width="14" height="14"> My browser started giving me
\r
188 ``server not responding'' messages</h3>
\r
190 <p>Once your browser is told to use a proxy such as the
\r
191 Internet Junkbuster, it thinks of it as its server for
\r
192 everything, so this message means it can't talk to the proxy.
\r
193 The Internet Junkbuster may not be running, or you may have
\r
194 specified its proxy address incorrectly. Check that the details
\r
195 you entered are correct. If you have <code>telnet</code> you
\r
196 can try connecting to the appropriate port to see if the
\r
197 Internet Junkbuster is running. If your ISP is running the
\r
198 Internet Junkbuster, you may want to check with them. If you
\r
199 are running it yourself under UNIX ®, try looking at a
\r
200 <code>ps ax</code> to see if it is running. The <a href=
\r
201 "ijbman.html#o_h">port</a> specified in its options should be
\r
202 the same one as your browser has configured.</p>
\r
204 <h3><a name="idea"></a><img border="0" src="fb.gif" alt="*"
\r
205 width="14" height="14"> I've got this great idea for a
\r
206 new feature. Who do I tell?</h3>
\r
208 <p>We'd be very interested to hear it, but please bear a few
\r
209 things in mind.</p>
\r
212 <li><a name="considered"></a>Please check this FAQ to see if
\r
213 we've already considered the idea, such as automatic
\r
214 detection of banner ads and replacing ads with something else
\r
215 such as a transparent GIF.</li>
\r
217 <li><a name="confidential"></a>Don't tell us anything you
\r
218 want to keep confidential or retain some right over.</li>
\r
220 <li><a name="wish"></a>We currently have a long wish list of
\r
221 things that we may or may not do in the near future,
\r
222 including a version for your favorite computer and a plug-in
\r
225 <li><a name="go4it"></a>If you don't want to wait you're
\r
226 welcome to improve on our code, publish your version on the
\r
227 Web, and tell us where to find it. Projects that are
\r
228 especially welcome include a port to the Mac and extensions
\r
229 for HTTP 1.1. (Meanwhile, be sure your browser is configured
\r
230 not to use HTTP 1.1.)</li>
\r
233 <h3><a name="other"></a><img border="0" src="fb.gif" alt="*"
\r
234 width="14" height="14"> My question isn't listed here.
\r
235 Who do I ask for support?</h3>
\r
237 <p><a name="harder"></a>If you find using our free product
\r
238 harder than you're used to for consumer software, there are
\r
239 many commercial alternatives that you could consider.</p>
\r
241 <p><a name="RTM"></a>The answer to detailed technical questions
\r
242 may be answered in <a href="ijbman.html">manual page</a>, or in
\r
243 the source code. Also double-check this page for an answer:
\r
244 using the ``find'' feature on your browser for likely keywords
\r
245 may help. Our site also has a search feature.</p>
\r
247 <p><a name="Use"></a>Many people post requests for help and
\r
248 responses on Usenet.</p>
\r
250 <p><a name="them"></a>If your ISP is providing the Internet
\r
251 Junkbuster for you, and your question is about how to use it,
\r
252 check their web page before asking them.</p>
\r
254 <p><a name="us"></a>Even though we don't offer the kind of
\r
255 support you might expect if you paid a lot of money for a
\r
256 software product, you can still ask us. But before you do,
\r
257 please consider whether you could ask someone closer to you.
\r
258 And please be patient if we're slow to reply: we never charge
\r
259 consumers for our services, so we have to subsidize consumers
\r
260 with revenue from companies, and our resources are limited.</p>
\r
262 <p><a name="quote"></a>If your company or organization would be
\r
263 interested in a maintenance contract with phone and email
\r
264 support, hard copy documentation and source code and
\r
265 pre-compiled binaries on tape or disk, please ask us for a
\r
268 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
269 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
272 <h2><a name="browser"></a>Configuring your browser to talk to
\r
273 the Internet Junkbuster</h2>
\r
275 <h3><a name="address"></a><img border="0" src="fb.gif" alt="*"
\r
276 width="14" height="14"> What is the proxy address of the
\r
277 Internet Junkbuster?</h3>
\r
279 <p><a name="localhost"></a>If you set up the Internet
\r
280 Junkbuster to run on the computer you browse from (rather than
\r
281 your ISP's server or some networked computer at work), the
\r
282 proxy will be on <code>localhost</code> (which is the special
\r
283 name used by every computer on the Internet to refer to itself)
\r
284 and the port will be <code>8000</code> (unless you have told
\r
285 the Internet Junkbuster to run on a different port with the <a
\r
286 href="ijbman.html#listen-address">listen-address</a> option).
\r
287 So you when configuring your browser's proxy settings you
\r
288 typically enter the word <code>localhost</code> in the two
\r
289 boxes next to <b class="eg">HTTP</b> and <b class="eg">
\r
290 Secure</b>, and the number <code>8000</code> in the two boxes
\r
291 labeled to the right of those boxes. <a name="Gopher"></a>The
\r
292 Internet Junkbuster does not currently handle other protocols
\r
293 such as Gopher, FTP, or WAIS, so leave those setting unchanged.
\r
294 Nor does it handle ICQ or Instant Messenger services.</p>
\r
296 <p><a name="remote"></a>If your ISP or company is running the
\r
297 Internet Junkbuster for you, they will tell you the address to
\r
298 use. It will be the name of the computer it's running on (or
\r
299 possibly its numeric IP address), plus a port number. Port 8000
\r
300 is the default, so assume this number if it is not specified.
\r
301 Sometimes a colon is used to glue them together, as in <code>
\r
302 junkbuster.fictitious-pro-privacy-isp.net:8000</code> but with
\r
303 most browsers you do not type the colon, you enter the address
\r
304 and port number in separate boxes.</p>
\r
306 <h3><a name="set"></a><img border="0" src="fb.gif" alt="*"
\r
307 width="14" height="14"> How do I tell the browser where
\r
308 to find the Internet Junkbuster?</h3>
\r
310 <p>All current browsers can be told the address of a proxy to
\r
311 use. You enter the same information in two fields in your
\r
312 browser's proxy configuration screen (see list below): one for
\r
313 HTTP, and one for the Secure Protocol (assuming your browser
\r
314 supports SSL). If you find some information already entered for
\r
315 your proxy, see the next question. Here are the menus you go
\r
316 through to get to the proxy configuration settings. (We also
\r
317 recommend that you disable Java, which is a separate
\r
318 operation.) <strong>Make notes on the changes you make so you
\r
319 know how to undo them!</strong> You will need to know what you
\r
320 did in case you wish to discontinue using the proxy.</p>
\r
323 <li><a name="netscape"></a>For Netscape 2.01, 2.02 and 3.0
\r
324 [Graphic Illustration]: <b class="eg">Options</b>; <b class=
\r
325 "eg">Network Preferences</b>; <b class="eg">Proxies</b>; <b
\r
326 class="eg">Manual Proxy Configuration View ;</b> enter proxy
\r
327 address details under <b class="eg">HTTP</b> and <b class=
\r
328 "eg">Security Proxy</b>; click on <b class="eg">OK</b>; click
\r
329 on the next <b class="eg">OK</b>. [Return to Windows
\r
330 Installation Procedure]<br>
\r
331 With Netscape 2.0, follow with <b class="eg">Options</b>, <b
\r
332 class="eg">Save Options</b>.<br>
\r
333 <a name="Netscape4.02"></a>With Netscape 4.X series, you
\r
334 first have to go through <b class="eg">Edit/Preferences</b>.
\r
335 [Graphic Illustration] Then in the frame on the left, click
\r
336 on triangle pointing to the right towards the word <b class=
\r
337 "eg">Advanced</b>; it will switch to a triangle pointing
\r
338 down; and the words <b class="eg">Cache</b>, <b class="eg">
\r
339 Proxies</b> and <b class="eg">Disk Space</b> appear. Click on
\r
340 <b class="eg">Proxies</b> and the frame on the right will
\r
341 display a banner saying <b class="eg">Proxies Configure
\r
342 proxies to access the Internet</b>. Click the radio button
\r
343 labeled <b class="eg">Manual proxy configuration</b> then
\r
344 click the button labeled <b class="eg">View</b>; enter proxy
\r
345 address details under <b class="eg">HTTP</b> and <b class=
\r
346 "eg">Security Proxy</b>; click on <b class="eg">OK</b>; click
\r
347 on the next <b class="eg">OK</b>. [Return to Windows
\r
348 Installation Procedure]</li>
\r
350 <li><a name="explorer3"></a>For Internet Explorer 3.0
\r
351 [Graphic Illustration]: <b class="eg">View</b>; <b class=
\r
352 "eg">Options</b>; <b class="eg">Connections</b>; tick <b
\r
353 class="eg">Connect through proxy server</b> box; <b class=
\r
354 "eg">Settings</b>; enter proxy address details <b class="eg">
\r
355 HTTP</b> Box, with port number in the second box; same with
\r
356 <b class="eg">Secure</b>; click on <b class="eg">OK</b>.
\r
357 [Return to Windows Installation Procedure]</li>
\r
359 <li><a name="explorer2"></a>For Internet Explorer 2.0: <b
\r
360 class="eg">View</b>; <b class="eg">Options</b>; <b class=
\r
361 "eg">Proxy</b>; enter proxy address details click on <b
\r
362 class="eg">OK</b>. [Return to Windows Installation
\r
365 <li><a name="nt"></a>On NT for MS-IE: <b class="eg">Control
\r
366 Panel</b>; <b class="eg">Internet</b>; <b class="eg">
\r
367 Advanced</b>; <b class="eg">Proxy</b>.</li>
\r
369 <li><a name="if"></a>For MS-IE 4.0: similar to 3.0: <b class=
\r
370 "eg">View</b>; <b class="eg">Internet Options</b>; <b class=
\r
371 "eg">Connection</b>; tick <b class="eg">Access Internet using
\r
372 a proxy server</b> box; from there we have had reports of
\r
373 different versions, either click on <b class="eg">
\r
374 Advanced</b> or <b class="eg">Settings</b>; enter proxy
\r
375 address details <b class="eg">HTTP</b> Box, with port number
\r
376 in the second box; same with <b class="eg">Secure</b>; click
\r
377 on <b class="eg">OK</b>. Note that 4.0 has <b class="eg">
\r
378 Advanced</b> settings to allow HTTP 1.1 through proxies;
\r
379 these must be disabled because the proxy does not currently
\r
380 understand HTTP 1.1. Please tell us if you see any other
\r
381 differences. [Return to Windows Installation Procedure]</li>
\r
383 <li><a name="IE5"></a>For MS-IE 5.0: similar to 4.0: <b
\r
384 class="eg">Tools|Internet Options</b> from the menu bar; <b
\r
385 class="eg">Connections</b>. Select either dial-up connection
\r
386 or LAN (depending on how you connect to the Internet); press
\r
387 <b class="eg">Settings</b>; and check the <b class="eg">Use
\r
388 Proxy Server</b> box; enter proxy address details in the <b
\r
389 class="eg">HTTP</b> Box, with port number in the second box;
\r
390 same with <b class="eg">Secure</b>; click on <b class="eg">
\r
391 OK</b> buttons to get out. <em>Note:</em> <a name=
\r
392 "defaulted"></a>You must also uncheck the HTTP 1.1 checkboxes
\r
393 at the end of the <b class="eg">Advanced</b> options. This
\r
394 seems to have been made the default in IE 5.0. [Return to
\r
395 Windows Installation Procedure]</li>
\r
397 <li><a name="level5"></a>For Netscape's level 5 browser, we
\r
398 have no information. If you do, please tell us.</li>
\r
400 <li><a name="mosaic"></a>For NCSA Mosaic for Windows: <b
\r
401 class="eg">Options</b>, <b class="eg">Preferences</b>, <b
\r
402 class="eg">Proxy</b>; enter proxy address details under <b
\r
403 class="eg">HTTP</b>.</li>
\r
405 <li><a name="Opera"></a>For Opera: <b class="eg">
\r
406 Preferences</b>, <b class="eg">Proxy servers</b>; check the
\r
407 box next to HTTP; enter the server and port number in the box
\r
408 on the other side; click on <b class="eg">OK</b>.</li>
\r
410 <li><a name="lynx"></a>For Lynx, Mosaic/X, <a href=
\r
411 "http://monty.cnri.reston.va.us/grail-0.3/">Grail,</a> and
\r
412 W3O Arena, you can specify the proxy via environment
\r
413 variables before starting the application. This will probably
\r
414 be done with something like either<br>
\r
415 <code>setenv http_proxy
\r
416 http://localhost:8000/</code><br>
\r
418 <code>
\r
419 http_proxy=http://junkbuster.fictitious-pro-privacy-isp.net:8000/
\r
420 export http_proxy</code><br>
\r
421 depending on your shell and where the Internet Junkbuster
\r
425 <p>If your browser is not listed here, or if you notice an
\r
426 error, please tell us the correct procedure.</p>
\r
428 <h3><a name="already"></a><img border="0" src="fb.gif" alt="*"
\r
429 width="14" height="14"> What should I do if I find
\r
430 another proxy is already configured?</h3>
\r
432 <p>Some ISPs and companies require all Web traffic to go
\r
433 through their proxy. In this case you would find your proxy
\r
434 configuration with values already set, possibly under <a name=
\r
435 "Automatic"></a>Automatic Proxy Configuration (in the case of
\r
436 Netscape and MS-IE 3.0 and above). It's probably a firewall
\r
437 proxy between your company and the outside world, <a name=
\r
438 "cache"></a>or a caching proxy if you're using an ISP.</p>
\r
440 <p><a name="f"></a>What needs to be done in this case is to use
\r
441 the <a href="ijbman.html#forwardfile">forwardfile</a> option to
\r
442 tell the Internet Junkbuster the address of the other proxy.
\r
443 Specify a different (unused) port number with the <a href=
\r
444 "ijbman.html#listen-address">listen-address</a> option, and
\r
445 configure your browser to use that port. If you haven't done
\r
446 this kind of thing before, it's probably best to consult your
\r
447 systems administrator or ISP about it; check their web page
\r
450 <h3><a name="discontinue"></a><img border="0" src="fb.gif" alt=
\r
451 "*" width="14" height="14"> What if I want to stop using
\r
452 the Internet Junkbuster?</h3>
\r
454 <p>Just go through the same procedure you used to start your
\r
455 browser using the Internet Junkbuster, but remove the details
\r
456 you put in (or if there was something there before, restore
\r
457 it). You may need to use <b class="eg">Save Options</b> to make
\r
458 this change permanent. On Netscape 3.0 you can go through <b
\r
459 class="eg">Options</b>; <b class="eg">Network Preferences</b>;
\r
460 <b class="eg">Proxies</b> and click on <b class="eg">No
\r
461 Proxy</b> to turn it off, and later click on <b class="eg">
\r
462 Manual Proxy Configuration</b> if you want to start using it
\r
463 again. (No need to enter the again details under <b class="eg">
\r
464 View</b> as you did the first time; they should remain there
\r
467 <p><a name="shut"></a>This stops your browser talking to the
\r
468 proxy; shutting down the proxy is a different matter.</p>
\r
470 <h3><a name="dial"></a><img border="0" src="fb.gif" alt="*"
\r
471 width="14" height="14"> Automatic dialing isn't working
\r
472 any more. How do I fix it?</h3>
\r
474 <p>Some browsers (such as MSIE-4) can be configured to dial
\r
475 your ISP automatically when you click on a link, but this
\r
476 feature (called "automatically connect" or "autoconnect") gets
\r
477 disabled if you specify a proxy running on your own computer
\r
478 (with address <code>localhost</code> or <code>127.0.0.1</code>)
\r
479 because these addresses don't require dialing. The Internet
\r
480 Junkbuster knows nothing about dialing, so it doesn't work. To
\r
481 make automatic dialing work, make up a name such as <code>
\r
482 junkbuster.ijb</code> and use that name in the proxy settings
\r
483 instead of <code>localhost</code>, and then add the line <code>
\r
484 127.0.0.1 junkbuster.ijb</code> to the file <code>
\r
485 c:\windows\hosts</code> (if there already is a line beginning
\r
486 with <code>127.0.0.1</code> just add <code>
\r
487 junkbuster.ijb</code> at the end of it.)</p>
\r
489 <p><a name="also"></a>This should also work Netscape
\r
490 Communicator 4 on machines where IE-4 has been installed.</p>
\r
492 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
493 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
496 <h2><a name="local"></a>Setting up the Internet Junkbuster on
\r
497 your local computer</h2>
\r
499 <p>The next two sections assume you wish to compile the code
\r
500 with your own C compiler. <a name="install"></a>If you just
\r
501 want to use the <code>.exe</code> file provided for Windows,
\r
502 see the Windows Installation page.</p>
\r
504 <h3><a name="u"></a><img border="0" src="fb.gif" alt="*" width=
\r
505 "14" height="14"> How do I compile the code under
\r
508 <p>If you are running Redhat Linux you may prefer to use the
\r
509 rpm instead of the following procedure.</p>
\r
512 <li><a name="download"></a>First download the tar file
\r
513 (~286k) <a name="tar"></a>and uncompress and extract the
\r
514 files from it with this command<br>
\r
515 <code>uncompress -c ijb20.tar.Z | tar xf
\r
518 <li><a name="sun"></a>If your operating system is from Sun or
\r
519 HP examine the <code>Makefile</code> and make any changes
\r
520 indicated inside.</li>
\r
522 <li><a name="make"></a>Run<br>
\r
524 <code>make</code></li>
\r
527 <a name="defaults"></a>Copy the sample configuration file
\r
528 (<code>junkbstr.ini</code>, previously called <code>
\r
529 sconfig.txt</code> and other names in earlier releases) to
\r
530 some convenient place such as <code>
\r
531 /usr/local/lib/junkbuster/configfile</code> or whatever you
\r
532 choose. The sample file has all the options commented out.
\r
533 You can remove the <code>#</code> character on any that you
\r
534 want, but it may be better to leave this until to later.
\r
535 Run it asynchronously:<br>
\r
537 <code>junkbuster configfile &</code>
\r
540 <p>If you are running a version earlier than 2.0 you can
\r
541 start it with <code>junkbuster &</code></p>
\r
544 <li><a name="config"></a>Configure your browser (described
\r
547 <li><a name="test"></a>Verify that the Internet Junkbuster is
\r
548 working (described above).</li>
\r
550 <li><a name="restart"></a>Decide on the options you really
\r
551 want, <code>kill</code> the process and start it again. The
\r
552 most popular option is <a href="ijbman.html#blockfile">
\r
553 blockfile</a> to block ads. <a name="comprehensive"></a>A
\r
554 sample blockfile is provided as an illustration, but it
\r
555 doesn't really stop many ads. More comprehensive ones are
\r
556 available elsewhere.</li>
\r
558 <li><a name="rc"></a>You'll probably want to add an entry to
\r
559 <code>/etc/rc.d/rc.local</code> or equivalent to start it at
\r
560 boot time. (Any output you specify should be redirected to a
\r
561 file. And don't forget the & at the end to run it
\r
562 asynchronously or your system will seize up after the next
\r
566 <h3><a name="win"></a><img border="0" src="fb.gif" alt="*"
\r
567 width="14" height="14"> How do I compile the code under
\r
570 <p>A <code>.exe</code> file (binary) is supplied with the
\r
571 source code, but if you prefer to compile it yourself here is
\r
572 the likely procedure. Most of these steps are repeated in our
\r
573 checklist for installation under Windows.</p>
\r
576 <li><a name="zip"></a>First click here to download the zip
\r
577 file called <code>ijb20.zip</code> (~208k), then uncompress
\r
578 and unpack the zip archive using a tool like WinZip.</li>
\r
580 <li><a name="change"></a>Now the distribution (source and
\r
581 sample files) will be in a folder called <code>ijb20</code>.
\r
582 Go into that folder and then edit the Makefile for your
\r
583 system, removing the comment character (<code>#</code>) in
\r
584 the lines related to Win32. Then type:<br>
\r
585 <code>nmake</code><br>
\r
586 This should create an executable called <code>
\r
587 junkbstr.exe</code>. <a name="compilers"></a>For information
\r
588 on issues with various compilers, see the Distribution
\r
589 Information page.</li>
\r
592 <a name="attempt"></a>Run the executable with the
\r
594 <code>junkbstr</code><br>
\r
595 <a name="terminal"></a>(Click on the icon with that name
\r
596 that looks like a terminal, not like a notepad.) The
\r
597 program will produce a message indicating that it has
\r
598 started and is ready to serve.
\r
600 <p><a name="ini"></a>(Version 2.0.1 and above uses the file
\r
601 <code>junkbstr.ini</code> as the config file if it exists
\r
602 and no argument was given. If you have an earlier version
\r
603 or if you want it to use a different config file, simply
\r
604 specify that file as the argument.)</p>
\r
607 <li><a name="configures"></a>Configure your browser
\r
608 (described above).</li>
\r
610 <li><a name="work"></a>Check the proxy is working (described
\r
614 <a name="shortcut"></a>To have the proxy start itself
\r
615 automatically when you login to Win95, drop the
\r
616 ``shortcut'' to the <code>junkbstr</code> executable into
\r
617 the StartUp folder:<br>
\r
618 <code>C:\Windows\Start
\r
619 Menu\Programs\StartUp</code><br>
\r
620 You might want to change the shortcut's <code>
\r
621 Properties->Shortcut</code> to <code>Run:
\r
622 Minimized</code>. If you specify the <a href=
\r
623 "ijbman.html#hide-console">hide-console</a> option then the
\r
624 DOS window will vanish after it starts.
\r
626 <p><a name="NT"></a>WinNT users can put it into their own
\r
627 StartUp folders or the Administrator can put it into the
\r
628 system's global StartUp folder. For details on how to make
\r
629 this a service under NT see our Windows page.</p>
\r
633 <h3><a name="check"></a><img border="0" src="fb.gif" alt="*"
\r
634 width="14" height="14"> How do I check that the proxy is
\r
637 <p>Pick a page from somewhere (such as your bookmarks, or just
\r
638 one that your browser was pointing to) and <b class="eg">
\r
639 Reload</b> it. If you get a message along the lines of ``server
\r
640 not responding, using cached copy instead,'' see the advice
\r
641 above. If the page reloads OK, check that your browser is
\r
642 actually talking to the proxy by going to
\r
643 http://internet.junkbuster.com/cgi-bin/show-proxy-args or any
\r
644 URL ending in <code>show-proxy-args</code> (as described below,
\r
645 the proxy should intercept the request.) When you see
\r
646 ``Internet Junkbuster Proxy Status,'' you'll know it's
\r
649 <h3><a name="chain"></a><img border="0" src="fb.gif" alt="*"
\r
650 width="14" height="14"> How and why would I have this
\r
651 proxy chained with other proxies?</h3>
\r
653 <p>You may need the <a href="ijbman.html#forwardfile">
\r
654 forwarding</a> feature to ``daisy chain'' the Internet
\r
655 Junkbuster to another proxy, perhaps an anonymizing proxy to
\r
656 conceal your IP address, or a caching proxy from your ISP, or a
\r
657 firewall proxy between your company and the outside world.
\r
658 Version 2.0 and above can be even configured to forward <a
\r
659 href="ijbman.html#forwardfile">selectively</a> according to the
\r
660 URL requested: for example, connecting directly to trusted
\r
661 hosts, but going through an anonymizing or firewall proxy for
\r
662 all other hosts.</p>
\r
664 <p><a name="administrator"></a>Network administrators might use
\r
665 it to provide transparent access to multiple networks without
\r
666 modifying browser configurations. <a name="direct"></a>Most
\r
667 browsers also provide a way of specifying hosts that the
\r
668 browser connects to directly, bypassing the proxy. Some provide
\r
669 a method for Automatic Proxy Configuration. A well written
\r
670 Internet Junkbuster configuration can be much more flexible and
\r
673 <p><a name="example"></a>An ISP's caching proxy would typically
\r
674 be called something like <code>cache.your-isp.net:8080</code>
\r
675 (as described on you ISP's web page); you would put this
\r
676 information in your <a href="ijbman.html#forwardfile">
\r
677 forwardfile</a> as described in our manual. Your browser would
\r
678 be configured to the Internet Junkbuster for HTTP and Security
\r
679 Proxies as before, but you probably want to tell it to use the
\r
680 caching proxy for FTP and other protocols. <a name="nonlocal">
\r
681 </a>If your ISP is running the Internet Junkbuster for you,
\r
682 they have probably already decided whether to chain with a
\r
685 <h3><a name="socks"></a><img border="0" src="fb.gif" alt="*"
\r
686 width="14" height="14"> How does the Internet Junkbuster
\r
687 work with SOCKS gateways?</h3>
\r
689 <p>There is support for some gateways in Version 1.4 and above.
\r
690 The gateway protocol used to be specified on the command line;
\r
691 it is now specified in the same file as <a href=
\r
692 "ijbman.html#forwardfile">forwarding.</a> Note that the
\r
693 browser's proxy configuration must <em>not</em> specify a
\r
694 <code>SOCKS</code> host; it should specify the proxy as
\r
695 described above.</p>
\r
697 <h3><a name="plain"></a><img border="0" src="fb.gif" alt="*"
\r
698 width="14" height="14"> How do I configure it to be just
\r
699 a plain old proxy?</h3>
\r
701 <p>To get the proxy to do as little as possible (which means
\r
702 not deleting any sensitive headers), place in your
\r
703 configuration file the following three lines (each ending in a
\r
704 space then a period) to stop it changing sensitive headers:<br>
\r
705 <code>referer .</code><br>
\r
706 <code>from .</code><br>
\r
707 <code>user-agent .</code><br>
\r
708 <code>cookiefile mycookiefile</code><br>
\r
709 The fourth line is also needed to specify a <a href=
\r
710 "ijbman.html#o_c">cookiefile</a> that might be called <code>
\r
711 mycookiefile</code> containing a single line with a <code>
\r
712 *</code> character, to allow all cookies through.</p>
\r
714 <h3><a name="shutdown"></a><img border="0" src="fb.gif" alt="*"
\r
715 width="14" height="14"> How do I shut down the proxy (to
\r
718 <p>It depends on your platform.</p>
\r
721 <li><a name="X"></a>Under Windows, you can click on the "X"
\r
722 button at the top right of the DOS window (and answer <b
\r
723 class="eg">Yes</b> when Windows warns you it cannot shut down
\r
724 the program automatically), or use <b class="eg">
\r
725 Ctrl-Break</b> or the old three-fingered salute of <b class=
\r
726 "eg">Ctrl-Alt-Delete</b> and select <b class="eg">End
\r
729 <li><a name="ps"></a>Under UNIX ® you'll need to <code>
\r
730 kill</code> the <b><code>junkbuster</code></b> process. <a
\r
731 name="pid"></a>If you don't know the process number to give
\r
732 to <code>kill</code>, try this:<br>
\r
733 <code>ps ax | grep junkbuster</code></li>
\r
736 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
737 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
740 <h2><a name="companies"></a> Information for companies</h2>
\r
742 <h3><a name="think"></a><img border="0" src="fb.gif" alt="*"
\r
743 width="14" height="14"> What do advertising companies
\r
744 think of this kind of technology?</h3>
\r
746 <p>We've seen only a few public comments from the advertising
\r
747 industry on this, other than SEC filings. First, the president
\r
748 of the Internet Advertising Bureau told CNET that he wasn't
\r
749 worried by banner blockers. Second, after the Federal Trade
\r
750 Commission's workshop where we gave a live demonstration of our
\r
751 proxy before many eminent representatives of the industry, the
\r
752 Direct Marketing Association made the following statement in
\r
753 the closing paragraphs of their summary comments to the
\r
757 Clever shareware developers have come up with products that
\r
758 can obliterate cookies and advertisements for those consumers
\r
759 who have these concerns. The Internet is a market that is so
\r
760 democratic and flexible that it is easy for companies and
\r
761 software developers to respond to a perceived market need.
\r
764 <p>Their attitude seems to be that they would prefer that
\r
765 people use technical solutions to protect their privacy than
\r
766 have protections imposed by legislation or government
\r
767 regulations. So, do you perceive a market need? Then here are
\r
768 some ways to flex your democratic muscles.</p>
\r
770 <h3><a name="nobrainer"></a><img border="0" src="fb.gif" alt=
\r
771 "*" width="14" height="14"> Should we provide the
\r
772 Internet Junkbuster for our employees?</h3>
\r
774 <p>That depends. Try this quick three-point test.</p>
\r
777 <li><a name="waste"></a>Do you want to spend your
\r
778 communications budget on bandwidth that wastes your
\r
779 employees' time by forcing them to wait for a lot of annoying
\r
780 distractions while they're trying to do their jobs?</li>
\r
782 <li><a name="surveillance"></a>Do you want current and
\r
783 potential vendors to know quantitative details about the
\r
784 software and hardware platforms that you have?</li>
\r
786 <li><a name="intelligence"></a>Do you want your competitors
\r
787 to be able to track exactly which of your employees are
\r
788 checking out their web sites?</li>
\r
791 <p>If the answer to all three questions is yes, then you
\r
792 probably don't have any need for this kind of product.</p>
\r
794 <h3><a name="commercial"></a><img border="0" src="fb.gif" alt=
\r
795 "*" width="14" height="14"> Can our company get
\r
796 commercial support for the software?</h3>
\r
798 <p>Yes, ask us for a quote on a maintenance contract with your
\r
799 choice of phone and email support, hard copy documentation,
\r
800 source code and pre-compiled binaries on tape or disk, and
\r
801 email alerting of upgrades and issues. We also offer consulting
\r
802 services to help set up ``stealth browsing'' capabilities to
\r
803 help reduce the footprints left while doing competitive
\r
804 analysis and other Web work where confidentiality is
\r
807 <h3><a name="isps"></a><img border="0" src="fb.gif" alt="*"
\r
808 width="14" height="14"> I run an ISP. What issues should
\r
809 I consider before offering it?</h3>
\r
811 <p>Many ISPs who offer the proxy to their customers have told
\r
812 us that most of their customers are delighted with it (although
\r
813 one reported that a customer complaint that without banner ads,
\r
814 surfing was like reading a novel: we recommend making it
\r
815 optional). Many ISPs like it because it reduces bandwidth
\r
816 requirements. To help get you started, here's a checklist we've
\r
817 developed from working with a few ISPs. You may think of more,
\r
818 and we'd be interested if you're willing to share them with
\r
822 <li><a name="pending"></a>If you get more than one request
\r
823 for the Internet Junkbuster you may want to tell your
\r
824 customers on your News page that you already know about it
\r
825 and are assessing it.</li>
\r
827 <li><a name="try"></a>Try the software and verify that it
\r
828 performs satisfactorily.</li>
\r
830 <li><a name="value"></a>Determine whether your customers
\r
831 perceive the service as valuable (and therefore worth the
\r
832 time to set up). We've had reports of many delighted
\r
835 <li><a name="secure"></a>Assess the level of security
\r
836 associated with the software. If access is to be restricted
\r
837 (to just dial-in ports, for example) how is this to be
\r
840 <li><a name="costs"></a>Consider whether to expect any
\r
841 additional load on computing resources required, and any
\r
842 change in use of bandwidth due to the blocking of large
\r
845 <li><a name="opt"></a>Choose the <a href="ijbman.html">
\r
846 options</a> you wish to provide.</li>
\r
849 <a name="multiple"></a>Decide whether you want to offer a
\r
850 choice of configurations, such some of these four.
\r
853 <li><a name="banner"></a>Banners Blocked, Wafer with
\r
854 No-Cookie-Copyright notice</li>
\r
856 <li><a name="low"></a>Cookies not stopped (<a href=
\r
857 "ijbman.html#cookiefile">cookiefile</a> with just a
\r
858 <code>*</code> in it), User Agent specified as Lynx</li>
\r
860 <li><a name="oneway"></a>Cookies from browser allowed,
\r
861 permitting registered services</li>
\r
863 <li><a name="kid"></a>A proxy for kids.</li>
\r
865 <a name="caching"></a>If you run a caching proxy, decide
\r
866 whether the Internet Junkbuster will chain with it by
\r
867 default, and whether to offer an alternate with no caching.
\r
868 (Some ISPs don't, because they want to give customers an
\r
869 incentive to use caching and save bandwidth.)
\r
872 <li><a name="naming"></a>Decide on a naming scheme for your
\r
873 proxies. If you're running only one proxy on one machine, the
\r
874 simplest way is to just use port 8000 on your main machine,
\r
875 such as <code>our-isp.net.</code> But it would probably be
\r
876 safer to put an entry in your name server and call it
\r
877 something like <code>junkbuster.our-isp.net.</code> If
\r
878 running several proxies, you could either use different ports
\r
879 on the same machine, or if you have the opportunity to
\r
880 distribute the load over a few machines you could use
\r
881 different hostname aliases such as <code>
\r
882 banner.junkbuster.our-isp.net</code>, <code>
\r
883 lynx.junkbuster.our-isp.net</code> and <code>
\r
884 oneway.junkbuster.our-isp.net</code> (corresponding to the
\r
885 examples in the previous point). You may want to set up
\r
886 Automatic Proxy Configuration.</li>
\r
889 <a name="document"></a>Prepare a page explaining the
\r
890 Internet Junkbuster to your customers. <a name="does"></a>
\r
891 Here's are some examples from Australia, Germany, Florida,
\r
892 New York/New Jersey/Pennsylvania, North Carolina, Texas,
\r
893 and Utah. <a name="reuse"></a>You are welcome to copy and
\r
894 modify material from Junkbusters according to the GPL. You
\r
895 might want to set up a process to check this page
\r
896 periodically and update it when it changes. (A few links
\r
897 can probably serve as well as lot of copying however.) A
\r
898 typical page would probably specify the following.
\r
901 <li><a name="abstract"></a>A brief explanation stating
\r
902 what the Internet Junkbuster does, with a link to this
\r
905 <li><a name="addresses"></a>The addresses of the proxy or
\r
906 proxies, with their port number(s).</li>
\r
908 <li><a name="options"></a>The options used, and how to
\r
909 view the contents of the blockfile (which you can place
\r
910 on your web pages, preferably in a file called <code>
\r
911 blocklist.html</code> or <code>
\r
912 blocklist.txt</code>).</li>
\r
914 <li><a name="additions"></a>An indication of whether
\r
915 suggestions for the blocklist are considered, and if so,
\r
916 how to submit them: to a particular email address, via
\r
917 web-based form, etc.</li>
\r
919 <li><a name="configuration"></a>Instructions on how to
\r
920 configure a browser. You may want to include details for
\r
921 only the two major browsers and leave the others to a
\r
924 <li><a name="service"></a>Procedures on how to report
\r
925 problems, give feedback etc.</li>
\r
929 <li><a name="beta"></a>Invite a small number of
\r
930 technologically sophisticated customers to beta-test the
\r
933 <li><a name="announce"></a>Announce general availability on
\r
934 your ``News'' page. Tell us if you would like to be included
\r
935 on a list of ISPs offering the Internet Junkbuster.</li>
\r
938 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
939 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
942 <h2><a name="blocking"></a> Blocking</h2>
\r
944 <h3><a name="readymade"></a><img border="0" src="fb.gif" alt=
\r
945 "*" width="14" height="14"> Where can I get an example
\r
946 blockfile that stops most ads?</h3>
\r
948 <p>The sample blockfile we provide blocks almost nothing, and
\r
949 we do not publish blockfiles that stop almost all banner ads.
\r
950 But others have; you can find them by asking Google. You can
\r
951 add any part of the new file to your old one (probably called
\r
952 <code>sblock.ini</code> if you haven't changed the default name
\r
953 in the latest version) or your just replace it completely. You
\r
954 probably don't need to restart the proxy.</p>
\r
956 <p><a name="pub"></a>If you develop an interesting blocklist
\r
957 and publish it on the Web, you might want to include the word
\r
958 ``junkbuster'' in it and use the word ``blocklist'' in the file
\r
959 name given in the URL so that others can find it with the query
\r
960 given in the previous sentence.</p>
\r
962 <h3><a name="zap"></a><img border="0" src="fb.gif" alt="*"
\r
963 width="14" height="14"> If I see an ad I wish I hadn't,
\r
964 how do I stop it?</h3>
\r
966 <p>If your ISP is running the Internet Junkbuster, they should
\r
967 have a policy on whether they accept suggestions from their
\r
968 customers on what to block. Consult their web page.</p>
\r
970 <p><a name="cover"></a>If you are running the Internet
\r
971 Junkbuster yourself, you have complete control over what gets
\r
972 through. Just add a pattern to cover the offending URL to your
\r
973 blockfile. Version 1.3 and later automatically rereads the
\r
974 blockfile when it changes, but if you're running an earlier
\r
975 version you'll have to stop it and restart it.</p>
\r
977 <p><a name="target"></a>To choose a pattern you'll first need
\r
978 to find the URL of the ad you want cover.</p>
\r
980 <p><a name="pinpoint"></a>Some people use the <a href=
\r
981 "ijbman.html#debug">debug</a> <code>1</code> option to display
\r
982 each URL in a window as the request is sent to the server. It's
\r
983 then usually an easy task to pick the offending URL from the
\r
984 list of recent candidates.</p>
\r
986 <p><a name="source"></a>Alternatively, you can use <b class=
\r
987 "eg">View Document Info</b> (or <b class="eg">View Document
\r
988 Source</b> if your browser doesn't have that). The <b class=
\r
989 "eg">Info</b> feature has the advantage of showing you the full
\r
990 URL including the host name, which may not be specified in the
\r
991 source: there you might see something like <code>
\r
992 SRC="/ads/click_here_or_die.gif"</code> indicating only the <i>
\r
993 <dfn>path</dfn></i>. (The host name is assumed to be the same
\r
994 as the one the page came from.)</p>
\r
996 <p><a name="offsite"></a>But ads often come from a different
\r
997 site, in which case you might see something like <code>
\r
998 SRC="grabem.n.trackem.com/Ad/Infinitum/SpaceID=1666"</code> or
\r
999 longer. <a name="warehouse"></a>If the company looks like a
\r
1000 pure ad warehouse (as in the last case), you may want to place
\r
1001 just its domain name in the blockfile, which blocks all URLs
\r
1002 from that site.</p>
\r
1004 <p><a name="wanted"></a>If the ad comes from a server that you
\r
1005 really want some content from, you can include enough of the
\r
1006 path to avoid zapping stuff you might want. In the first
\r
1007 example above, <code>/ads/</code> would seem to be enough. If
\r
1008 you don't include the domain name, the pattern applies to all
\r
1009 sites, so you don't want such patterns to be too general: for
\r
1010 example <code>/ad</code> would block <code>
\r
1011 /admin/salaries/</code> on your company's internal site.</p>
\r
1013 <p><a name="image"></a>To speed the blocking of images, some
\r
1014 UNIX ® users create a shell script called <code>
\r
1015 Image:</code> containing a line such as <code>echo $1 | sed
\r
1016 s/http:..// >> $HOME/lib/blockfile</code> that adds its
\r
1017 argument to the user's blockfile. Once an offending image has
\r
1018 been be found using <b class="eg">View Document Info</b> it's
\r
1019 easy to cut-and-paste the line (or part of it) into a shell
\r
1020 window. The same script can be linked to a file called <code>
\r
1021 Frame:</code> to dealing with framed documents, and <code>
\r
1022 junkbuster:</code> to accept the output of the <a href=
\r
1023 "ijbman.html#debug">debug</a> option.</p>
\r
1025 <p><a name="partial"></a>When compiled without the <i><dfn>
\r
1026 regular expressions</dfn></i> option, the Internet Junkbuster
\r
1027 uses only very simple (and fast) matching methods. The pattern
\r
1028 <code>/banners</code> will not stop <code>
\r
1029 /images/banners/huge.gif</code> getting through: you would have
\r
1030 to include the pattern <code>/images/banners</code> or
\r
1031 something that matches in full from the left. <a name="regex">
\r
1032 </a>So you can get what you want here, the matcher understands
\r
1033 POSIX regular expressions: you can use <code>
\r
1034 /*.*/banners</code> to block and any URL containing <code>
\r
1035 /banners</code> (even in the middle of the path). <a name=
\r
1036 "posix"></a>(In Versions 1.1 through 1.4 they were an option at
\r
1037 compile time; from Version 2.0 they have become the default.)
\r
1038 Regular expressions give you many more features than this, but
\r
1039 if you're not already familiar with them you probably won't
\r
1040 need to know anything beyond the <code>/*.*/</code> idiom. If
\r
1041 you do, a <code>man egrep</code> is probably a good starting
\r
1044 <p><a name="slash"></a>Don't forget the <code>/</code> (slash)
\r
1045 at the beginning of the path. If you leave it out the line will
\r
1046 be interpreted as a domain name, so <code>ad</code> would block
\r
1047 all sites from Andorra (since <code>.ad</code> is the
\r
1048 two-letter country code for that principality).</p>
\r
1050 <p><a name="detail"></a>For a detailed technical description of
\r
1051 how pattern matching is done, see the <a href=
\r
1052 "ijbman.html#o_b">manual.</a></p>
\r
1054 <h3><a name="despite"></a><img border="0" src="fb.gif" alt="*"
\r
1055 width="14" height="14"> How come this ad is still getting
\r
1056 through anyway?</h3>
\r
1058 <p>If the ad had been displayed before you included its URL in
\r
1059 the blockfile, it will probably be held in cache for some time,
\r
1060 so it will be displayed without the need for any request to the
\r
1061 server. Using the <a href="ijbman.html#debug">debug</a> <code>
\r
1062 1</code> option to show each URL as it is fetched is a good way
\r
1063 to see exactly what is happening.</p>
\r
1065 <p><a name="otherwise"></a>If new items seem to be getting
\r
1066 through, check that you are really running the proxy with the
\r
1067 right blockfile in the options. Check the blockfile for
\r
1070 <p><a name="java"></a>Some sites may have different ways of
\r
1071 inserting ads, such as via Java. If you have ideas on how to
\r
1072 block new kinds of junk not currently covered, please tell
\r
1075 <h3><a name="exceptions"></a><img border="0" src="fb.gif" alt=
\r
1076 "*" width="14" height="14"> How do I stop it blocking a
\r
1077 URL that I actually want?</h3>
\r
1079 <p>You can change the patterns so they don't cover it, or use a
\r
1080 simple feature in Version 1.1 and later: a line beginning with
\r
1081 a <code>~</code> character means that a URL blocked by previous
\r
1082 patterns that matches the rest of the line is let through. For
\r
1083 example, the pattern <code>/ad</code> would block <code>
\r
1084 /addasite.html</code> but not if followed by <code>
\r
1085 ~/addasite</code> in the blockfile. Or suppose you want to see
\r
1086 everything that comes from a site you like, even if it looks
\r
1087 like an ad: simply put <code>~aSiteYouLike.com</code> at the
\r
1088 <em>end</em> of the blockfile. (Order is important, because the
\r
1089 last matching line wins.)</p>
\r
1091 <p><a name="agreed"></a>As well as unblocking pages that were
\r
1092 unintentionally blocked, this feature is useful for unblocking
\r
1093 ads from a specific source. This might be because you are
\r
1094 interested in those particular ones, or if you have an explicit
\r
1095 agreement to accept certain ads, such as those from a free
\r
1096 web-based email provider.</p>
\r
1098 <p><a name="blocked"></a>If you want to find out exactly which
\r
1099 pattern in the blockfile a given URL matched, just click on the
\r
1100 words ``Internet Junkbuster'' which are displayed alone on a
\r
1101 page when your browser requests a blocked URL. The proxy
\r
1102 displays a message that pinpoints the pattern for you.</p>
\r
1104 <h3><a name="children"></a><img border="0" src="fb.gif" alt="*"
\r
1105 width="14" height="14"> Can I block sites I don't want my
\r
1106 children to see?</h3>
\r
1108 <p>Yes, but remember that <a name="savvy"></a>children who are
\r
1109 technically sophisticated enough to use the browsers' proxy
\r
1110 configuration options could of course bypass any proxy. This
\r
1111 kind of technology can be used as a gentle barrier to remind or
\r
1112 guide the child, but nobody should expect it to replace the
\r
1113 parent's role in setting and enforcing standards of online
\r
1114 behavior for their children.</p>
\r
1116 <p><a name="recommend"></a>Some ISPs are starting to provide
\r
1117 specialized proxies to protect children. There are two basic
\r
1118 approaches: the ``black list'' and the ``white list'' approach.
\r
1119 <a name="negative"></a>The black list approach allows the child
\r
1120 to go anywhere not explicitly prohibited; the white list
\r
1121 permits visits only to sites explicitly designated as
\r
1124 <p><a name="positive"></a>It's very easy for anyone to compile
\r
1125 a white list from a page of ``recommended kids sites'' and to
\r
1126 configure an Internet Junkbuster to allow access to those sites
\r
1127 only. (If you publish such a list on the web, please tell us
\r
1128 its URL). Assuming your version isn't an old one without regex,
\r
1129 you can place a <code>*</code> (asterisk) as the first line of
\r
1130 the blockfile (which blocks everything), and then list
\r
1131 exceptions after that. Be careful to make the exception
\r
1132 sufficiently broad: for example, using <code>
\r
1133 ~www.uexpress.com/ups/comics/ch/</code> as the exception for
\r
1134 <cite>Calvin and Hobbes</cite> would block some of the graphic
\r
1135 elements on the page; you would probably want a wider exception
\r
1136 such as <code>~www.uexpress.com/ups/</code> to permit them.</p>
\r
1138 <p><a name="trust"></a>Version 2.0 has an experimental feature
\r
1139 to permit only sites mentioned in a nominated <a href=
\r
1140 "ijbman.html#trustfile">trusted site.</a> This allows
\r
1141 organizations to build lists of sites for kids to browse, and
\r
1142 the software automatically restricts access to those on the
\r
1145 <p><a name="scan"></a>Many filtering products actually scan for
\r
1146 keywords in the text of pages they retrieve before presenting
\r
1147 it, but the Internet Junkbuster does not do this. Building a
\r
1148 perfectly reliable black list system is hard, because it's very
\r
1149 difficult to state in advance exactly what is obscene or
\r
1150 unsuitable. For more info see our links page.</p>
\r
1152 <h3><a name="message"></a><img border="0" src="fb.gif" alt="*"
\r
1153 width="14" height="14"> What do I see when a page or
\r
1154 graphic is blocked by the proxy?</h3>
\r
1156 <p>You usually see a broken image icon, but it depends on
\r
1157 several factors beyond the proxy's control. If asked for a URL
\r
1158 matching its blockfile, the proxy returns an HTML page
\r
1159 containing a message identifying itself (currently the two
\r
1160 words ``Internet Junkbuster'') with a status 202 (Accepted)
\r
1161 instead of the usual 200 (OK). (Versions 1.X returned an error
\r
1162 404: Forbidden, which caused strange behavior in some cases.)
\r
1163 Status 202 is described in the HTTP RFC as indicating that the
\r
1164 request has been accepted but not completed, and that it might
\r
1165 complete successfully in the future (in our case, if the
\r
1166 blockfile were changed).</p>
\r
1168 <p><a name="depends"></a>The broken image icon is most common
\r
1169 because the browser is usually expecting a graphic. But if it
\r
1170 was expecting text, or if the page happens to be using certain
\r
1171 HTML extensions such as <code>layer</code> and your browser is
\r
1172 a late model from Microsoft, you may see the words ``Internet
\r
1173 Junkbuster'' displayed as a hot link.</p>
\r
1175 <p><a name="click"></a>Clicking on the link takes you to an
\r
1176 explanation of the pattern in the blockfile that caused the
\r
1177 block, so that you can edit the blockfile and go back and
\r
1178 reload if you really want to see what was blocked. The
\r
1179 explanatory link is generated by the proxy and is automatically
\r
1180 intercepted based on its ending in <code>ij-blocked-url</code>;
\r
1181 even though the site is specified as <code>
\r
1182 http://internet.junkbuster.com</code> no request should
\r
1183 actually made to that site. If one is, it means that the proxy
\r
1184 was been removed after it generated the link.</p>
\r
1186 <p><a name="layer"></a>To summarize: the identifying link to
\r
1187 the blocking explanation is usually turned into a broken image
\r
1188 icon, but it may be displayed on a page alone, or they may may
\r
1189 be restricted to the particular frame, layer or graphic area
\r
1190 specified in the page containing them. The proxy has no way of
\r
1191 knowing the context in which a URL will be used and cannot
\r
1192 control how the blocking message will be rendered.</p>
\r
1194 <h3><a name="broken"></a><img border="0" src="fb.gif" alt="*"
\r
1195 width="14" height="14"> Why not replace blocked banners
\r
1196 with something invisible?</h3>
\r
1198 <p><a name="infringe"></a>Many users have suggested to us that
\r
1199 blocked banners should be replaced by a something like a 1x1
\r
1200 transparent GIF to make the page would look as if there was
\r
1201 nothing ever there. Apart from making it harder to catch
\r
1202 unintended blocking, this might also displease the owners of
\r
1203 the page, who could argue that such a change constitutes a
\r
1204 copyright infringement. We think that merely failing to allow
\r
1205 an included graphic to be accessed would probably not be
\r
1206 considered an infringement: after all this is what happens when
\r
1207 a browser is configured not to load images automatically.
\r
1208 However, we are not lawyers, so anyone in doubt should take
\r
1209 appropriate advice.</p>
\r
1211 <p><a name="done"></a>In a context where the copyright issue is
\r
1212 resolved satisfactorily, a proxy could simply return a status
\r
1213 301 or 302 and specify a replacement URL in a <code>
\r
1214 Location</code> and/or <code>URI</code> header. An alternative
\r
1215 would be to use inline code to return a 1 x 1 clear GIF. We do
\r
1216 not publish sample code for this, and we have no way of
\r
1217 stopping others who have.</p>
\r
1219 <h3><a name="size"></a><img border="0" src="fb.gif" alt="*"
\r
1220 width="14" height="14"> Why not block banners based on
\r
1221 the dimensions of the image?</h3>
\r
1223 <p>Many users have pointed out that most banner ads come in
\r
1224 standard sizes, so why not block all GIFs of those sizes? This
\r
1225 would theoretically be without fetching the object because the
\r
1226 dimensions are usually given in the <code>IMG</code> tag, but
\r
1227 it would require substantial changes in the code, and we doubt
\r
1228 whether it would be much more effective than a good block
\r
1231 <h3><a name="embedded"></a><img border="0" src="fb.gif" alt="*"
\r
1232 width="14" height="14"> What about non-graphic
\r
1233 advertising within the pages I want?</h3>
\r
1235 <p>The Internet Junkbuster deliberately does not provide a way
\r
1236 of automatically editing the contents of a page, to remove
\r
1237 textual advertising or to repair the holes left by blocked
\r
1238 banners. Other packages such as WebFilter do.</p>
\r
1240 <p><a name="base"></a>For the same reason, it has no way of
\r
1241 stopping a new browser window being created, because this is
\r
1242 done through the <code>target</code> attribute in the <code>
\r
1243 <a></code> and <code><base></code> elements, not
\r
1244 through headers. Nor do we plan to add a feature to paralyze
\r
1245 animated GIFs.</p>
\r
1247 <h3><a name="push"></a><img border="0" src="fb.gif" alt="*"
\r
1248 width="14" height="14"> Does it block ads on the
\r
1249 broadcasting ``push'' systems? How about pop-up ads?</h3>
\r
1251 <p>We haven't tried it but we expect it would probably work on
\r
1252 image ads on push channels. See also adchoice.</p>
\r
1254 <p><a name="pop"></a>Disabling Javascript stops some pop-up
\r
1255 ads. One problem is that some advertisers throw open a new
\r
1256 browser window to frame the ad. The ad is easily blocked, but
\r
1257 the empty window remains. You can kill it easily, but this is a
\r
1258 chore. We don't see how to stop them other than editing the
\r
1259 HTML from the parent window, which we don't like to do.</p>
\r
1261 <p><a name="TBTD"></a>The TBTF newsletter warned subscribers to
\r
1262 push information that <a name="LOGTARGET"></a>in IE4, LOGTARGET
\r
1263 allows servers to determine the URLs viewed at their site even
\r
1264 if accessed from cache or through a proxy. If you use this
\r
1265 browser see our instructions on how to disable this.</p>
\r
1267 <p><a name="pushy"></a>If you find you have experience using
\r
1268 the proxy with push, or have any other advice about it, please
\r
1271 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
1272 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
1275 <h2><a name="cookies"></a> Cookies</h2>
\r
1277 <p>For background information on cookies see our page
\r
1278 describing their dangers.</p>
\r
1280 <h3><a name="breakthrough"></a><img border="0" src="fb.gif"
\r
1281 alt="*" width="14" height="14"> Might some cookies still
\r
1282 get through? How can I stop them?</h3>
\r
1284 <p>Yes, you should expect the occasional cookie to make it
\r
1285 through to your browser. We know of at least three ways this
\r
1286 can happen; please tell us if you find any others. One way is
\r
1287 in secure documents, which are explained below.</p>
\r
1289 <p><a name="EQUIV"></a>A few sites set cookies using a line
\r
1290 such as <code><META HTTP-EQUIV="Set-Cookie"
\r
1291 CONTENT="flavor=chocolate"></code> in the <code>HEAD</code>
\r
1292 section of an HTML document. <a name="javascript"></a>Cookies
\r
1294 <!-- IEM: http://cgi.netscape.com/eng/mozilla/Gold/handbook/javascript/ref_a-c.html#cookie_property -->
\r
1295 set and read in JavaScript. To see if this is happening in a
\r
1296 document, view its source, look in the <code>head</code> for a
\r
1297 section tagged <code>script language="JavaScript"</code>. If it
\r
1298 contains a reference to <code>document.cookie</code>, the page
\r
1299 can manipulate your cookie file without sending any cookie
\r
1300 headers. The Internet Junkbuster does not tamper with these
\r
1301 methods. Fortunately they are rarely used at the moment. If a
\r
1302 cookie gets set, it should be stopped by the proxy on its way
\r
1303 back to the server when a page is requested, but it can still
\r
1304 be read in Javascript.</p>
\r
1306 <p><a name="alert"></a>To prevent cookies breaking through,
\r
1307 <strong>always</strong> keep cookie alerts turned on in your
\r
1308 browser, and disable Java and Javascript. Making the files hard
\r
1309 to write may also help.</p>
\r
1311 <h3><a name="method"></a><img border="0" src="fb.gif" alt="*"
\r
1312 width="14" height="14"> Exactly how do cookies get
\r
1313 created and stored anyway?</h3>
\r
1315 <p>When a web site's server sends you a page it also sends
\r
1316 certain ``header information'' which your browser records but
\r
1317 does not display. One of these is a <code>Set-Cookie</code>
\r
1318 header, which specifies the cookie information that the server
\r
1319 wants your browser to record. Similarly, when your browser
\r
1320 requests a page it also sends headers, specifying information
\r
1321 such as the graphics formats it understands. If a cookie has
\r
1322 previously been set by a site that matches the URL it is about
\r
1323 to request, your browser adds a <code>Cookie</code> header
\r
1324 quoting the previous information.</p>
\r
1326 <p><a name="privacy"></a>For more background information on how
\r
1327 cookies can damage your privacy, see our page on cookies. For
\r
1328 highly detailed technical information see the RFC. The Internet
\r
1329 Junkbuster will show you all headers you use the <a href=
\r
1330 "ijbman.html#debug">debug</a> <code>8</code> option, or you can
\r
1331 get a sample from our demonstration page.</p>
\r
1333 <h3><a name="break"></a><img border="0" src="fb.gif" alt="*"
\r
1334 width="14" height="14"> If cookies can't get through,
\r
1335 will some things stop working for me?</h3>
\r
1337 <p>Possibly. Some personalized services including certain
\r
1338 <!-- IEM: http://my.yahoo.com --> chat rooms require cookies.
\r
1339 <a name="registration"></a>Newspapers that require
\r
1340 <!-- IEM: http://www.nytimes.com/subscribe/sub-bin/new_sub.cgi#agree -->
\r
1342 <!-- IEM: http://interactive5.wsj.com/regUser.html -->
\r
1343 subscription will not automatically recognize you if you don't
\r
1344 send them the cookie they assigned you. And there are a very
\r
1345 small number of sites that do strange things with cookies; they
\r
1346 don't work for anyone that blocks cookies by any means. Some
\r
1347 sites such as Microsoft explain that their content is so
\r
1348 wonderfully compelling that they will withhold it from you
\r
1349 unless you submit to their inserting cookies.</p>
\r
1351 <p><a name="hotmail"></a>Many free Web-based email services
\r
1352 require cookies. Hotmail also seems to require allowing both
\r
1353 <code>msn.com</code> and <code>passport.com</code> to set
\r
1356 <p><a name="want"></a>If you want such sites to be given your
\r
1357 cookies, you can use the <a href="ijbman.html#cookiefile">
\r
1358 cookiefile</a> option provided you are running Version 1.2 or
\r
1359 later yourself. Simply include the domain name of those sites
\r
1360 in the <i>cookiefile</i> specified by this option. If it still
\r
1361 doesn't work, the problem may be in other headers.</p>
\r
1363 <p><a name="one"></a>It's possible to let cookies out but not
\r
1364 in, which is enough to keep some sites happy, but not all of
\r
1365 them: one newspaper site seems to go into an endless frenzy if
\r
1366 deprived of fresh cookies. A cookiefile containing a single
\r
1367 line consisting of the two characters <code>>*</code>
\r
1368 (greater-than and star) permits server-bound cookies only. The
\r
1369 <code>*</code> is a <a href="ijbman.html#wildcard">wildcard</a>
\r
1370 that matches all domains.</p>
\r
1372 <p><a name="else"></a>If someone else is running the Internet
\r
1373 Junkbuster for you and has a version that
\r
1374 <!-- IAM: ijbfaq.html#registration --> passes server-bound
\r
1375 cookies through, you can try editing your browser's cookie file
\r
1376 to contain just the ones you want, and restart your browser. <a
\r
1377 name="window"></a>To subscribe to a new service like this after
\r
1378 you have started using the Internet Junkbuster, you can try the
\r
1379 following: tell your browser to stop using the Internet
\r
1380 Junkbuster, fill out and submit your subscription details
\r
1381 (allowing that web site to set a cookie), then reconfigure your
\r
1382 browser to use the Internet Junkbuster again (and stop more
\r
1383 cookies being sent). This also requires the <a href=
\r
1384 "ijbman.html#cookiefile">cookiefile</a> option, and its success
\r
1385 depends on the Web site not wanting to change your cookies at
\r
1386 every session. For this reason it does not work at some major
\r
1387 newspaper sites, for example. <a name="buyers"></a>But you may
\r
1388 prefer to look at whether other sites provide the same or
\r
1389 better services without demanding the opportunity to track your
\r
1390 behavior. The web is a buyer's market where most prices are
\r
1391 zero: very few people pay for content with money, so why should
\r
1392 you pay with your privacy?</p>
\r
1394 <h3><a name="crumble"></a><img border="0" src="fb.gif" alt="*"
\r
1395 width="14" height="14"> Can I control cookies on a
\r
1396 per-site basis?</h3>
\r
1398 <p><a name="discard"></a>Yes, since version 1.2 the Internet
\r
1399 Junkbuster has included advanced cookie management facilities.
\r
1400 Unless you specify otherwise, cookies are discarded
\r
1401 (``crumbled'') by the Internet Junkbuster whether they came
\r
1402 from the server or the browser. In Version 1.2 and later you
\r
1403 can use the <a href="ijbman.html#cookiefile">cookiefile</a>
\r
1404 option to specify when cookies are to be passed through intact.
\r
1405 It uses the same syntax and <a href="ijbman.html#o_b">
\r
1406 matching</a> algorithm as the blockfile.</p>
\r
1408 <p><a name="cook"></a>If the URL matches a pattern in the <i>
\r
1409 <dfn>cookiefile</dfn></i> then cookies are let through in both
\r
1410 the browser's request for the URL and in the server's response.
\r
1411 <a name="directional"></a>One-way permissions can be specified
\r
1412 by starting the line with the <code>></code> or <code>
\r
1413 <</code> character. For example, a cookiefile consisting of
\r
1414 the four lines<br>
\r
1415 <code>org</code><br>
\r
1416 <code>>send-user-cookies.org</code><br>
\r
1417 <code>
\r
1418 <accept-server-cookies.org</code><br>
\r
1419 <code>~block-all-cookies.org</code><br>
\r
1420 allows cookies to and from <code>.org</code> domains only,
\r
1421 with the following exceptions:<br>
\r
1425 <li><a name="fed"></a>Cookies sent from servers in the domain
\r
1426 <code>send-user-cookies.org</code> are blocked on their way
\r
1427 to the client, but cookies sent by the browser to that domain
\r
1428 are still be fed to them.</li>
\r
1430 <li><a name="take"></a>The cookies of <code>
\r
1431 accept-server-cookies.org</code> check in to the proxy and
\r
1432 are passed through to the browser, but when they come back to
\r
1433 the proxy they never check out.</li>
\r
1435 <li><a name="deny"></a>All cookies to and from <code>
\r
1436 block-all-cookies.org</code> are blocked.</li>
\r
1439 <p><a name="paths"></a>If the <b><code>junkbuster</code></b>
\r
1440 was compiled with the regular expressions option they may be
\r
1441 used in paths. Any logging to a ``cookie jar'' is separate and
\r
1444 <p><a name="breadth"></a>It's important to give hosts you want
\r
1445 to be able to set cookies sufficient breadth. For example,
\r
1446 instead of <code>www.yahoo.com</code> use <code>
\r
1447 yahoo.com</code> because the company uses many different hosts
\r
1448 ending in that domain.</p>
\r
1450 <h3><a name="wafers"></a><img border="0" src="fb.gif" alt="*"
\r
1451 width="14" height="14"> Can I make up my own fake cookies
\r
1452 (wafers) to feed to servers?</h3>
\r
1454 <p>Yes, using the <a href="ijbman.html#wafer">wafer</a> option.
\r
1455 We coined the term <i><dfn>wafer</dfn></i> to describe cookies
\r
1456 chosen by a user, not the Web server. Servers may not find
\r
1457 wafers as tasty as the cookies they make themselves. But users
\r
1458 may enjoy controlling servers' diets for various reasons, such
\r
1459 as the following.</p>
\r
1462 <li><a name="retaliate"></a>Users who consider cookies to be
\r
1463 an unwelcome intrusion and a waste of their disk space can
\r
1464 respond in kind. By writing ``signature wafers'' they can
\r
1465 express their feelings about cookies, in a place that the
\r
1466 people in charge of them are most likely to notice.</li>
\r
1469 <a name="notice"></a>Sites running a proxy that logs
\r
1470 cookies to a file (such as the Internet Junkbuster does
\r
1471 with the <a href="ijbman.html#jarfile">jarfile</a> option
\r
1472 on) may want to notify servers that their cookies are being
\r
1473 intercepted, deleted or copied. One possible reason for
\r
1474 doing this is the uncertain copyright status of cookie
\r
1475 strings. Nothing here should be taken as legal advice: we
\r
1476 are simply raising a question for any interested parties to
\r
1477 consider, and make no representation that such measures are
\r
1478 necessary or sufficient. Concerned proxy sites might decide
\r
1479 to send a wafer (named ``NOTICE'' for example) containing
\r
1480 text along the lines of the following.
\r
1483 <p><a name="licenses_on_cookies_refused"></a>TO WHOM IT
\r
1484 MAY CONCERN<i><br>
\r
1486 Do not send me any copyrighted information other than
\r
1487 the document that I am requesting or any of its necessary
\r
1490 In particular do not send me any cookies that are
\r
1491 subject to a claim of copyright by anybody. Take notice
\r
1492 that I refuse to be bound by any license condition
\r
1493 (copyright or otherwise) applying to any cookie.</i></p>
\r
1495 Any company that tries to argue in court that the proxy
\r
1496 site was breaching their copyright in the cookies would be
\r
1497 met with the defense that the proxy site gave that company
\r
1498 the opportunity to protect its copyright by simply not
\r
1499 sending cookies after receiving the notice.
\r
1501 <p><a name="pointer"></a>Cookies can be as long as four
\r
1502 thousand characters, so there's plenty of space for
\r
1503 lawyerly verbosity, but white space, commas, and
\r
1504 semi-colons are <a href="ijbman.html#o_w">prohibited.</a>
\r
1505 Spaces can be turned into underscores. Alternatively, a URL
\r
1506 could be sent as the cookie value, pointing to a document
\r
1507 containing a notice, perhaps with a suggestive value such
\r
1510 http://www.junkbusters.com/ht/en/ijbfaq.html#licenses_on_cookies_refused</code><br>
\r
1512 But including the notice directly would probably be
\r
1513 preferable because the addressee does not have to look it
\r
1516 <p><a name="vanilla"></a>The Internet Junkbuster 2.0.2
\r
1517 currently sends a full notice as a ``vanilla wafer'' if
\r
1518 cookies are being logged to a cookie jar and no other
\r
1519 wafers have been specified. It can be suppressed with the
\r
1520 <a href="ijbman.html#suppress-vanilla-wafer">
\r
1521 suppress-vanilla-wafer</a> option, which might be used in
\r
1522 situations where there is an established understanding
\r
1523 between the proxy and all who serve it.</p>
\r
1527 <p><a name="gimme"></a>Junkbusters provides a CGI script that
\r
1528 lets you see your wafers as they appear to servers.</p>
\r
1530 <p><a name="malfunction"></a>Wafers confuse a few fragile
\r
1531 servers. Hotmail appears to be one of them. If this troubles
\r
1532 you, don't use this option.</p>
\r
1534 <p><a name="regardless"></a>Any wafers specified are sent to
\r
1535 all sites regardless of the cookiefile. <a name="compliant">
\r
1536 </a> They are appended after any genuine cookies, to maintain
\r
1537 compliance with RFC 2109 in the event that a path was specified
\r
1538 for a cookie. The RFC's provisions regarding the <code>$</code>
\r
1539 character (such as the <code>Version</code> attribute) are
\r
1540 transparent to the proxy; it simply quotes what was recited by
\r
1543 <p><a name="personalize"></a>If you want to send wafers only to
\r
1544 specific sites, you could try putting them your browser's
\r
1545 cookie file in a format conforming to the Netscape
\r
1546 specification, and then specify in the proxy's cookiefile that
\r
1547 cookies are to be sent to but not accepted from those sites, so
\r
1548 they can't overwrite the file. This may work with Netscape but
\r
1549 not all other browsers.</p>
\r
1551 <h3><a name="jar"></a><img border="0" src="fb.gif" alt="*"
\r
1552 width="14" height="14"> Why would anyone want to save
\r
1553 their cookies in a ``cookie jar?''</h3>
\r
1555 <p>We provided this capability just in case anyone wants it.
\r
1556 There are a few possible reasons.</p>
\r
1559 <li><a name="pay"></a>It's conceivable that marketing
\r
1560 companies might one day buy history files and cookie jars
\r
1561 from consumers in the same way that they currently pay them
\r
1562 to fill out survey forms. With this information they could
\r
1563 gather psychographic information, see which competitors'
\r
1564 sites the consumer has visited, and discover what advertising
\r
1565 is being targeted at them.</li>
\r
1567 <li><a name="choose"></a>Some consumers might employ
\r
1568 semi-automated means of sorting through their cookie jars,
\r
1569 selecting which ones to place in their cookies file for use
\r
1570 by their browsers. Their decisions could be based on payments
\r
1571 offered, privacy rating systems such as TRUSTe proposes, or
\r
1572 their own opinion of the company. It could be done manually
\r
1573 or with software. There's an Internet Draft on trust
\r
1574 certification of cookies.</li>
\r
1576 <li><a name="share"></a>Users may even start ``sharing''
\r
1577 cookies among themselves, sending back cookies that servers
\r
1578 generated for other visitors. Servers that aren't expecting
\r
1579 this possibility will be misled about their visitors'
\r
1580 identities. Cookies could be shared among users on a single
\r
1581 machine, or across continents via FTP and anonymous
\r
1582 remailers. <a name="disinformation"></a>Privacy activists may
\r
1583 promote cookie disinformation campaigns as a way to defend
\r
1584 the public against abuse. If a significant percentage of
\r
1585 people send disinformative cookies, user tracking via cookies
\r
1586 may become less reliable and less used.</li>
\r
1589 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
1590 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
1593 <h2><a name="anonymity"></a> Anonymity</h2>
\r
1595 <p>For details on how your identity can be revealed while you
\r
1596 surf, see our page on privacy. Once you start using the
\r
1597 Internet Junkbuster you should find that much of the
\r
1598 information previously indicated on that page will no longer be
\r
1599 provided. If the <code>REMOTE HOST</code> indicating your IP
\r
1600 address is too close for comfort, see our suggestions below on
\r
1601 how to conceal your IP address. We also recommend that you
\r
1602 disable JavaScript and Java.</p>
\r
1604 <h3><a name="disclose"></a><img border="0" src="fb.gif" alt="*"
\r
1605 width="14" height="14"> If I use the Internet Junkbuster,
\r
1606 will my anonymity be guaranteed?</h3>
\r
1608 <p>No. Your chances of remaining anonymous are improved, but
\r
1609 unless you are an expert on Internet security it would be
\r
1610 safest to assume that everything you do on the Web can be
\r
1611 attributed to you personally.</p>
\r
1613 <p><a name="happen"></a>The Internet Junkbuster removes various
\r
1614 information about you, but it's still possible that web sites
\r
1615 can find out who you are. Here's one way this can happen.</p>
\r
1617 <p><a name="ftp"></a>A few browsers disclose the user's email
\r
1618 address in certain situations, such as when transferring a file
\r
1619 by FTP. The Internet Junkbuster 2.0.2 does not filter the FTP
\r
1620 stream. If you need this feature, or are concerned about the
\r
1621 mail handler of your browser disclosing your email address, you
\r
1622 might consider products such as NSClean.</p>
\r
1624 <p><a name="binaries"></a>Browsers downloaded as binaries could
\r
1625 use non-standard headers to give out any information they can
\r
1626 have access to: see the manufacturer's license agreement. It's
\r
1627 impossible to anticipate and prevent every breach of privacy
\r
1628 that might occur. The professionally paranoid prefer browsers
\r
1629 available as source code, because anticipating their behavior
\r
1632 <h3><a name="should"></a><img border="0" src="fb.gif" alt="*"
\r
1633 width="14" height="14"> Why should I trust my ISP or
\r
1634 Junkbusters with my browsing data?</h3>
\r
1636 <p>You shouldn't have to trust us, and you certainly don't have
\r
1637 to. We do not run the proxy as a service, where we could
\r
1638 observe your online behavior. We provide source code so that
\r
1639 everyone can see that the proxy isn't doing anything
\r
1642 <p><a name="awful"></a>You are already trusting your ISP not to
\r
1643 look at an awful lot of information on what you do. They
\r
1644 probably post a privacy policy on their site to reassure you.
\r
1645 If they run a proxy for you, using it could actually make it
\r
1646 slightly easier for them to monitor you, but we doubt that any
\r
1647 sane ISP would try this, because if it were discovered
\r
1648 customers would desert them.</p>
\r
1650 <h3><a name="logging"></a><img border="0" src="fb.gif" alt="*"
\r
1651 width="14" height="14"> Can the proxy be used for logging
\r
1652 who looks at what?</h3>
\r
1654 <p>We don't want institutions to use this software as an
\r
1655 instrument of surveillance. We have deliberately not provided
\r
1656 options to add timestamps or records of which IP addresses
\r
1657 accessed which URLs. However, because we publish source code
\r
1658 anyone can modify it to do such things, and there is no way a
\r
1659 remote user can find out if this is happening. Again, you need
\r
1660 to be able to trust the entity providing your proxy service,
\r
1661 but you were probably in that position even before using a
\r
1664 <h3><a name="header"></a><img border="0" src="fb.gif" alt="*"
\r
1665 width="14" height="14"> What private information from
\r
1666 server-bound headers is removed?</h3>
\r
1668 <p>The Internet Junkbuster pounces on the following HTTP
\r
1669 headers in requests to servers, unless instructed otherwise in
\r
1673 <li><a name="from"></a>The <code>FROM</code> header, which a
\r
1674 few browsers use to tell your email address to servers, is
\r
1675 dropped unless the <a href="ijbman.html#from">from</a> option
\r
1678 <li><a name="agent"></a>The <code>USER_AGENT</code> <a name=
\r
1679 "infer"></a>header is changed to indicate that the browser is
\r
1680 currently Mozilla (Netscape) 3.01 Gold with an unremarkable
\r
1681 Macintosh configuration. Misidentification helps resist
\r
1682 certain attacks. If your browser and hardware happen to be
\r
1683 accurately identified, you might want to change the default.
\r
1684 (Earlier versions of the Internet Junkbuster indicated
\r
1685 different details; by altering them periodically we aim to
\r
1686 hinder anyone trying to infer whether our proxy is present.)
\r
1687 <a name="lying"></a>If you don't like the idea of incorrectly
\r
1688 identifying your computer as a Mac, set it accordingly.
\r
1689 <!-- Aside: or read Kundera's Unbearable Lightness of Being, 5:5, ``It is a tragicomic fact..'' (p187?) --></li>
\r
1691 <li><a name="referer"></a>The <code>REFERER</code> header
\r
1692 (which indicates where the URL currently being requested was
\r
1693 found) is dropped. A single static referer to replace all
\r
1694 real referers may be specified using the <a href=
\r
1695 "ijbman.html#referer">referer</a> option. Where no referer is
\r
1696 provided by the browser, none is added; the <a href=
\r
1697 "ijbman.html#add-header">add-header</a> option with arguments
\r
1698 such as <code>-x 'Referer: http://me.me.me'</code> can be
\r
1699 used to send a bogus referer with every request.</li>
\r
1702 <p>In Version 1.4 and later you can use the <a href=
\r
1703 "ijbman.html#o_r">-r @</a> option to selectively disclose
\r
1704 <code>REFERER</code> and <code>USER_AGENT</code> to only those
\r
1705 sites you nominate.</p>
\r
1707 <p><a name="UA"></a>Some browsers send Referer and User-Agent
\r
1708 information under different non-standard headers. The Internet
\r
1709 Junkbuster 2.0.2 stops <code>UA</code> headers, but others may
\r
1710 get through. This information is also available via JavaScript,
\r
1711 so disable it. <a name="indexers"></a>Some search engines
\r
1712 encode the query you typed in the URL that goes to advertisers
\r
1713 to target a banner ad at you, so you will need to block the ad
\r
1714 as well as the referer header, unless you want them (and anyone
\r
1715 they might buy data from) to know everything you ever search
\r
1718 <p><a name="JavaScript"></a>If you have JavaScript enabled (the
\r
1719 default on most browsers) servers can use it to obtain Referer
\r
1720 and User Agent, as well as your plug-ins. We recommend
\r
1721 disabling JavaScript and Java.</p>
\r
1723 <p><a name="response"></a>Currently no HTTP response headers
\r
1724 (browser bound) are removed, not even the <code>
\r
1725 Forwarded:</code> or <code>X-Forwarded-For:</code> headers. Nor
\r
1726 are any added, <a href="ijbman.html#o_y">unless requested.</a>
\r
1727 We are considering a more flexible header management system for
\r
1728 a future version.</p>
\r
1730 <h3><a name="breakage"></a><img border="0" src="fb.gif" alt="*"
\r
1731 width="14" height="14"> Might some things break because
\r
1732 header information is changed?</h3>
\r
1734 <p>Possibly. If used with a browser less advanced than Netscape
\r
1735 3.0 or IE-3, indicating an advanced browser may encourage pages
\r
1736 containing extensions that confuse your browser. If this
\r
1737 becomes a problem upgrade your browser or use the <a href=
\r
1738 "ijbman.html#user-agent">user-agent</a> option to indicate an
\r
1739 older browser. In Version 1.4 and later you can selectively
\r
1740 reveal your real browser to only those sites you nominate.</p>
\r
1742 <p><a name="Russian"></a>Because different browsers use
\r
1743 different encodings of Russian and Czech characters, certain
\r
1744 web servers convert pages on-the-fly according to the User
\r
1745 Agent header. Giving a User Agent with the wrong operating
\r
1746 system or browser manufacturer causes some sites in these
\r
1747 languages to be garbled; Surfers to Eastern European sites
\r
1748 should <a href="ijbman.html#o_r">change it</a> to something
\r
1751 <p><a name="counters"></a>Some page access counters work by
\r
1752 looking at the referer; they may fail or break when
\r
1755 <p><a name="wired"></a>Some sites depend on getting a referer
\r
1756 header, such as <code>uclick.com</code>, which serves comic
\r
1757 strips for many newspaper sites, including <cite>
\r
1758 Doonsbury</cite> for the <cite>Washington Post.</cite> (If you
\r
1759 click on that last link, you can then get to a page containing
\r
1760 the strip via the same URL we've linked to under <cite>
\r
1761 Doonsbury</cite>, but if you click on the <cite>
\r
1762 Doonsbury</cite> link directly, it gives you an error message
\r
1763 suggesting that you use a browser that supports referers.) In
\r
1764 Version 1.4 and later you can use the <a href=
\r
1765 "ijbman.html#o_r">-r @</a> option and place a line like <code>
\r
1766 >uclick.com</code> in your cookiefile. Wired News used to
\r
1767 use referer to decide whether to add a navigation column to the
\r
1768 page, but they have changed that.</p>
\r
1770 <p><a name="Intellicast"></a>The weather maps of Intellicast
\r
1771 have been blocked by their server when no referer or cookie is
\r
1772 provided. You can use the same countermeasure with a line such
\r
1773 as <code>>208.194.150.32</code> (or simply get your weather
\r
1774 information elsewhere).</p>
\r
1776 <p><a name="decide"></a>Some software vendors, including
\r
1777 Download.com and Intuit use <code>USER_AGENT</code> to decide
\r
1778 which versions of their products to display to you. With the
\r
1779 default you get Mac versions.</p>
\r
1781 <p><a name="resort"></a>As a last resort if a site you need
\r
1782 doesn't seem to be working, the proxy configuration of many
\r
1783 browsers allow you to specify <b class="eg">No Proxy For</b>
\r
1784 any hostname you want.</p>
\r
1786 <p><a name="What"></a>We had reports that on some versions of
\r
1787 Netscape the What's New feature did not work with the proxy,
\r
1788 but we think we fixed this in Version 2.0.1.</p>
\r
1790 <h3><a name="misidentify"></a><img border="0" src="fb.gif" alt=
\r
1791 "*" width="14" height="14"> How is misidentifying my
\r
1792 browser good for security and privacy?</h3>
\r
1794 <p>Almost every major release of both leading browsers has
\r
1795 contained bugs that allow malicious servers to compromise your
\r
1796 privacy and security. Known bugs are quickly fixed, but
\r
1797 millions of copies of the affected software remain out there,
\r
1798 and yours is probably one of them. The header that normally
\r
1799 identifies your browser tells such servers exactly which
\r
1800 attacks to use against you. By misidentifying your browser you
\r
1801 reduce the likelihood that they will be able to mount a
\r
1802 successful attack.</p>
\r
1804 <h3><a name="conceal"></a><img border="0" src="fb.gif" alt="*"
\r
1805 width="14" height="14"> Does the Internet Junkbuster
\r
1806 conceal my IP address?</h3>
\r
1808 <p>Web sites get the IP address of any proxy or browser they
\r
1809 serve pages to. If you run the proxy on your own computer the
\r
1810 IP address disclosed is the same as your browser would, unless
\r
1811 you use the <a href="ijbman.html#forwardfile">forwardfile</a>
\r
1812 option is used to chain to another proxy, in which case servers
\r
1813 only get the last IP address in the chain. Chaining slightly
\r
1814 slows browsing of course, but it improves anonymity.</p>
\r
1816 <h3><a name="ident"></a><img border="0" src="fb.gif" alt="*"
\r
1817 width="14" height="14"> Does the Internet Junkbuster
\r
1818 thwart identification by identd?</h3>
\r
1820 <p>We think so, provided you are not the user running the
\r
1821 proxy. If your computer (or your ISP's) is running the <code>
\r
1822 identd</code> demon, servers can ask it for the identity of the
\r
1823 user making the request at time you request a page from them.
\r
1824 But if you're going through a proxy, they will identify the
\r
1825 user name associated with the proxy, not you. A visit to
\r
1826 http://ident.junkbusters.com lets you see what's happening.
\r
1827 This test is (quite rightly) blocked by many firewalls; just
\r
1828 interrupt the transfer if you get an abnormal wait after
\r
1829 clicking. Running other applications may also expose you via
\r
1830 <code>identd</code>; the proxy of course doesn't help then.</p>
\r
1832 <h3><a name="detect"></a><img border="0" src="fb.gif" alt="*"
\r
1833 width="14" height="14"> Can web sites tell that I'm using
\r
1834 the Internet Junkbuster?</h3>
\r
1836 <p>With the default options the proxy doesn't announce itself.
\r
1837 Obvious indications such as Keep-Alive headers are <a href=
\r
1838 "ijbman.html#o_x">deleted,</a> but sites might notice that you
\r
1839 can cancel cookies faster than any human could possibly click
\r
1840 on a mouse. (If you want to provide a plausible explanation for
\r
1841 this, change the User Agent header to a cookie-free or
\r
1842 cookie-crunching browser).</p>
\r
1844 <p><a name="figure"></a>But when certain options are used they
\r
1845 could figure out something's going on, even if they're not
\r
1846 pushing cookies. If you use blocking they can tell from their
\r
1847 logs that the graphics in their pages are not being requested
\r
1848 selectively. The <a href="ijbman.html#add-forwarded-header">
\r
1849 add-forwarded-header</a> option explicitly announces to the
\r
1850 server that a proxy is present, and sending them wafers is of
\r
1851 course a dead giveaway.</p>
\r
1853 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
1854 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
1857 <h2><a name="security"></a> Security</h2>
\r
1859 <h3><a name="encrypt"></a><img border="0" src="fb.gif" alt="*"
\r
1860 width="14" height="14"> What happens with Secure
\r
1861 Documents (SSL, https:)?</h3>
\r
1863 <p>If you enter a ``Secure Document Area,'' cookies and other
\r
1864 header information such as User Agent and Referer are sent
\r
1865 encrypted, so they cannot be filtered. We recommend getting
\r
1866 your browser to alert you when this happens. (On Netscape: <b
\r
1867 class="eg">Options</b>; <b class="eg">Security</b>; <b class=
\r
1868 "eg">General</b>; <b class="eg">Show an alert before entering a
\r
1869 secure document space</b>.) We also recommend adding the line
\r
1870 <code>:443</code> to the blockfile to stop all but sites
\r
1871 specified in an exception after that line from using SSL.</p>
\r
1873 <p><a name="passage"></a>It may be possible to filter encrypted
\r
1874 cookies by combining the blocking proxy with a cryptographic
\r
1875 proxy along the lines of SafePassage, but we have not tried
\r
1878 <h3><a name="ssl"></a><img border="0" src="fb.gif" alt="*"
\r
1879 width="14" height="14"> Will using this as my Security
\r
1880 Proxy compromise security?</h3>
\r
1882 <p>We're not security experts, but we don't think so. The whole
\r
1883 point of SSL is that the contents of messages are
\r
1884 <!-- IEM: http://addy.com/dc/html/what_is_ssl_.html -->
\r
1885 encrypted by the time they leave the browser and the server.
\r
1886 Eavesdroppers (including proxies) can see where your messages
\r
1887 are going whether you are running a proxy or not, but they only
\r
1888 get to see the contents after they have been encrypted.</p>
\r
1890 <h3><a name="restrict"></a><img border="0" src="fb.gif" alt="*"
\r
1891 width="14" height="14"> Can I restrict use of the proxy
\r
1892 to a set of nominated IP addresses?</h3>
\r
1894 <p>Yes, we added an <a href="ijbman.html#aclfile">access
\r
1895 control</a> file in Version 2.0. But before you use it please
\r
1896 consider why you want to do it. If the reason is security, it
\r
1897 probably means you need a firewall.</p>
\r
1899 <p><a name="selective"></a>The <a href=
\r
1900 "ijbman.html#listen-address">listen-address</a> option provides
\r
1901 a way of binding the proxy to a single IP address/port. The
\r
1902 right way to do this is to choose a port inside your firewall,
\r
1903 and deny access to it to those outside the firewall. The
\r
1904 Internet Junkbuster is not a firewall proxy; it should not be
\r
1905 expected to solve security problems.</p>
\r
1907 <p><a name="firewall"></a>For background information on
\r
1908 firewalls, see Yahoo or a magazine article or these well-known
\r
1909 books: <cite>Firewalls and Internet Security: Repelling the
\r
1910 Wily Hacker</cite> by William R. Cheswick and Steven M.
\r
1911 Bellovin or <cite>Building Internet Firewalls</cite> by D.
\r
1912 Brent Chapman and Elizabeth D. Zwicky. There's
\r
1913 <!-- IEM: http://www.wmd.de/wmd/staff/pauck/misc/fwtk_on_linux.html -->
\r
1914 free Linux software available, and a large number of commercial
\r
1915 products and services. For an excellent security overview,
\r
1916 primer, and compendium reference, see <cite>Practical Unix and
\r
1917 Internet Security</cite> by Simson Garfinkel and Gene
\r
1920 <h3><a name="others"></a><img border="0" src="fb.gif" alt="*"
\r
1921 width="14" height="14"> Are there any security risks for
\r
1922 ISPs or others who offer the proxy?</h3>
\r
1924 <p>Yes. As with any service offered over the Internet, hackers
\r
1925 can try to misuse it. A well-run ISP will have professionals
\r
1926 who are experienced at assessing and containing these
\r
1929 <p><a name="outside"></a>It's possible to set up your machine
\r
1930 so that other people can have access to your proxy, but if you
\r
1931 lack expertise in computer security you probably shouldn't have
\r
1932 your computer configured to offer this or any other service to
\r
1933 the outside world.</p>
\r
1935 <p><a name="attack"></a>Hackers can attempt to gain access to
\r
1936 the machine by various attacks, which we have tried to guard
\r
1937 against but don't guarantee to thwart. They can also use the
\r
1938 ``anonymizing'' quality of proxies to try to cover their tracks
\r
1939 while hacking other computers. For this reason we recommend
\r
1940 preventing it being used as an anonymous <code>telnet</code> by
\r
1941 putting the pattern <code>:23</code> in the blockfile (it's
\r
1942 included as standard equipment). (Actually the current
\r
1943 implementation incidentally blocks telnet due to the way
\r
1944 headers are handled, but it's best not to rely on this.) If you
\r
1945 wish to block all ports except the default HTTP port 80, you
\r
1946 can put the lines<br>
\r
1947 <code>:</code><br>
\r
1948 <code>~:80</code><br>
\r
1949 at the beginning of the blockfile, but be aware that some
\r
1950 servers run on non-default ports (e.g. 8080). You might also
\r
1951 want to add the line <code>~:443</code> to allow SSL.</p>
\r
1953 <p><a name="root"></a>On UNIX ® systems it is neither
\r
1954 necessary nor desirable for the proxy to run as root.</p>
\r
1956 <p><a name="patched"></a>Versions 2.0.1 and below may be
\r
1957 vulnerable to remote exploitation of a memory buffer bug; for
\r
1958 security reasons all users are encouraged to upgrade.</p>
\r
1960 <p><a name="holes"></a>If you find any security holes in the
\r
1961 code please tell us, along with any suggestions you may have
\r
1962 for fixing it. However, we do not claim that we will be able to
\r
1965 <p><a name="useful"></a>We distribute this code in the hope
\r
1966 that people will find it useful, but we provide no warranty for
\r
1967 it, and we are not responsible for anyone's use or misuse of
\r
1970 <p><a name="updates"></a>You may also want to check back
\r
1971 periodically for updated versions of the code. We do not
\r
1972 currently maintain a mailing list. To get quick updates,
\r
1973 bookmark our Distribution Information page.</p>
\r
1975 <p align="center"><a href="#top_of_page"><img border="0" src=
\r
1976 "top.gif" alt="--- Back to Top of Page ---" width="250" height=
\r
1979 <p class="sans"><a href="http://ijbswa.sourceforge.net/">
\r
1980 Website</a> <b class="dot">·</b> <a href="ijbman.html">
\r
1981 Manual</a> <b class="dot">·</b> <b>FAQ</b> <b class=
\r
1982 "dot">·</b> <a href="gpl.html">GPL</a></p>
\r
1984 <p class="sans"><small><small><a href="gpl.html#text">
\r
1985 Copyright</a> © 1996-8 <a href=
\r
1986 "http://www.junkbusters.com/">Junkbusters</a> <a href=
\r
1987 "http://www.junkbusters.com/ht/en/legal.html#marks">®</a>
\r
1988 Corporation. <a href="gpl.html#text">Copyright</a> © 2001
\r
1989 <a href="http://sourceforge.net/projects/ijbswa/">Jon
\r
1990 Foster</a>. Copying and distribution permitted under the <a
\r
1991 href="gpl.html">GNU</a> General Public
\r
1992 License.</small></small></p>
\r
1994 <p><small><code><a href=
\r
1995 "http://sourceforge.net/projects/ijbswa/">
\r
1996 http://sourceforge.net/projects/ijbswa/</a></code></small></p>
\r
projects / privoxy.git / blob