X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=68de45b58fe04fa5e8b28795bcba13777e51875a;hb=cc77d4eec4405c7a88977ee93f0d317827aba968;hp=1548d0713ea29b9b85665d2f6d5ca69ef816d564;hpb=ea3ca56adb3901e74bb9e93f00299b5adbc471f2;p=privoxy.git diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index 1548d071..68de45b5 100644 --- a/doc/webserver/man-page/privoxy-man-page.html +++ b/doc/webserver/man-page/privoxy-man-page.html @@ -1,8 +1,9 @@ -Manpage of PRIVOXY + +Man page of PRIVOXY

PRIVOXY

-Section: (1)
Updated: 24 April 2002
Index +Section: (1)
Updated: 19 January 2008
Index
  @@ -13,10 +14,7 @@ privoxy - Privacy Enhancing Proxy

SYNOPSIS

-privoxy [--help] [--version] [--no-daemon] [--pidfile pidfile] [--user user[.group]] [configfile] (UNIX) -

-

-privoxy.exe [configfile] (Windows) +privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [--pre-chroot-nslookup hostname ] [configfile ]

 

OPTIONS

@@ -36,7 +34,7 @@ leader, don't detach from controlling tty, and do all logging there.
--pidfile pidfile
On startup, write the process ID to pidfile. Delete the pidfile on exit. -Failiure to create or delete the pidfile +Failure to create or delete the pidfile is non-fatal. If no --pidfile option is given, no PID file will be used.
--user user[.group]
After (optionally) writing the PID file, assume the user ID of @@ -45,13 +43,23 @@ After (optionally) writing the PID file, assume the user ID of group was not given, the default group of user. Exit if the privileges are not sufficient to do so. +
--chroot
+Before changing to the user ID given in the --user option, chroot to +that user's home directory, i.e. make the kernel pretend to the +Privoxy process that the directory tree starts +there. If set up carefully, this can limit the impact of possible +vulnerabilities in Privoxy to the files contained in +that hierarchy. +
--pre-chroot-nslookup hostname
+Initialize the resolver library using hostname +before chroot'ing. On some systems this reduces the number of files +that must be copied into the chroot tree.

If the configfile is not specified on the command line, Privoxy will look for a file named -config in the current directory (except on Win32 where -it will try config.txt). If no +config in the current directory . If no configfile is found, Privoxy will fail to start.   @@ -59,38 +67,51 @@ fail to start.

-Privoxy is a web proxy with advanced filtering -capabilities for protecting privacy, filtering web page content, managing -cookies, controlling access, and removing ads, banners, pop-ups and other -obnoxious Internet junk. Privoxy has a very -flexible configuration and can be customized to suit individual needs and -tastes. Privoxy has application for both -stand-alone systems and multi-user networks. +Privoxy is a non-caching +web proxy +with advanced filtering capabilities for enhancing privacy, +modifying web page data, managing HTTP +cookies, +controlling access, and removing ads, banners, pop-ups and other obnoxious +Internet junk. Privoxy has a flexible configuration and can be +customized to suit individual needs and tastes. Privoxy has application for +both stand-alone systems and multi-user networks.

-Privoxy is based on Internet -Junkbuster (tm). +Privoxy is based on Internet Junkbuster (tm).  

INSTALLATION AND USAGE

-Browsers must be individually configured to use Privoxy as -a HTTP proxy. The default setting is for localhost, on port 8118 -(configurable in the main config file). To set the HTTP proxy in Netscape -and Mozilla, go through: Edit; +Browsers can either be individually configured to use +Privoxy as a HTTP proxy (recommended), +or Privoxy can be combined with a packet +filter to build an intercepting proxy +(see config). The default setting is for +localhost, on port 8118 (configurable in the main config file). To set the +HTTP proxy in Netscape and Mozilla, go through: Edit; Preferences; Advanced; Proxies; Manual Proxy Configuration; View.

+For Firefox, go through: Tools; +Options; General; +Connection Settings; +Manual Proxy Configuration. +

+ For Internet Explorer, go through: Tools; Internet Properties; Connections; LAN Settings.

The Secure (SSL) Proxy should also be set to the same values, otherwise -https: URLs will not be proxied. +https: URLs will not be proxied. Note: Privoxy can only +proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols. +HTTPS presents some limitations, and not all features will work with HTTPS +connections.

For other browsers, check the documentation. @@ -101,146 +122,140 @@ For other browsers, check the documentation. Privoxy can be configured with the various configuration files. The default configuration files are: config, -default.action, and -default.filter. These are well commented. On Unix and -Unix-like systems, these are located in /etc/privoxy/ by -default. On Windows, OS/2 and AmigaOS, these files are in the same directory -as the Privoxy executable. +default.filter, and +default.action. user.action should +be used for locally defined exceptions to the default rules of +default.action, and user.filter for +locally defined filters. These are well commented. On Unix +and Unix-like systems, these are located in +/etc/privoxy/ by default.

-The name and number of configuration files has changed from previous -versions, and is subject to change as development progresses. In fact, the -configuration itself is changed and much more sophisticated. See the -user-manual for a -brief explanation of all configuration options. +Privoxy uses the concept of actions +in order to manipulate the data stream between the browser and remote sites. +There are various actions available with specific functions for such things +as blocking web sites, managing cookies, etc. These actions can be invoked +individually or combined, and used against individual URLs, or groups of URLs +that can be defined using wildcards and regular expressions. The result is +that the user has greatly enhanced control and freedom.

The actions list (ad blocks, etc) can also be configured with your -web browser at http://ijbswa.sourceforge.net/config. +web browser at http://config.privoxy.org/ +(assuming the configuration allows it). Privoxy's configuration parameters can also be viewed at the same page. In addition, Privoxy can be toggled on/off. -This is an internal page. +This is an internal page, and does not require Internet access. +

+ +See the User Manual for a detailed +explanation of installation, general usage, all configuration options, new +features and notes on upgrading.  

SAMPLE CONFIGURATION

-A brief example of what a default.action configuration -might look like: +A brief example of what a simple default.action +configuration might look like:

-
  # Define a few useful custom aliases for later use
  {{alias}}
 
- # Useful aliases
- +prevent-cookies = +prevent-setting-cookies +prevent-reading-cookies
- -prevent-cookies = -prevent-setting-cookies -prevent-reading-cookies
- +imageblock      = +block +handle-as-image
+ # Useful aliases that combine more than one action
+ +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
+ -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
+ +block-as-image = +block +handle-as-image
 
  # Fragile sites should have the minimum changes
  fragile     = -block -deanimate-gifs -fast-redirects -filter \
                -hide-referer -prevent-cookies -kill-popups
 
- # Shops should be allowed to set persistent cookies
- shop        = -filter -prevent-cookies -prevent-keeping-cookies
-
- # Your favourite blend of filters:
- #
- myfilters   = +filter{html-annoyances} +filter{js-annoyances} \
-               +filter{popups} +filter{webbugs} +filter{banners-by-size} 
-
- ## Default Policies (actions) ############################
- { \
- -add-header \
- -block \
- +deanimate-gifs{last} \
- -downgrade-http-version \
- -fast-redirects \
- +filter{html-annoyances} \
- +filter{js-annoyances} \
- +filter{content-cookies} \
- -filter{popups} \
- +filter{webbugs} \
- +filter{refresh-tags} \
- -filter{fun} \
- +filter{nimda} \
- +filter{banners-by-size} \
- -filter{shockwave-flash} \
- -filter{crude-prental} \
- +hide-forwarded-for-headers \
- +hide-from-header{block} \
- +hide-referrer{forge} \
- -hide-user-agent \
- -handle-as-image \
- +set-image-blocker{pattern} \
- -limit-connect \
- +prevent-compression \
- +session-cookies-only \
- +prevent-reading-cookies \
- +prevent-setting-cookies \
- -kill-popups \
- -send-vanilla-wafer \
- -send-wafer \
- }
- /
- # Now set exceptions to the above defined policies #######
-
- # Sites where we want persistant cookies
- {-prevent-reading-cookies -prevent-setting-cookies}
-  .redhat.com
-  .sun.com
-  .yahoo.com
-  .msdn.microsoft.com
+ ## Turn some actions on ################################
+ ## NOTE: Actions are off by default, unless explictily turned on 
+ ## otherwise with the '+' operator.
+
+{ \
++deanimate-gifs{last} \
++filter{refresh-tags} \
++filter{img-reorder} \
++filter{banners-by-size} \
++filter{webbugs} \
++filter{jumping-windows} \
++filter{ie-exploits} \
++hide-forwarded-for-headers \
++hide-from-header{block} \
++hide-referrer{conditional-block} \
++session-cookies-only \
++set-image-blocker{pattern} \
+}
+/ # '/' Match *all* URL patterns
 
- # This site requires cookies AND 'fast-redirects' on
- {-prevent-reading-cookies -prevent-setting-cookies -fast-redirects}
-  .nytimes.com
-
- # Add custom headers, and turn off filtering of page source
- {+add-header{X-Privacy: Yes please} #-add-header{*} \
-  +add-header{X-User-Tracking: No thanks!} -filter}
-  privacy.net
-
- # Block, and treat these URLs as 'images'.
- {+imageblock}
- ar.atwola.com 
- .ad.doubleclick.net
- .a.yimg.com/(?:(?!/i/).)*$
- .a[0-9].yimg.com/(?:(?!/i/).)*$
- bs*.gsanet.com
- bs*.einets.com
- .qkimg.net
- ad.*.doubleclick.net
-
- # Block any URLs that match these patterns
- {+block}
- ad*.
- .*ads.
- banner?.
- count*.
- /(?:.*/)?(ads(erver?|tream)?|.*?ads|adv(ert(s|enties|is(ing|e?ments)?)?)?|(ad)?[-_]?banner(s|ads?|farm)?)/
- /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
- /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
- .hitbox.com 
+ 
+ # Block all URLs that match these patterns
+ { +block }
+  ad.
+  ad[sv].
+  .*ads.
+  banner?.
+  /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
+  .hitbox.com 
+  media./.*(ads|banner)
+
+ # Block, and treat these URL patterns as if they were 'images'.
+ # We would expect these to be ads.
+ { +block-as-image }
+  .ad.doubleclick.net
+  .a[0-9].yimg.com/(?:(?!/i/).)*$
+  ad.*.doubleclick.net
 
  # Make exceptions for these harmless ones that would be 
- # caught by +block.
- {-block}
- include.ebay.com
- adsl.
- advice.
- .edu
- .ac.uk
- .uni-*.de
- .*downloads.
+ # caught by our +block patterns just above.
+ { -block }
+  adsl.
+  adobe.
+  advice.
+  .*downloads.
+  # uploads or downloads
+  /.*loads
+
+ +

+ +Then for a user.action, we would put local, +narrowly defined exceptions: +

+

+ # Re-define aliases as needed here
+ {{alias}}
+
+ # Useful aliases
+ -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
+ 
+ # Set personal exceptions to the policies in default.action #######
+
+ # Sites where we want persistent cookies, so allow *all* cookies
+ { -crunch-cookies -session-cookies-only }
+  .redhat.com
+  .sun.com
+  .msdn.microsoft.com
+ 
+ # These sites break easily. Use our "fragile" alias here.
+ { fragile }
+  .forbes.com
+  mybank.example.com
+
+ # Replace example.com's style sheet with one of my choosing
+ { +redirect{http://localhost/css-replacements/example.com.css} }
+  .example.com/stylesheet.css
 

See the comments in the configuration files themselves, or the -user-manual -for explanations of the above syntax, and other Privoxy +User Manual +for full explanations of the above syntax, and other Privoxy configuration options.  

FILES

@@ -254,6 +269,7 @@ configuration options. /etc/privoxy/standard.action /etc/privoxy/user.action /etc/privoxy/default.filter + /etc/privoxy/user.filter /etc/privoxy/trust /etc/privoxy/templates/* /var/log/privoxy/logfile @@ -262,8 +278,8 @@ configuration options.

Various other files should be included, but may vary depending on platform -and build configuration. More documentation should be included in the local -documentation directory, though is not complete at this time. +and build configuration. Additional documentation should be included in the local +documentation directory.  

SIGNALS

@@ -281,12 +297,8 @@ automatically.

-This is a beta version of Privoxy. Not -all features are well tested. -

- -Please see the user-manual on how to contact the -developers for feature requests, reporting problems, and other questions. +Please see the User Manual on how to contact the +developers, for feature requests, reporting problems, and other questions.  

SEE ALSO

@@ -297,70 +309,98 @@ users:

-http://www.privoxy.org/, -The Privoxy Home page. +http://www.privoxy.org/, +the Privoxy Home page. +

+http://www.privoxy.org/faq/, +the Privoxy FAQ.

-http://sourceforge.net/projects/ijbswa, +http://sourceforge.net/projects/ijbswa/, the Project Page for Privoxy on -Sourceforge. +SourceForge. +

+http://config.privoxy.org/, +the web-based user interface. Privoxy must be +running for this to work. Shortcut: http://p.p/ +

+http://sourceforge.net/tracker/?group_id=11118&atid=460288, to submit ``misses'' and other +configuration related suggestions to the developers.

-http://p.p/, access -Privoxy from your browser. Alternately, -http://config.privoxy.org -may work in some situations where the first does not. +http://www.junkbusters.com/ht/en/cookies.html, +an explanation how cookies are used to track web users.

-http://p.p/ -to submit ``misses'' to the developers. +http://www.junkbusters.com/ijb.html, +the original Internet Junkbuster.

-http://www.junkbusters.com/ht/en/cookies.html +http://privacy.net/, a useful site +to check what information about you is leaked while you browse the web.

-http://www.waldherr.org/junkbuster/ +http://www.squid-cache.org/, a popular +caching proxy, which is often used together with Privoxy.

-http://privacy.net/analyze/ +http://www.pps.jussieu.fr/~jch/software/polipo/, +Polipo is a caching proxy with advanced features +like pipelining, multiplexing and caching of partial instances. In many setups +it can be used as Squid replacement.

-http://www.squid-cache.org/ +http://tor.eff.org/, +Tor can help anonymize web browsing, +web publishing, instant messaging, IRC, SSH, and other applications. +

+http://www.privoxy.org/developer-manual/, +the Privoxy developer manual.  

DEVELOPMENT TEAM

- Jon Foster
- Andreas Oesterhelt
- Stefan Waldherr
- Thomas Steudten
- Rodney Stromlund
- Rodrigo Barbosa (RPM specfiles)
- Hal Burgiss (docs)
- Alexander Lazic
- Gábor Lipták
- Guy
- Haroon Rafique
- David Schmidt (OS/2, Mac OSX ports)
- Joerg Strohmayer
- Sarantis Paskalis
+ Fabian Keil, lead developer
+ David Schmidt, developer
+ 
+ Hal Burgiss
+ Gerry Murphy
+ Roland Rosenfeld
+ Jörg Strohmayer
 
 

COPYRIGHT AND LICENSE

+  +

COPYRIGHT

+ +

+ +Copyright (C) 2001-2007 by Privoxy Developers <ijbswa-developers@lists.sourceforge.net> +

+ +Some source code is based on code Copyright (C) 1997 by Anonymous Coders +and Junkbusters, Inc. and licensed under the GNU General Public +License. +  +

LICENSE

+

Privoxy is free software; you can -redistribute it and/or modify it under the terms of the GNU General Public -License as published by the Free Software Foundation; either version 2 of the -License, or (at your option) any later version. +redistribute it and/or modify it under the terms of the +GNU General Public +License, version 2, as published by the Free Software Foundation.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or -FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for -more details, which is available from the Free Software Foundation, Inc, 59 -Temple Place - Suite 330, Boston, MA 02111-1307, USA. +FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for +more details, which is available from the Free Software Foundation, Inc, +51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

-You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software Foundation, Inc., -59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. +You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc. 51 Franklin Street, Fifth Floor +Boston, MA 02110-1301 +USA


@@ -379,11 +419,15 @@ along with this program; if not, write to the Free Software Foundation, Inc.,
SEE ALSO
DEVELOPMENT TEAM
COPYRIGHT AND LICENSE
+
+
COPYRIGHT
+
LICENSE
+

This document was created by man2html, using the manual pages.
-Time: 23:48:45 GMT, April 24, 2002 +Time: 15:18:46 GMT, January 19, 2008