X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=bd63f559d4fbd5405e58979b38b91d7a16a4adc9;hp=71e518014fc0f0fcf9118db355502830fd04ce7d;hb=a5b4d31ab5ad2ed24cdb53ffa92679411b4176b0;hpb=72081f829de368392d04076728f8c991178c0080;ds=sidebyside diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index 71e51801..bd63f559 100644 --- a/doc/webserver/man-page/privoxy-man-page.html +++ b/doc/webserver/man-page/privoxy-man-page.html @@ -1,422 +1,212 @@ - -Manpage of PRIVOXY - -

PRIVOXY

-Section: (1)
Updated: 25 March 2003
Index -
- -  -

NAME

- -privoxy - Privacy Enhancing Proxy -  -

SYNOPSIS

- -

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

-

-privoxy.exe [configfile ] (Windows) -

-  -

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

- -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 -configfile is found, Privoxy will -fail to start. -  -

DESCRIPTION

- -

- -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 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; -Preferences; Advanced; -Proxies; Manual Proxy Configuration; -View. -

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

- -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 These are all 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. -

- -The name and number of configuration files has changed from previous -versions. In fact, the configuration itself is changed and much more -sophisticated. See the user-manual for a complete -explanation of all configuration options and general usage, and notes for -upgrading from Junkbuster and earlier Privoxy -versions. -

- -The actions list (ad blocks, etc) can also be configured with your -web browser at http://config.privoxy.org/. -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. -  -

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
- +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
- -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- +imageblock      = +block +handle-as-image
-
- # Fragile sites should have the minimum changes
- fragile     = -block -deanimate-gifs -fast-redirects -filter \
-               -hide-referer -prevent-cookies -kill-popups
-
- ## Turn some actions on ################################
- { \
- -add-header \
- -block \
- +deanimate-gifs{last} \
- -downgrade-http-version \
- -fast-redirects \
- +filter{html-annoyances} \
- +filter{js-annoyances} \
- +filter{content-cookies} \
- +filter{webbugs} \
- +filter{banners-by-size} \
- +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 \
- -crunch-cookies \
- -kill-popups \
- }
- /   # '/' Matches *all* URL patterns
- 
- # Block, and treat these URL patterns as if they were 'images'.
- # We would expect these to be ads.
- {+imageblock}
-  .ad.doubleclick.net
-  .a[0-9].yimg.com/(?:(?!/i/).)*$
-  ad.*.doubleclick.net
-
- # Block any URLs that match these patterns
- {+block}
-  ad*.
-  .*ads.
-  banner?.
-  /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
-  .hitbox.com 
-
- # Make exceptions for these harmless ones that would be 
- # caught by our +block patterns just above.
- {-block}
-  adsl.
-  advice.
-  .*downloads.
-
- -

- -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 persistant cookies, so allow *all* cookies
- {-crunch-cookies -session-cookies-only}
-  .redhat.com
-  .sun.com
-  .msdn.microsoft.com
- 
- # This site breaks easily.
- {-block -fast-redirects}
-  .forbes.com
-
- -

- -See the comments in the configuration files themselves, or the -user-manual -for 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/trust
- /etc/privoxy/templates/*
- /var/log/privoxy/logfile
-
- -

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

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

- -

- -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://www.privoxy.org/actions/, to submit ``misses'' to the developers. -

-http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/contrib/, cool -and fun ideas from Privoxy users. -

-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://www.waldherr.org/junkbuster/, -Stefan Waldherr's version of Junkbuster, from which Privoxy was -derived. -

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

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

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

DEVELOPMENT TEAM

- -

-

- Hal Burgiss (docs)
- Jon Foster
- Andreas Oesterhelt
- David Schmidt (OS/2, Mac OSX ports)
-
- Johny Agotnes 
- Rodrigo Barbosa (RPM specfiles)
- Moritz Barsnick
- Mattes Dolak 
- Karsten Hopp (Red Hat)
- Alexander Lazic
- Daniel Leite
- Gábor Lipták
- Adam Lock (Win32)
- Guy Laroche
- Haroon Rafique
- Roland Rosenfeld (Debian)
- Georg Sauthoff (Gentoo)
- Thomas Steudten
- Joerg Strohmayer (Amiga)
- Rodney Stromlund
- Sviatoslav Sviridov
- Sarantis Paskalis
- Stefan Waldherr
-
- -  -

COPYRIGHT AND LICENSE

- -  -

COPYRIGHT

- -

- -Copyright (C) 2001 - 2003 by Privoxy Developers <developers@privoxy.org> -

- -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 -more details, which is available from 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. 59 Temple Place - Suite 330 -Boston, MA 02111-1307 -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: 02:05:48 GMT, March 26, 2003 - - + + + + + + + + + + PRIVOXY + + + +

PRIVOXY

NAME
+ SYNOPSIS
+ OPTIONS
+ DESCRIPTION
+ INSTALLATION AND USAGE
+ CONFIGURATION
+ FILES
+ SIGNALS
+ NOTES
+ SEE ALSO
+ DEVELOPMENT TEAM
+ COPYRIGHT AND LICENSE
+
+ +

NAME

+

privoxy − Privacy Enhancing Proxy

+

SYNOPSIS

+

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

+

OPTIONS

+

Privoxy may be invoked with the following command line options: +
+ −−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.

+

−−config-test

+

Exit after loading the configuration files before binding to the listen address. The exit + code signals whether or not the configuration files have been successfully loaded.

+

If the exit code is 1, at least one of the configuration files is + invalid, if it is 0, all the configuration files have been successfully loaded (but may still contain errors that can + currently only be detected at run time).

+

This option doesn’t affect the log setting, combination with + "--no-daemon" is recommended if a configured log file shouldn’t be used.

+ + + + + + + + +
+

−−help

+
+

Print brief usage 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.

+

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

+

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

+

−−version

+

Print version info and exit.

+

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 and HTTP headers, controlling access, and removing ads and other + obnoxious Internet junk. Privoxy has a flexible configuration and can be customized to suit individual needs and + tastes. It has application for both stand-alone systems and multi-user networks.

+

Privoxy is Free Software and licensed under the GNU GPLv2 or later.

+

Privoxy is an associated project of Software in the Public Interest + (SPI).

+

Helping hands and donations are welcome:

+ + + + + + + + + + + + + + + +
+

+
+

https://www.privoxy.org/participate

+
+

+
+

https://www.privoxy.org/donate

+
+

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; 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, 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
+ /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 and SIGTERM + 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. Signals other than the ones listed above aren’t explicitly handled and + result in the default action defined by the operating system.

+

NOTES

+

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:

+

https://www.privoxy.org/, the Privoxy Home page.

+

https://www.privoxy.org/faq/, the Privoxy FAQ.

+

https://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/p/ijbswa/actionsfile-feedback/, to submit + ‘‘misses’’ and other configuration related suggestions to the developers.

+

DEVELOPMENT TEAM

+

Fabian Keil, lead developer
+ David Schmidt
+ Lee Rian
+ Roland Rosenfeld
+ Ian Silvester

+

COPYRIGHT AND LICENSE

+

COPYRIGHT
+ Copyright (C) 2001-2020 by Privoxy Developers <privoxy-devel@lists.privoxy.org>

+

Some source code is based on code Copyright (C) 1997 by Anonymous Coders + and Junkbusters, Inc.

+

LICENSE
+ Privoxy
is free software; you can redistribute and/or modify its source code 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.

+

The same is true for Privoxy binaries unless they are linked with + a mbed TLS version that is licensed under the Apache 2.0 license in which case you can redistribute and/or modify the + Privoxy binaries under the terms of the GNU General Public License as published by the Free Software + Foundation, either version 3 of the license, or (at your option) any later version.

+

Privoxy 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 license for details.

+
+ +