From: hal9 Date: Wed, 26 Mar 2003 02:58:06 +0000 (+0000) Subject: Regenerate for 3.0.2 release. X-Git-Tag: v_3_0_2~1 X-Git-Url: http://www.privoxy.org/gitweb/@user-manual@@actions-help-prefix@BLOCK?a=commitdiff_plain;h=4629b053cce6086446ba48cd49b4765c2e98fffe;p=privoxy.git Regenerate for 3.0.2 release. --- diff --git a/doc/text/developer-manual.txt b/doc/text/developer-manual.txt index e0dc191e..6718ceaf 100644 --- a/doc/text/developer-manual.txt +++ b/doc/text/developer-manual.txt @@ -10,7 +10,7 @@ development. It is mandatory (and helpful!) reading for anyone who wants to join the team. Please note that this document is constantly evolving. This copy represents the -state at the release of version 3.0.1. You can find the latest version of the +state at the release of version 3.0.2. You can find the latest version of the this manual at http://www.privoxy.org/developer-manual/. Please see the Contact section on how to contact the developers. @@ -469,7 +469,7 @@ entities are listed below. See any of the main docs for examples. * Commonly used "internal entities": - p-version: the Privoxy version string, e.g. "3.0.1". + p-version: the Privoxy version string, e.g. "3.0.2". p-status: the project status, either "alpha", "beta", or "stable". p-not-stable: use to conditionally include text in "not stable" releases (e.g. "beta"). @@ -1986,13 +1986,13 @@ First, make sure that you have freshly exported the right version into an empty directory. (See "Building and releasing packages" above). Then add a log entry to debian/changelog, if it is not already there, for example by running: - debchange -v 3.0.1-stable-1 "New upstream version" + debchange -v 3.0.2-stable-1 "New upstream version" Then, run: dpkg-buildpackage -rfakeroot -us -uc -b -This will create ../privoxy_3.0.1-stable-1_i386.deb which can be uploaded. To +This will create ../privoxy_3.0.2-stable-1_i386.deb which can be uploaded. To upload the package to Sourceforge, simply issue make debian-upload @@ -2118,7 +2118,7 @@ Once this done go to http://sourceforge.net/project/admin/editpackages.php? group_id=11118, making sure you are logged in. Find your target platform in the second column, and click Add Release. You will then need to create a new release for your package, using the format of $VERSION ($CODE_STATUS), e.g. -3.0.1 (beta). +3.0.2 (beta). Now just follow the prompts. Be sure to add any appropriate Release notes. You should see your freshly uploaded packages in "Step 2. Add Files To This @@ -2255,7 +2255,7 @@ group_id=11118. 9. Privoxy Copyright, License and History -Copyright © 2001, 2002 by Privoxy Developers +Copyright © 2001 - 2003 by Privoxy Developers Some source code is based on code Copyright © 1997 by Anonymous Coders and Junkbusters, Inc. and licensed under the GNU General Public License. @@ -2309,7 +2309,7 @@ Then, some developers picked up the thread, and started turning the software inside out, upside down, and then reassembled it, adding many new features along the way. -The result of this is Privoxy, whose first stable release, 3.0, was released +The result of this is Privoxy, whose first stable version, 3.0, was released August, 2002. ------------------------------------------------------------------------------- diff --git a/doc/text/faq.txt b/doc/text/faq.txt index 838132f4..c741395c 100644 --- a/doc/text/faq.txt +++ b/doc/text/faq.txt @@ -2,7 +2,7 @@ Privoxy Frequently Asked Questions Copyright © 2001, 2002 by Privoxy Developers -$Id: faq.sgml,v 1.61.2.27 2002/12/01 06:31:58 hal9 Exp $ +$Id: faq.sgml,v 1.61.2.28 2003/03/18 19:37:21 oes Exp $ This FAQ gives quick answers to frequently asked questions about Privoxy. It can't and doesn't replace the User Manual. @@ -17,7 +17,7 @@ networks. Privoxy is based on Internet Junkbuster (tm). Please note that this document is constantly evolving. This copy represents the -state at the release of version 0.0.0. You can find the latest version of the +state at the release of version 3.0.2. You can find the latest version of the document at http://www.privoxy.org/faq/. Please see the Contact section if you want to contact the developers. @@ -62,8 +62,8 @@ Table of Contents 3.5. How are actions files configured? What is the easiest way to do this? 3.6. There are several different "actions" files. What are the differences? 3.7. How can I make my Yahoo/Hotmail/GMX account work? - 3.8. What's the difference between the "Cautious", "Medium" and "Radical" - defaults? + 3.8. What's the difference between the "Cautious", "Medium" and + "Adventuresome" defaults? 3.9. Why can I change the configuration with a browser? Does that not raise security issues? 3.10. What is the default.filter file? What is a "filter"? @@ -171,7 +171,7 @@ Then, some developers picked up the thread, and started turning the software inside out, upside down, and then reassembled it, adding many new features along the way. -The result of this is Privoxy, whose first stable release, 3.0, was released +The result of this is Privoxy, whose first stable version, 3.0, was released August, 2002. ------------------------------------------------------------------------------- @@ -192,7 +192,7 @@ project itself, and they, in fact, still share our ideals and goals. The developers also believed that there are so many changes from the original code, that it was time to make a clean break from the past and make a name in -their own right, especially now with the pending release of version 3.0. +their own right. ------------------------------------------------------------------------------- @@ -561,7 +561,7 @@ yahoo might look like: ------------------------------------------------------------------------------- -3.8. What's the difference between the "Cautious", "Medium" and "Radical" +3.8. What's the difference between the "Cautious", "Medium" and "Adventuresome" defaults? Configuring Privoxy is not entirely trivial. To help you get started, we @@ -574,9 +574,9 @@ Where the defaults are likely to break some sites, exceptions for known popular settings are, the more exceptions you will have to make later. See the User Manual for a more deatiled discussion. -It should be noted that the "Radical" profile (formerly known as the "Advanced" -profile) is not only more aggressive, but also includes fun and, extreme usage -of most of Privoxy's features. Use at your own risk! +It should be noted that the "Adventuresome" profile (formerly known as the +"Advanced" profile) is not only more aggressive, but also includes fun and, +extreme usage of most of Privoxy's features. Use at your own risk! ------------------------------------------------------------------------------- @@ -842,7 +842,7 @@ built-in editor for the actions files. Note that the built-in URLs from earlier versions of Junkbuster / Privoxy, http://example.com/show-proxy-args and http://i.j.b/, are no longer supported. If you still use such an old version, you should really consider upgrading to -0.0.0. +3.0.2. ------------------------------------------------------------------------------- @@ -1116,8 +1116,8 @@ manipulating my browsing? We're not. The text substitutions that you are seeing are disabled in the default configuration as shipped. You have either manually activated the "fun" filter which is clearly labeled "Text replacements for subversive browsing fun! -" or you have implicitly activated it by choosing the "Radical" profile in the -web-based editor (formerly known as the Advanced profile). +" or you have implicitly activated it by choosing the "Adventuresome" profile +in the web-based editor (formerly known as the Advanced profile). ------------------------------------------------------------------------------- @@ -1363,7 +1363,7 @@ group_id=11118. 7. Privoxy Copyright, License and History -Copyright © 2001, 2002 by Privoxy Developers +Copyright © 2001 - 2003 by Privoxy Developers Some source code is based on code Copyright © 1997 by Anonymous Coders and Junkbusters, Inc. and licensed under the GNU General Public License. @@ -1420,6 +1420,6 @@ Then, some developers picked up the thread, and started turning the software inside out, upside down, and then reassembled it, adding many new features along the way. -The result of this is Privoxy, whose first stable release, 3.0, was released +The result of this is Privoxy, whose first stable version, 3.0, was released August, 2002. diff --git a/doc/text/user-manual.txt b/doc/text/user-manual.txt index 424f53c7..e996ae26 100644 --- a/doc/text/user-manual.txt +++ b/doc/text/user-manual.txt @@ -1,8 +1,8 @@ -Privoxy 3.0.1 User Manual +Privoxy 3.0.2 User Manual -Copyright © 2001, 2002 by Privoxy Developers +Copyright © 2001 - 2003 by Privoxy Developers -$Id: user-manual.sgml,v 1.123.2.27 2003/03/18 19:37:14 oes Exp $ +$Id: user-manual.sgml,v 1.123.2.31 2003/03/26 02:03:43 oes Exp $ The User Manual gives users information on how to install, configure and use Privoxy. @@ -149,6 +149,7 @@ Table of Contents 9. The Filter File 9.1. Filter File Tutorial + 9.2. The Pre-defined Filters 10. Templates 11. Contacting the Developers, Bug Reporting and Feature Requests @@ -179,7 +180,7 @@ Table of Contents 1. Introduction This documentation is included with the current stable version of Privoxy, -v.3.0.1. +v.3.0.2. ------------------------------------------------------------------------------- @@ -250,7 +251,7 @@ How to install the binary packages depends on your operating system: 2.1.1. Red Hat, SuSE and Conectiva RPMs -RPMs can be installed with rpm -Uvh privoxy-3.0.1-1.rpm, and will use /etc/ +RPMs can be installed with rpm -Uvh privoxy-3.0.2-1.rpm, and will use /etc/ privoxy for the location of configuration files. Note that on Red Hat, Privoxy will not be automatically started on system boot. @@ -258,7 +259,7 @@ You will need to enable that using chkconfig, ntsysv, or similar methods. Note that SuSE will automatically start Privoxy in the boot process. If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm ---rebuild privoxy-3.0.1-1.src.rpm. This will use your locally installed +--rebuild privoxy-3.0.2-1.src.rpm. This will use your locally installed libraries and RPM version. Also note that if you have a Junkbuster RPM installed on your system, you need @@ -269,7 +270,7 @@ remove Junkbuster automatically, before installing Privoxy. 2.1.2. Debian -DEBs can be installed with dpkg -i privoxy_3.0.1-1.deb, and will use /etc/ +DEBs can be installed with dpkg -i privoxy_3.0.2-1.deb, and will use /etc/ privoxy for the location of configuration files. ------------------------------------------------------------------------------- @@ -343,7 +344,7 @@ latest changes from the Portage tree. With emerge privoxy you install the latest version. Configuration files are in /etc/privoxy, the documentation is in /usr/share/doc -/privoxy-3.0.1 and the Log directory is in /var/log/privoxy. +/privoxy-3.0.2 and the Log directory is in /var/log/privoxy. ------------------------------------------------------------------------------- @@ -362,8 +363,8 @@ compiler like gcc are required. When building from a source tarball (either release version or nightly CVS tarball), first unpack the source: - tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz] - cd privoxy-3.0.1 + tar xzvf privoxy-3.0.2-src* [.tgz or .tar.gz] + cd privoxy-3.0.2 For retrieving the current CVS sources, you'll need CVS installed. Note that sources from CVS are development quality, and may not be stable, or well @@ -1286,15 +1287,15 @@ Notes: Unix, in local filesystem: - user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/ + user-manual file:///usr/share/doc/privoxy-3.0.2/user-manual/ Windows, in local filesystem, must use forward slash notation: - user-manual file:/c:/some-dir/privoxy-3.0.1/user-manual/ + user-manual file:/c:/some-dir/privoxy-3.0.2/user-manual/ Windows, UNC notation (with forward slashes): - user-manual file://///some-server/some-path/privoxy-3.0.1/user-manual/ + user-manual file://///some-server/some-path/privoxy-3.0.2/user-manual/ Any platform, on local webserver (called "local-webserver"): @@ -2598,8 +2599,9 @@ Type: Parameter: The name of a filter, as defined in the filter file (typically - default.filter, set by the filterfile option in the config file). Filtering - can be completely disabled without the use of parameters. + default.filter, set by the filterfile option in the config file). When used + in its negative form, and without parameters, filtering is completely + disabled. Notes: @@ -2607,15 +2609,15 @@ Notes: in the distribution filter file that you can use. See the examples below for a list. - This is potentially a very powerful feature! But "rolling your own" filters - requires a knowledge of regular expressions and HTML. - Filtering requires buffering the page content, which may appear to slow down page rendering since nothing is displayed until all content has passed the filters. (It does not really take longer, but seems that way since the page is not incrementally displayed.) This effect will be more noticeable on slower connections. + This is very powerful feature, but "rolling your own" filters requires a + knowledge of regular expressions and HTML. + The amount of data that can be filtered is limited to the buffer-limit option in the main config file. The default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered data, and all pending data, is passed @@ -2638,7 +2640,12 @@ Notes: Feedback with suggestions for new or improved filters is particularly welcome! -Example usage (with filters from the distribution default.filter file): + The below list has only the names and a one-line description of each + predefined filter. There are more verbose explanations of what these + filters do in the filter file chapter. + +Example usage (with filters from the distribution default.filter file). See the + Predefined Filters section for more explanation on each: +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse @@ -3959,6 +3966,191 @@ You get the idea? ------------------------------------------------------------------------------- +9.2. The Pre-defined Filters + +The distribution default.filter file contains a selection of pre-defined +filters for your convenience: + +js-annoyances + + The purpose of this filter is to get rid of particularly annoying + JavaScript abuse. To that end, it + + + replaces JavaScript references to the browser's referrer information + with the string "Not Your Business!". This compliments the + hide-referrer action on the content level. + + + removes the bindings to the DOM's unload event which we feel has no + right to exist and is responsible for most "exit consoles", i.e. nasty + windows that pop up when you close another one. + + + removes code that causes new windows to be opened with undesired + properties, such as being full-screen, non-resizable, without location, + status or menu bar etc. + +js-events + + This is a very radical measure. It removes virtually all JavaScript event + bindings, which means that scripts can not react to user actions such as + mouse movements or clicks, window resizing etc, anymore. + + We strongly discourage using this filter as a default since it breaks many + legitimate scripts. It is meant for use only on extra-nasty sites (should + you really need to go there). + +html-annoyances + + This filter will undo many common instances of HTML based abuse. + + The BLINK and MARQUEE tags are neutralized (yeah baby!), and browser + windows will be created as resizable (as of course they should be!), and + will have location, scroll and menu bars -- even if specified otherwise. + +content-cookies + + Most cookies are set in the HTTP dialogue, where they can be intercepted by + the crunch-incoming-cookies and crunch-outgoing-cookies actions. But web + sites increasingly make use of HTML meta tags and JavaScript to sneak + cookies to the browser on the content level. + + This filter disables HTML and JavaScript code that reads or sets cookies. + Use it wherever you would also use the cookie crunch actions. + +refresh tags + + Disable any refresh tags if the interval is greater than nine seconds (so + that redirections done via refresh tags are not destroyed). This is useful + for dial-on-demand setups, or for those who find this HTML feature + annoying. + +unsolicited-popups + + This filter attempts to prevent only "unsolicited" pop-up windows from + opening, yet still allow pop-up windows that the user has explicitly chosen + to open. It was added in version 3.0.1, as an improvement over earlier such + filters. + + Technical note: The filter works by redefining the window.open JavaScript + function to a dummy function during the loading and rendering phase of each + HTML page access, and restoring the function afterwards. + +all-popups + + Attempt to prevent all pop-up windows from opening. Note this should be + used with more discretion than the above, since it is more likely to break + some sites that require pop-ups for normal usage. Use with caution. + +img-reorder + + This is a helper filter that has no value if used alone. It makes the + banners-by-size and banners-by-link (see below) filters more effective and + should be enabled together with them. + +banners-by-size + + This filter removes image tags purely based on what size they are. + Fortunately for us, many ads and banner images tend to conform to certain + standardized sizes, which makes this filter quite effective for ad + stripping purposes. + + Occasionally this filter will cause false positives on images that are not + ads, but just happen to be of one of the standard banner sizes. + +banners-by-link + + This is an experimental filter that attempts to kill any banners if their + URLs seem to point to known or suspected click trackers. It is currently + not of much value and is not recommended for use by default. + +webbugs + + Webbugs are small, invisible images (technically 1X1 GIF images), that are + used to track users across websites, and collect information on them. As an + HTML page is loaded by the browser, an embedded image tag causes the + browser to contact a third-party site, disclosing the tracking information + through the requested URL and/or cookies for that third-party domain, + without the use ever becoming aware of the interaction with the third-party + site. HTML-ized spam also uses a similar technique to verify email + addresses. + + This filter removes the HTML code that loads such "webbugs". + +tiny-textforms + + A rather special-purpose filter that can be used to enlarge textareas + (those multi-line text boxes in web forms) and turn off hard word wrap in + them. It was written for the sourceforge.net tracker system where such + boxes are a nuisance, but it can be handy on other sites, too. + + It is not recommended to use this filter as a default. + +jumping-windows + + Many consider windows that move, or resize themselves to be abusive. This + filter neutralizes the related JavaScript code. Note that some sites might + not display or behave as intended when using this filter. + +frameset-borders + + Some web designers seem to assume that everyone in the world will view + their web sites using the same browser brand and version, screen resolution + etc, because only that assumption could explain why they'd use static frame + sizes, yet prevent their frames from being resized by the user, should they + be too small to show their whole content. + + This filter removes the related HTML code. It should only be applied to + sites which need it. + +demoronizer + + Many Microsoft products that generate HTML use non-standard extensions + (read: violations) of the ISO 8859-1 aka Latin-1 character set. This causes + those HTML documents to display with errors on standard-compliant + platforms. + + This filter translates the MS-only characters into Latin-1 equivalents. It + is safe for general use, and recommended for non-MS platforms. + +shockwave-flash + + A filter for shockwave haters. As the name suggests, this filter strips + code out of web pages that is used to embed shockwave flash objects. + +quicktime-kioskmode + + Change HTML code that embeds Quicktime objects so that kioskmode, which + prevents saving, is disabled. + +fun + + Text replacements for subversive browsing fun. Make fun of your favorite + Monopolist or play buzzword bingo. + +crude-parental + + A demonstration-only filter that shows how Privoxy can be used to delete + web content on a keyword basis. + +ie-exploits + + A collection of text replacements to disable malicious HTML and JavaScript + code that exploits known security holes in Internet Explorer. + + Presently, it only protects against Nimda and a cross-site scripting bug, + and would need active maintenance to provide more substantial protection. + +site-specifics + + Some web sites have very specific problems, the cure for which doesn't + apply anywhere else, or could even cause damage on other sites. + + This is a collection of such site-specific cures which should only be + applied to the sites they were intended for, which is what the supplied + default.action file does. Users shouldn't need to change anything regarding + this filter. + +------------------------------------------------------------------------------- + 10. Templates All Privoxy built-in pages, i.e. error pages such as the "404 - No Such Domain" @@ -4081,7 +4273,7 @@ group_id=11118. 12. Privoxy Copyright, License and History -Copyright © 2001, 2002 by Privoxy Developers +Copyright © 2001 - 2003 by Privoxy Developers Some source code is based on code Copyright © 1997 by Anonymous Coders and Junkbusters, Inc. and licensed under the GNU General Public License. @@ -4135,42 +4327,43 @@ Then, some developers picked up the thread, and started turning the software inside out, upside down, and then reassembled it, adding many new features along the way. -The result of this is Privoxy, whose first stable release, 3.0, was released +The result of this is Privoxy, whose first stable version, 3.0, was released August, 2002. ------------------------------------------------------------------------------- 12.3. Authors -Current Project Developers: +Current Developement Team: + Hal Burgiss (docs) Jon Foster Andreas Oesterhelt - Stefan Waldherr + David Schmidt (OS/2, Mac OSX ports) + - Thomas Steudten - Rodney Stromlund -Current Project Contributors: +Current and Former Project Contributors: Johny Agotnes Rodrigo Barbosa (RPM specfiles) Moritz Barsnick - Hal Burgiss (docs) Mattes Dolak Karsten Hopp (Red Hat) Alexander Lazic Daniel Leite Gábor Lipták - Andrew Lock (Win32) + Adam Lock (Win32) Guy Laroche Haroon Rafique Roland Rosenfeld (Debian) Georg Sauthoff (Gentoo) - David Schmidt (OS/2, Mac OSX ports) + Thomas Steudten Joerg Strohmayer (Amiga) + Rodney Stromlund Sviatoslav Sviridov Sarantis Paskalis + Stefan Waldherr Based in part on code originally developed by: diff --git a/doc/webserver/developer-manual/copyright.html b/doc/webserver/developer-manual/copyright.html index d1cd3870..5d4bc738 100644 --- a/doc/webserver/developer-manual/copyright.html +++ b/doc/webserver/developer-manual/copyright.html @@ -77,7 +77,7 @@ NAME="COPYRIGHT" >9. Privoxy Copyright, License and History

Copyright © 2001, 2002 by Privoxy Developers Copyright © 2001 - 2003 by Privoxy Developers

which can be uploaded. To upload the package to Sourceforge, simply issue @@ -1769,7 +1769,7 @@ CLASS="LITERAL" CLASS="emphasis" >3.0.1 +>3.0.2 (beta). diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html index 6314175d..c9c55ab4 100644 --- a/doc/webserver/faq/configuration.html +++ b/doc/webserver/faq/configuration.html @@ -388,7 +388,7 @@ CLASS="QUOTE" >"Medium" and "Radical""Adventuresome" defaults?

Configuring

It should be noted that the "Radical""Adventuresome" profile (formerly known as the 7. Privoxy Copyright, License and History

Copyright © 2001, 2002 by Privoxy Developers Copyright © 2001 - 2003 by Privoxy Developers