This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: privoxy-man-page.sgml,v 1.9 2002/04/25 14:45:25 hal9 Exp $
+ $Id: privoxy-man-page.sgml,v 2.5 2006/07/18 14:48:51 david__schmidt Exp $
- Written by and Copyright (C) 2001 the SourceForge
- Privoxy team. http://www.privoxy.org/
-
- Based on the Internet Junkbuster originally written
- by and Copyright (C) 1997 Anonymous Coders and
- Junkbusters Corporation. http://www.junkbusters.com
+ Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
+ See LICENSE.
========================================================================
NOTE: Please read developer-manual/documentation.html before touching
<!entity p-intro SYSTEM "privoxy.sgml">
<!entity seealso SYSTEM "seealso.sgml">
<!entity copyright SYSTEM "copyright.sgml">
+<!entity license SYSTEM "license.sgml">
<!entity authors SYSTEM "p-authors.sgml">
-<!entity p-version "2.9.15">
-<!entity p-status "beta">
+<!entity p-version "3.0.4">
+<!entity p-status "BETA">
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
<!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
<!entity % p-authors-formal "IGNORE"> <!-- exclude additional formating -->
+<!entity my-copy "(C)"> <!-- db2man barfs on copyright symbol -->
]>
<refentry id="privoxy">
<refentryinfo>
- <date>2002-04-11</date>
+ <date>2006-08-24</date>
</refentryinfo>
-
<refmeta>
<refentrytitle>privoxy</refentrytitle>
<manvolnum>1</manvolnum>
- <refmiscinfo>Privoxy &p-version;<![%p-not-stable;[ &p-status;]]></refmiscinfo>
+ <refmiscinfo>
+ Privoxy &p-version;<![%p-not-stable;[ &p-status;]]>
+ </refmiscinfo>
</refmeta>
<refnamediv>
<arg><option>--no-daemon</option></arg>
<arg><option>--pidfile </option><replaceable class="parameter">pidfile</replaceable></arg>
<arg><option>--user </option><replaceable class="parameter">user[.group]</replaceable></arg>
+ <arg><option>--chroot</option></arg>
<arg><replaceable class="parameter">configfile</replaceable></arg>
- <command>(UNIX)</command>
+ <command> (UNIX)</command>
</cmdsynopsis>
<cmdsynopsis>
<command>privoxy.exe</command>
<arg><replaceable class="parameter">configfile</replaceable></arg>
- <command>(Windows)</command>
+ <command> (Windows)</command>
</cmdsynopsis>
</refsynopsisdiv>
<para>
On startup, write the process ID to <replaceable class="parameter">pidfile</replaceable>.
Delete the <replaceable class="parameter">pidfile</replaceable> on exit.
- Failiure to create or delete the <replaceable class="parameter">pidfile</replaceable>
+ Failure to create or delete the <replaceable class="parameter">pidfile</replaceable>
is non-fatal. If no <command>--pidfile</command> option is given, no PID file will be used.
</para>
</listitem>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>--chroot</term>
+ <listitem>
+ <para>
+ 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
+ <command>Privoxy</command> process that the directory tree starts
+ there. If set up carefully, this can limit the impact of possible
+ vulnerabilities in <command>Privoxy</command> to the files contained in
+ that hierarchy.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
-
+
<para>
If the <filename>configfile</filename> is not specified on the command line,
<command>Privoxy</command> will look for a file named
</para>
<para>
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: <command>Privoxy</command> can only
+ proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols.
</para>
+
<para>
For other browsers, check the documentation.
</para>
<filename>default.filter</filename>, and
<filename>default.action</filename>. <filename>user.action</filename> should
be used for locally defined exceptions to the default rules of
- <filename>default.action</filename> These are all well commented. On Unix
+ <filename>default.action</filename>, and <filename>user.filter</filename> for
+ locally defined filters. These are well commented. On Unix
and Unix-like systems, these are located in
<filename>/etc/privoxy/</filename> by default. On Windows, OS/2 and AmigaOS,
these files are in the same directory as the <command>Privoxy</command>
executable.
</para>
<para>
- 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
- <ulink url="http://www.privoxy.org/user-manual/">user-manual</ulink> for a
- brief explanation of all configuration options.
+ See the <ulink
+ url="http://www.privoxy.org/user-manual/">user-manual</ulink> for a complete
+ explanation of general usage, configuration options, new features and notes for
+ upgrading.
</para>
<para>
The actions list (ad blocks, etc) can also be configured with your
- web browser at <ulink url="http://ijbswa.sourceforge.net/config">http://ijbswa.sourceforge.net/config</ulink>.
+ web browser at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>.
<command>Privoxy's</command> configuration parameters can also be viewed at
the same page. In addition, <command>Privoxy</command> can be toggled on/off.
- This is an internal page.
+ This is an internal page, and does not require Internet access.
</para>
</refsect1>
{{alias}}
# Useful aliases
- +prevent-cookies = +prevent-setting-cookies +prevent-reading-cookies
- -prevent-cookies = -prevent-setting-cookies -prevent-reading-cookies
+ +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
{ \
-add-header \
-block \
+ -content-type-overwrite \
+ -crunch-if-none-match \
+ +crunch-incoming-cookies \
+ +crunch-outgoing-cookies \
+ +crunch-server-header {no-cache} \
+deanimate-gifs{last} \
-downgrade-http-version \
-fast-redirects \
- +filter{html-annoyances} \
- +filter{js-annoyances} \
+ -force-text-mode \
+ -filter{html-annoyances} \
+ -filter{js-annoyances} \
+filter{content-cookies} \
+filter{webbugs} \
- +filter{banners-by-size} \
+ -filter{banners-by-size} \
+ -handle-as-empty-document \
+ +hide-accept-language{en-ca} \
+ +hide-content-disposition {block} \
+hide-forwarded-for-headers \
+hide-from-header{block} \
+ +hide-if-modified-since {-1} \
+hide-referrer{forge} \
-hide-user-agent \
-handle-as-image \
+ -inspect-jpegs \
+ -kill-popups \
+set-image-blocker{pattern} \
-limit-connect \
+ +overwrite-last-modified {randomize} \
+prevent-compression \
+session-cookies-only \
- +prevent-reading-cookies \
- +prevent-setting-cookies \
- -kill-popups \
+ +treat-forbidden-connects-like-blocks \
+ -crunch-cookies \
}
- / # Match all URLs
+ / # '/' 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/).)*$
.*ads.
banner?.
/.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
- /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|maino(kset|nta|s)?)/
.hitbox.com
# Make exceptions for these harmless ones that would be
- # caught by +block above.
+ # caught by our +block patterns just above.
{-block}
adsl.
advice.
</para>
<literallayout>
+ # 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 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
<filename>/etc/privoxy/standard.action</filename>
<filename>/etc/privoxy/user.action</filename>
<filename>/etc/privoxy/default.filter</filename>
+ <filename>/etc/privoxy/user.filter</filename>
<filename>/etc/privoxy/trust</filename>
<filename>/etc/privoxy/templates/*</filename>
<filename>/var/log/privoxy/logfile</filename>
<para>
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.
+ documentation directory.
</para>
</refsect1>
all features are well tested.
</para>]]>
<para>
- Please see the <citetitle>user-manual</citetitle> on how to contact the
- developers for feature requests, reporting problems, and other questions.
+ Please see the <citetitle>User Manual</citetitle> on how to contact the
+ developers, for feature requests, reporting problems, and other questions.
</para>
</refsect1>
<!-- ~~~~~ New section ~~~~~ -->
<refsect1><title>Copyright and License</title>
+
+<refsect2><title>Copyright</title>
<!-- Include copyright.sgml boilerplate: -->
©right;
<!-- end boilerplate -->
+</refsect2>
+
+<refsect2><title>License</title>
+<!-- Include license.sgml boilerplate: -->
+ &license;
+<!-- end boilerplate -->
+</refsect2>
</refsect1>
</refentry>
projects / privoxy.git / blobdiff
![[privoxy.git]](/gitweb/-%22http:/sourceforge.net/static/git-favicon.png?p=privoxy.git;a=tree;hb=d7bec693824da76d7088f831b7c43ac9cbd6e813){kind=link}
