X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=659c288b91d21721019e27a984b26e3c64a18dfa;hp=be1b7c7a4e69f51d27bd8d4948f7c29c46d615cf;hb=81bc12b6013fb4a4043614934dccd3b2a51065f9;hpb=47ebc96cd29a0e2de4c752e7b42006c27d365064 diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index be1b7c7a..659c288b 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: 09 May 2002
Index +Section: (1)
Updated: 15 February 2009
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. @@ -104,25 +125,32 @@ 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 +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. On Windows, OS/2 and AmigaOS, -these files are in the same directory as the Privoxy -executable. +/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

@@ -135,63 +163,62 @@ 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 + -hide-referer -prevent-cookies ## 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 \ - +prevent-reading-cookies \ - +prevent-setting-cookies \ - -kill-popups \ - } - / # Match all URLs - - # Block, and treat these URL patterns as if they were 'images'. - {+imageblock} - .ad.doubleclick.net - .a[0-9].yimg.com/(?:(?!/i/).)*$ - ad.*.doubleclick.net + ## NOTE: Actions are off by default, unless explictily turned on + ## otherwise with the '+' operator. + +{ \ ++change-x-forwarded-for{block} \ ++deanimate-gifs{last} \ ++filter{refresh-tags} \ ++filter{img-reorder} \ ++filter{banners-by-size} \ ++filter{webbugs} \ ++filter{jumping-windows} \ ++filter{ie-exploits} \ ++hide-from-header{block} \ ++hide-referrer{conditional-block} \ ++session-cookies-only \ ++set-image-blocker{pattern} \ +} +/ # '/' Match *all* URL patterns - # Block any URLs that match these patterns - {+block} - ad*. + + # Block all URLs that match these patterns + { +block } + ad. + ad[sv]. .*ads. banner?. /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?) - /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|maino(kset|nta|s)?)/ .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 above. - {-block} + # caught by our +block patterns just above. + { -block } adsl. + adobe. advice. .*downloads. + # uploads or downloads + /.*loads

@@ -200,23 +227,35 @@ 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
- {-prevent-reading-cookies -prevent-setting-cookies -session-cookies-only}
+ # Sites where we want persistent cookies, so allow *all* cookies
+ { -crunch-cookies -session-cookies-only }
   .redhat.com
   .sun.com
   .msdn.microsoft.com
  
- {-block -fast-redirects}
+ # 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

@@ -226,10 +265,11 @@ configuration options. /usr/sbin/privoxy /etc/privoxy/config + /etc/privoxy/match-all.action /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 @@ -238,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

@@ -257,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

@@ -273,46 +309,57 @@ users:

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

-http://sourceforge.net/projects/ijbswa, +http://www.privoxy.org/faq/, +the Privoxy FAQ. +

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

+https://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://www.squid-cache.org/, a popular +caching proxy, which is often used together with Privoxy.

-http://www.waldherr.org/junkbuster/ +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://privacy.net/analyze/ +https://www.torproject.org/, +Tor can help anonymize web browsing, +web publishing, instant messaging, IRC, SSH, and other applications.

-http://www.squid-cache.org/ +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
+ Mark Miller
+ Gerry Murphy
+ Lee Rian
+ Roland Rosenfeld
+ Jörg Strohmayer
 
  @@ -323,7 +370,7 @@ may work in some situations where the first does not.

-Copyright (C) 2001, 2002 by Privoxy Developers <developers@privoxy.org> +Copyright (C) 2001-2009 by Privoxy Developers <ijbswa-developers@lists.sourceforge.net>

Some source code is based on code Copyright (C) 1997 by Anonymous Coders @@ -336,22 +383,19 @@ 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. +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 details.

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

@@ -380,6 +424,6 @@ USA This document was created by man2html, using the manual pages.
-Time: 20:47:35 GMT, May 09, 2002 +Time: 18:45:33 GMT, February 15, 2009