X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=e9e78852cf54f6fae420803dfd6885d9a6aba526;hp=7bdb75e3d362630fdeb514868eee90e16c3a29c0;hb=07cf496b6edcbd3cf315ec7c48f2c94be27357b1;hpb=062c2d7a59739c3bd24b29322cb49044f92e9aa7 diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index 7bdb75e3..e9e78852 100644 --- a/doc/webserver/man-page/privoxy-man-page.html +++ b/doc/webserver/man-page/privoxy-man-page.html @@ -1,435 +1,215 @@ + - -Man page of PRIVOXY - -

PRIVOXY

-Section: (1)
Updated: 18 June 2008
Index -
- -  -

NAME

- -privoxy - Privacy Enhancing Proxy -  -

SYNOPSIS

- -

-privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [--pre-chroot-nslookup hostname ] [configfile ] -

-  -

OPTIONS

- -

- -Privoxy may be invoked with the following command line -options: -

-
--help
-Print brief usage info and exit. -
--version
-Print version info and exit. -
--no-daemon
-Don't become a daemon, i.e. don't fork and become process group -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. -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 -user and the GID of -group, or, if the optional -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 . If no -configfile is found, Privoxy will -fail to start. -  -

DESCRIPTION

- -

- -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). -  -

INSTALLATION AND USAGE

- -

- -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. 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. -  -

CONFIGURATION

- -

- -Privoxy can be configured with the various configuration -files. The default configuration files are: config, -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. -

- -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://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, 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 simple default.action -configuration might look like: -

-

- # Define a few useful custom aliases for later use
- {{alias}}
-
- # 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
-
- ## 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
-
- 
- # 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 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 full explanations of the above syntax, and other Privoxy -configuration options. -  -

FILES

- -

-

- 
- /usr/sbin/privoxy
- /etc/privoxy/config
- /etc/privoxy/default.action
- /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
-
- -

- -Various other files should be included, but may vary depending on platform -and build configuration. Additional documentation should be included in the local -documentation directory. -  -

SIGNALS

- -

- -Privoxy terminates on the SIGINT, -SIGTERM and SIGABRT signals. Log -rotation scripts may cause a re-opening of the logfile by sending a -SIGHUP to Privoxy. Note that unlike -other daemons, Privoxy does not need to be made aware of -config file changes by SIGHUP -- it will detect them -automatically. -  -

NOTES

- -

- -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. -  -

SEE ALSO

- -

- -Other references and sites of interest to Privoxy -users: -

- -

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

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

-http://sourceforge.net/projects/ijbswa/, -the Project Page for Privoxy on -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://www.junkbusters.com/ht/en/cookies.html, -an explanation how cookies are used to track web users. -

-http://www.junkbusters.com/ijb.html, -the original Internet Junkbuster. -

-http://privacy.net/, a useful site -to check what information about you is leaked while you browse the web. -

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

-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://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

- -

-

- Fabian Keil, lead developer
- David Schmidt, developer
- 
- Hal Burgiss
- Mark Miller
- Gerry Murphy
- Roland Rosenfeld
- Jörg Strohmayer
-
- -  -

COPYRIGHT AND LICENSE

- -  -

COPYRIGHT

- -

- -Copyright (C) 2001-2008 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, 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 details. -

- -You should have received a copy of the GNU GPL -along with this program; if not, write to the Free Software -Foundation, Inc. 51 Franklin Street, Fifth Floor -Boston, MA 02110-1301 -USA -

- -


- 

Index

-
-
NAME
-
SYNOPSIS
-
OPTIONS
-
DESCRIPTION
-
INSTALLATION AND USAGE
-
CONFIGURATION
-
SAMPLE CONFIGURATION
-
FILES
-
SIGNALS
-
NOTES
-
SEE ALSO
-
DEVELOPMENT TEAM
-
COPYRIGHT AND LICENSE
-
-
COPYRIGHT
-
LICENSE
-
-
-
-This document was created by -man2html, -using the manual pages.
-Time: 01:33:00 GMT, June 19, 2008 - - + + + + + Privoxy Man page + + + + +

NAME

+
+
+
+
+ +

SYNOPSIS

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

OPTIONS

+
+       Privoxy may be invoked with the following command line options:
+
+       --help Print brief usage  info and exit.
+
+       --version
+          Print version info and exit.
+
+       --no-daemon
+          Don't   become   a  daemon,  i.e.  don't fork and become process
+          group leader, don't detach from controlling tty, and do all log-
+          ging there.
+
+       --pidfile pidfile
+          On startup, write the process ID to pidfile.  Delete the pidfile
+          on exit.  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
+          user and the GID of group, or, if   the  optional  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 pre-
+          tend to the Privoxy  process  that  the  directory  tree   starts
+          there.  If set up carefully, this can limit the impact of possi-
+          ble 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. If no con-
+       figfile is found, Privoxy will fail to start.
+
+
+
+ +

DESCRIPTION

+
+       Privoxy is a non-caching web proxy with advanced filtering capabilities
+       for enhancing privacy, modifying web page data and HTTP  headers,  con-
+       trolling  access,  and  removing ads and other obnoxious Internet junk.
+       Privoxy has a flexible configuration and  can  be  customized  to  suit
+
+
+
+ +

INSTALLATION AND USAGE

+
+       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 Firefox, go through: Tools; Options; General;
+       Connection Settings; Manual Proxy Configuration.
+
+       For Internet Explorer, go through: Tools; Internet Properties;  Connec-
+       tions; LAN Settings.
+
+       The Secure (SSL) Proxy should also be set to the same values, otherwise
+       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.
+
+
+
+ +

CONFIGURATION

+
+       Privoxy   can  be  configured  with the various configuration files. The
+       default configuration files are: config,  default.filter,  default.action
+       and  default.action.  user.action  should  be  used for locally defined
+       exceptions to the default rules in match-all.action and 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.
+
+       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://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, 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.
+
+
+
+ +

FILES

+
+    /usr/sbin/privoxy
+    /etc/privoxy/config
+    /etc/privoxy/match-all.action
+    /etc/privoxy/default.action
+    /etc/privoxy/user.action
+    /etc/privoxy/default.filter
+       detect them automatically.
+
+
+
+ +

NOTES

+
+       This  is  a  UNRELEASED  version  of Privoxy. Not all features are well
+       tested.
+
+       Please see the User Manual on how to contact the   developers,  for  fea-
+       ture requests, reporting problems, and other questions.
+
+
+
+ +

SEE ALSO

+
+       Other references and sites of interest to Privoxy users:
+
+
+       http://www.privoxy.org/, the Privoxy Home page.
+
+       http://www.privoxy.org/faq/, the Privoxy  FAQ.
+
+       http://www.privoxy.org/developer-manual/, the Privoxy developer manual.
+
+       https://sourceforge.net/projects/ijbswa/, the Project Page for  Privoxy
+       on SourceForge.
+
+       http://config.privoxy.org/,  the web-based user interface. Privoxy must
+       be running for this to work. Shortcut: http://p.p/
+
+       https://sourceforge.net/tracker/?group_id=11118&atid=460288, to  submit
+       ``misses''  and other configuration related suggestions to the develop-
+       ers.
+
+
+
+ +

DEVELOPMENT TEAM

+
+    Fabian Keil, lead developer
+    David Schmidt, developer
+
+    Hal Burgiss
+    Mark Miller
+    Gerry Murphy
+    Lee Rian
+    Roland Rosenfeld
+
+
+
+ +

COPYRIGHT AND LICENSE

+
+   COPYRIGHT
+       Copyright  (C)  2001-2011  by   Privoxy   Developers   <ijbswa-develop-
+       ers@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, version 2,  as  pub-
+       lished by the Free Software Foundation.
+
+ +