<!entity license SYSTEM "license.sgml">
<!entity p-authors SYSTEM "p-authors.sgml">
<!entity config SYSTEM "p-config.sgml">
-<!entity p-version "3.0.20">
-<!entity p-status "beta">
+<!entity changelog SYSTEM "changelog.sgml">
+<!entity p-version "3.0.21">
+<!entity p-status "UNRELEASED">
<!entity % p-authors-formal "INCLUDE"> <!-- include additional text, etc -->
<!entity % p-not-stable "INCLUDE">
<!entity % p-stable "IGNORE">
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 2.159 2013/01/09 15:03:06 fabiankeil Exp $
+ $Id: user-manual.sgml,v 2.167 2013/01/25 14:19:27 fabiankeil Exp $
Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: user-manual.sgml,v 2.159 2013/01/09 15:03:06 fabiankeil Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 2.167 2013/01/25 14:19:27 fabiankeil Exp $</pubdate>
<!--
<!-- XXX: The installation sections should be sorted -->
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-pack-rpm"><title>Red Hat and Fedora RPMs</title>
-
-<para>
- RPMs can be installed with <literal>rpm -Uvh privoxy-&p-version;-1.rpm</literal>,
- and will use <filename>/etc/privoxy</filename> for the location
- of configuration files.
-</para>
-
-<para>
- Note that on Red Hat, <application>Privoxy</application> will
- <emphasis>not</emphasis> be automatically started on system boot. You will
- need to enable that using <command>chkconfig</command>,
- <command>ntsysv</command>, or similar methods.
-</para>
-
-<para>
- If you have problems with failed dependencies, try rebuilding the SRC RPM:
- <literal>rpm --rebuild privoxy-&p-version;-1.src.rpm</literal>. This
- will use your locally installed libraries and RPM version.
-</para>
-
-<para>
- Also note that if you have a <application>Junkbuster</application> RPM installed
- on your system, you need to remove it first, because the packages conflict.
- Otherwise, RPM will try to remove <application>Junkbuster</application>
- automatically if found, before installing <application>Privoxy</application>.
-</para>
-</sect3>
-
<!-- ~~~~~ New section ~~~~~ -->
<sect3 id="installation-deb"><title>Debian and Ubuntu</title>
<para>
</sect3>
<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-pack-win"><title>Windows</title>
-
-<para>
- Just double-click the installer, which will guide you through
- the installation process. You will find the configuration files
- in the same directory as you installed <application>Privoxy</application> in.
-</para>
-<para>
- Version 3.0.5 beta introduced full <application>Windows</application> service
- functionality. On Windows only, the <application>Privoxy</application>
- program has two new command line arguments to install and uninstall
- <application>Privoxy</application> as a <emphasis>service</emphasis>.
-</para>
- <variablelist>
- <varlistentry>
- <term>Arguments:</term>
- <listitem>
- <para>
- <replaceable class="parameter">--install</replaceable>[:<replaceable class="parameter">service_name</replaceable>]
- </para>
- <para>
- <replaceable class="parameter">--uninstall</replaceable>[:<replaceable class="parameter">service_name</replaceable>]
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- After invoking <application>Privoxy</application> with
- <command>--install</command>, you will need to bring up the
- <application>Windows</application> service console to assign the user you
- want <application>Privoxy</application> to run under, and whether or not you
- want it to run whenever the system starts. You can start the
- <application>Windows</application> services console with the following
- command: <command>services.msc</command>. If you do not take the manual step
- of modifying <application>Privoxy's</application> service settings, it will
- not start. Note too that you will need to give Privoxy a user account that
- actually exists, or it will not be permitted to
- write to its log and configuration files.
-</para>
-
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-pack-bintgz"><title>Solaris <!--, NetBSD, HP-UX--></title>
-
-<para>
- Create a new directory, <literal>cd</literal> to it, then unzip and
- untar the archive. For the most part, you'll have to figure out where
- things go. <!-- FIXME, more info needed? -->
-</para>
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-os2"><title>OS/2</title>
-
-<para>
- First, make sure that no previous installations of
- <application>Junkbuster</application> and / or
- <application>Privoxy</application> are left on your
- system. Check that no <application>Junkbuster</application>
- or <application>Privoxy</application> objects are in
- your startup folder.
-
-</para>
-
-<para>
- Then, just double-click the WarpIN self-installing archive, which will
- guide you through the installation process. A shadow of the
- <application>Privoxy</application> executable will be placed in your
- startup folder so it will start automatically whenever OS/2 starts.
-</para>
-
-<para>
- The directory you choose to install <application>Privoxy</application>
- into will contain all of the configuration files.
-</para>
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-mac"><title>Mac OS X</title>
-<para>
- Installation instructions for the OS X platform depend upon whether
- you downloaded a ready-built installation package (.pkg or .mpkg) or have
- downloaded the source code.
-</para>
-</sect3>
-<sect3 renderas="sect4" id="OS-X-install-from-package">
-<title>Installation from ready-built package</title>
-<para>
- The downloaded file will either be a .pkg (for OS X 10.5 upwards) or a bzipped
- .mpkg file (for OS X 10.4). The former can be double-clicked as is and the
- installation will start; double-clicking the latter will unzip the .mpkg file
- which can then be double-clicked to commence the installation.
-</para>
-<para>
- The privoxy service will automatically start after a successful installation
- (and thereafter every time your computer starts up) however you will need to
- configure your web browser(s) to use it. To do so, configure them to use a
- proxy for HTTP and HTTPS at the address 127.0.0.1:8118.
-</para>
-<para>
- To prevent the privoxy service from automatically starting when your computer
- starts up, remove or rename the file <literal>/Library/LaunchDaemons/org.ijbswa.privoxy.plist</literal>
- (on OS X 10.5 and higher) or the folder named
- <literal>/Library/StartupItems/Privoxy</literal> (on OS X 10.4 'Tiger').
-</para>
-<para>
- To manually start or stop the privoxy service, use the scripts startPrivoxy.sh
- and stopPrivoxy.sh supplied in /Applications/Privoxy. They must be run from an
- administrator account, using sudo.
-</para>
-<para>
- To uninstall, run /Applications/Privoxy/uninstall.command as sudo from an
- administrator account.
-</para>
-</sect3>
-<sect3 renderas="sect4" id="OS-X-install-from-source">
-<title>Installation from source</title>
-<para>
- To build and install the Privoxy source code on OS X you will need to obtain
- the macsetup module from the Privoxy Sourceforge CVS repository (refer to
- Sourceforge help for details of how to set up a CVS client to have read-only
- access to the repository). This module contains scripts that leverage the usual
- open-source tools (available as part of Apple's free of charge Xcode
- distribution or via the usual open-source software package managers for OS X
- (MacPorts, Homebrew, Fink etc.) to build and then install the privoxy binary
- and associated files. The macsetup module's README file contains complete
- instructions for its use.
-</para>
-<para>
- The privoxy service will automatically start after a successful installation
- (and thereafter every time your computer starts up) however you will need to
- configure your web browser(s) to use it. To do so, configure them to use a
- proxy for HTTP and HTTPS at the address 127.0.0.1:8118.
-</para>
-<para>
- To prevent the privoxy service from automatically starting when your computer
- starts up, remove or rename the file <literal>/Library/LaunchDaemons/org.ijbswa.privoxy.plist</literal>
- (on OS X 10.5 and higher) or the folder named
- <literal>/Library/StartupItems/Privoxy</literal> (on OS X 10.4 'Tiger').
-</para>
-<para>
- To manually start or stop the privoxy service, use the Privoxy Utility
- for Mac OS X (also part of the macsetup module). This application can start
- and stop the privoxy service and display its log and configuration files.
-</para>
-<para>
- To uninstall, run the macsetup module's uninstall.sh as sudo from an
- administrator account.
-</para>
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-amiga"><title>AmigaOS</title>
-<para>
- Copy and then unpack the <filename>lha</filename> archive to a suitable location.
- All necessary files will be installed into <application>Privoxy</application>
- directory, including all configuration and log files. To uninstall, just
- remove this directory.
-</para>
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installation-tbz"><title>FreeBSD</title>
-
-<para>
- Privoxy is part of FreeBSD's Ports Collection, you can build and install
- it with <literal>cd /usr/ports/www/privoxy; make install clean</literal>.
-</para>
-<para>
- If you don't use the ports, you can fetch and install
- the package with <literal>pkg_add -r privoxy</literal>.
-</para>
-<para>
- The port skeleton and the package can also be downloaded from the
- <ulink url="https://sourceforge.net/project/showfiles.php?group_id=11118">File Release
- Page</ulink>, but there's no reason to use them unless you're interested in the
- beta releases which are only available there.
-</para>
-</sect3>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect3 id="installattion-gentoo"><title>Gentoo</title>
-<para>
- Gentoo source packages (Ebuilds) for <application>Privoxy</application> are
- contained in the Gentoo Portage Tree (they are not on the download page,
- but there is a Gentoo section, where you can see when a new
- <application>Privoxy</application> Version is added to the Portage Tree).
-</para>
-<para>
- Before installing <application>Privoxy</application> under Gentoo just do
- first <literal>emerge --sync</literal> to get the latest changes from the
- Portage tree. With <literal>emerge privoxy</literal> you install the latest
- version.
-</para>
-<para>
- Configuration files are in <filename>/etc/privoxy</filename>, the
- documentation is in <filename>/usr/share/doc/privoxy-&p-version;</filename>
- and the Log directory is in <filename>/var/log/privoxy</filename>.
-</para>
-</sect3>
-
-</sect2>
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect2 id="installation-source"><title>Building from Source</title>
-
-<para>
- The most convenient way to obtain the <application>Privoxy</application> sources
- is to download the source tarball from our
- <ulink url="http://sourceforge.net/project/showfiles.php?group_id=11118&package_id=10571">project download
- page</ulink>.
-</para>
-
-<para>
- If you like to live on the bleeding edge and are not afraid of using
- possibly unstable development versions, you can check out the up-to-the-minute
- version directly from <ulink url="http://sourceforge.net/cvs/?group_id=11118">the
- CVS repository</ulink>.
-<!--
- deprecated...out of business.
- or simply download <ulink
- url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.bz2">the nightly CVS
- tarball.</ulink>
--->
-</para>
-
-<!-- include buildsource.sgml boilerplate: -->
-&buildsource;
-<!-- end boilerplate -->
-
-</sect2>
-<!-- ~~~~~ New section ~~~~~ -->
-<sect2 id="installation-keepupdated"><title>Keeping your Installation Up-to-Date</title>
-
-<para>
- If you wish to receive an email notification whenever we release updates of
- <application>Privoxy</application> or the actions file, <ulink
- url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
- to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
-</para>
-
-<para>
- In order not to lose your personal changes and adjustments when updating
- to the latest <literal>default.action</literal> file we <emphasis>strongly
- recommend</emphasis> that you use <literal>user.action</literal> and
- <literal>user.filter</literal> for your local
- customizations of <application>Privoxy</application>. See the <link
- linkend="actions-file">Chapter on actions files</link> for details.
-</para>
-
-</sect2>
-
-
-</sect1>
-
-<!-- ~ End section ~ -->
-
-<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="whatsnew">
-<title>What's New in this Release</title>
-<para>
- <application>Privoxy 3.0.19</application> is a stable release.
- The changes since 3.0.18 stable are:
-</para>
-
-<para>
- <itemizedlist>
- <listitem>
- <para>
- Bug fixes:
- <itemizedlist>
- <listitem>
- <para>
- Prevent a segmentation fault when de-chunking buffered content.
- It could be triggered by malicious web servers if Privoxy was
- configured to filter the content and running on a platform
- where SIZE_T_MAX isn't larger than UINT_MAX, which probably
- includes most 32-bit systems. On those platforms, all Privoxy
- versions before 3.0.19 appear to be affected.
- To be on the safe side, this bug should be presumed to allow
- code execution as proving that it doesn't seems unrealistic.
- </para>
- </listitem>
- <listitem>
- <para>
- Do not expect a response from the SOCKS4/4A server until it
- got something to respond to. This regression was introduced
- in 3.0.18 and prevented the SOCKS4/4A negotiation from working.
- Reported by qqqqqw in #3459781.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- General improvements:
- <itemizedlist>
- <listitem>
- <para>
- Fix an off-by-one in an error message about connect failures.
- </para>
- </listitem>
- <listitem>
- <para>
- Use a GNUMakefile variable for the webserver root directory and
- update the path. Sourceforge changed it which broke various
- web-related targets.
- </para>
- </listitem>
- <listitem>
- <para>
- Update the CODE_STATUS description.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- </itemizedlist>
-</para>
-
-<para>
- The following changes were made between 3.0.17 and 3.0.18:
-</para>
-
-<para>
- <itemizedlist>
- <listitem>
- <para>
- Bug fixes:
- <itemizedlist>
- <listitem>
- <para>
- If a generated redirect URL contains characters RFC 3986 doesn't
- permit, they are (re)encoded. Not doing this makes Privoxy versions
- from 3.0.5 to 3.0.17 susceptible to HTTP response splitting (CWE-113)
- attacks if the +fast-redirects{check-decoded-url} action is used.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix a logic bug that could cause Privoxy to reuse a server
- socket after it got tainted by a server-header-tagger-induced
- block that was triggered before the whole server response had
- been read. If keep-alive was enabled and the request following
- the blocked one was to the same host and using the same forwarding
- settings, Privoxy would send it on the tainted server socket.
- While the server would simply treat it as a pipelined request,
- Privoxy would later on fail to properly parse the server's
- response as it would try to parse the unread data from the
- first response as server headers for the second one.
- Regression introduced in 3.0.17.
- </para>
- </listitem>
- <listitem>
- <para>
- When implying keep-alive in client_connection(), remember that
- the client didn't. Fixes a regression introduced in 3.0.13 that
- would cause Privoxy to wait for additional client requests after
- receiving a HTTP/1.1 request with "Connection: close" set
- and connection sharing enabled.
- With clients which terminates the client connection after detecting
- that the whole body has been received it doesn't really matter,
- but with clients that don't the connection would be kept open until
- it timed out.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix a subtle race condition between prepare_csp_for_next_request()
- and sweep(). A thread preparing itself for the next client request
- could briefly appear to be inactive.
- If all other threads were already using more recent files,
- the thread could get its files swept away under its feet.
- So far this has only been reproduced while stress testing in
- valgrind while touching action files in a loop. It's unlikely
- to have caused any actual problems in the real world.
- </para>
- </listitem>
- <listitem>
- <para>
- Disable filters if SDCH compression is used unless filtering is forced.
- If SDCH was combined with a supported compression algorithm, Privoxy
- previously could try to decompress it and ditch the Content-Encoding
- header even though the SDCH compression wasn't dealt with.
- Reported by zebul666 in #3225863.
- </para>
- </listitem>
- <listitem>
- <para>
- Make a copy of the --user value and only mess with that when splitting
- user and group. On some operating systems modifying the value directly
- is reflected in the output of ps and friends and can be misleading.
- Reported by zepard in #3292710.
- </para>
- </listitem>
- <listitem>
- <para>
- If forwarded-connect-retries is set, only retry if Privoxy is actually
- forwarding the request. Previously direct connections would be retried
- as well.
- </para>
- </listitem>
- <listitem>
- <para>
- Fixed a small memory leak when retrying connections with IPv6
- support enabled.
- </para>
- </listitem>
- <listitem>
- <para>
- Remove an incorrect assertion in compile_dynamic_pcrs_job_list()
- It could be triggered by a pcrs job with an invalid pcre
- pattern (for example one that contains a lone quantifier).
- </para>
- </listitem>
- <listitem>
- <para>
- If the --user argument user[.group] contains a dot, always bail out
- if no group has been specified. Previously the intended, but undocumented
- (and apparently untested), behaviour was to try interpreting the whole
- argument as user name, but the detection was flawed and checked for '0'
- instead of '\0', thus merely preventing group names beginning with a zero.
- </para>
- </listitem>
- <listitem>
- <para>
- In html_code_map[], use a numeric character reference instead of '
- which wasn't standardized before XHTML 1.0.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix an invalid free when compiled with FEATURE_GRACEFUL_TERMINATION
- and shut down through http://config.privoxy.org/die
- </para>
- </listitem>
- <listitem>
- <para>
- In get_actions(), fix the "temporary" backwards compatibility hack
- to accept block actions without reason.
- It also covered other actions that should be rejected as invalid.
- Reported by Billy Crook.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- General improvements:
- <itemizedlist>
- <listitem>
- <para>
- Privoxy can (re)compress buffered content before delivering
- it to the client. Disabled by default as most users wouldn't
- benefit from it.
- </para>
- </listitem>
- <listitem>
- <para>
- The +fast-redirects{check-decoded-url} action checks URL
- segments separately. If there are other parameters behind
- the redirect URL, this makes it unnecessary to cut them off
- by additionally using a +redirect{} pcrs command.
- Initial patch submitted by Jamie Zawinski in #3429848.
- </para>
- </listitem>
- <listitem>
- <para>
- When loading action sections, verify that the referenced filters
- exist. Currently missing filters only result in an error message,
- but eventually the severity will be upgraded to fatal.
- </para>
- </listitem>
- <listitem>
- <para>
- Allow to bind to multiple separate addresses.
- Patch set submitted by Petr Pisar in #3354485.
- </para>
- </listitem>
- <listitem>
- <para>
- Set socket_error to errno if connecting fails in rfc2553_connect_to().
- Previously rejected direct connections could be incorrectly reported
- as DNS issues if Privoxy was compiled with IPv6 support.
- </para>
- </listitem>
- <listitem>
- <para>
- Adjust url_code_map[] so spaces are replaced with %20 instead of '+'
- While '+' can be used by client's submitting form data, this is not
- actually what Privoxy is using the lookups for. This is more of a
- cosmetic issue and doesn't fix any known problems.
- </para>
- </listitem>
- <listitem>
- <para>
- When compiled without FEATURE_FAST_REDIRECTS, do not silently
- ignore +fast-redirect{} directives
- </para>
- </listitem>
- <listitem>
- <para>
- Added a workaround for GNU libc's strptime() reporting negative
- year values when the parsed year is only specified with two digits.
- On affected systems cookies with such a date would not be turned
- into session cookies by the +session-cookies-only action.
- Reported by Vaeinoe in #3403560
- </para>
- </listitem>
- <listitem>
- <para>
- Fixed bind failures with certain GNU libc versions if no non-loopback
- IP address has been configured on the system. This is mainly an issue
- if the system is using DHCP and Privoxy is started before the network
- is completely configured.
- Reported by Raphael Marichez in #3349356.
- Additional insight from Petr Pisar.
- </para>
- </listitem>
- <listitem>
- <para>
- Privoxy log messages now use the ISO 8601 date format %Y-%m-%d.
- It's only slightly longer than the old format, but contains
- the full date including the year and allows sorting by date
- (when grepping in multiple log files) without hassle.
- </para>
- </listitem>
- <listitem>
- <para>
- In get_last_url(), do not bother trying to decode URLs that do
- not contain at least one '%' sign. It reduces the log noise and
- a number of unnecessary memory allocations.
- </para>
- </listitem>
- <listitem>
- <para>
- In case of SOCKS5 failures, dump the socks response in the log message.
- </para>
- </listitem>
- <listitem>
- <para>
- Simplify the signal setup in main().
- </para>
- </listitem>
- <listitem>
- <para>
- Streamline socks5_connect() slightly.
- </para>
- </listitem>
- <listitem>
- <para>
- In socks5_connect(), require a complete socks response from the server.
- Previously Privoxy didn't care how much data the server response
- contained as long as the first two bytes contained the expected
- values. While at it, shrink the buffer size so Privoxy can't read
- more than a whole socks response.
- </para>
- </listitem>
- <listitem>
- <para>
- In chat(), do not bother to generate a client request in case of
- direct CONNECT requests. It will not be used anyway.
- </para>
- </listitem>
- <listitem>
- <para>
- Reduce server_last_modified()'s stack size.
- </para>
- </listitem>
- <listitem>
- <para>
- Shorten get_http_time() by using strftime().
- </para>
- </listitem>
- <listitem>
- <para>
- Constify the known_http_methods pointers in unknown_method().
- </para>
- </listitem>
- <listitem>
- <para>
- Constify the time_formats pointers in parse_header_time().
- </para>
- </listitem>
- <listitem>
- <para>
- Constify the formerly_valid_actions pointers in action_used_to_be_valid().
- </para>
- </listitem>
- <listitem>
- <para>
- Introduce a GNUMakefile MAN_PAGE variable that defaults to privoxy.1.
- The Debian package uses section 8 for the man page and this
- should simplify the patch.
- </para>
- </listitem>
- <listitem>
- <para>
- Deduplicate the INADDR_NONE definition for Solaris by moving it to jbsockets.h
- </para>
- </listitem>
- <listitem>
- <para>
- In block_url(), ditch the obsolete workaround for ancient Netscape versions
- that supposedly couldn't properly deal with status code 403.
- </para>
- </listitem>
- <listitem>
- <para>
- Remove a useless NULL pointer check in load_trustfile().
- </para>
- </listitem>
- <listitem>
- <para>
- Remove two useless NULL pointer checks in load_one_re_filterfile().
- </para>
- </listitem>
- <listitem>
- <para>
- Change url_code_map[] from an array of pointers to an array of arrays
- It removes an unnecessary layer of indirection and on 64bit system reduces
- the size of the binary a bit.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix various typos. Fixes taken from Debian's 29_typos.dpatch by Roland Rosenfeld.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a dok-tidy GNUMakefile target to clean up the messy HTML
- generated by the other dok targets.
- </para>
- </listitem>
- <listitem>
- <para>
- GNUisms in the GNUMakefile have been removed.
- </para>
- </listitem>
- <listitem>
- <para>
- Change the HTTP version in static responses to 1.1
- </para>
- </listitem>
- <listitem>
- <para>
- Synced config.sub and config.guess with upstream
- 2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a dedicated function to parse the values of toggles. Reduces duplicated
- code in load_config() and provides better error handling. Invalid or missing
- toggle values are now a fatal error instead of being silently ignored.
- </para>
- </listitem>
- <listitem>
- <para>
- Terminate HTML lines in static error messages with \n instead of \r\n.
- </para>
- </listitem>
- <listitem>
- <para>
- Simplify cgi_error_unknown() a bit.
- </para>
- </listitem>
- <listitem>
- <para>
- In LogPutString(), don't bother looking at pszText when not
- actually logging anything.
- </para>
- </listitem>
- <listitem>
- <para>
- Change ssplit()'s fourth parameter from int to size_t.
- Fixes a clang complaint.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a warning that the statistics currently can't be trusted.
- Mention Privoxy-Log-Parser's --statistics option as
- an alternative for the time being.
- </para>
- </listitem>
- <listitem>
- <para>
- In rfc2553_connect_to(), start setting cgi->error_message on error.
- </para>
- </listitem>
- <listitem>
- <para>
- Change the expected status code returned for http://p.p/die depending
- on whether or not FEATURE_GRACEFUL_TERMINATION is available.
- </para>
- </listitem>
- <listitem>
- <para>
- In cgi_die(), mark the client connection for closing.
- If the client will fetch the style sheet through another connection
- it gets the main thread out of the accept() state and should thus
- trigger the actual shutdown.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a proper CGI message for cgi_die().
- </para>
- </listitem>
- <listitem>
- <para>
- Don't enforce a logical line length limit in read_config_line().
- </para>
- </listitem>
- <listitem>
- <para>
- Slightly refactor server_last_modified() to remove useless gmtime*() calls.
- </para>
- </listitem>
- <listitem>
- <para>
- In get_content_type(), also recognize '.jpeg' as JPEG extension.
- </para>
- </listitem>
- <listitem>
- <para>
- Add '.png' to the list of recognized file extensions in get_content_type().
- </para>
- </listitem>
- <listitem>
- <para>
- In block_url(), consistently use the block reason "Request blocked by Privoxy"
- In two places the reason was "Request for blocked URL" which hides the
- fact that the request got blocked by Privoxy and isn't necessarily
- correct as the block may be due to tags.
- </para>
- </listitem>
- <listitem>
- <para>
- In listen_loop(), reload the configuration files after accepting
- a new connection instead of before.
- Previously the first connection that arrived after a configuration
- change would still be handled with the old configuration.
- </para>
- </listitem>
- <listitem>
- <para>
- In chat()'s receive-data loop, skip a client socket check if
- the socket will be written to right away anyway. This can
- increase the transfer speed for unfiltered content on fast
- network connections.
- </para>
- </listitem>
- <listitem>
- <para>
- The socket timeout is used for SOCKS negotiations as well which
- previously couldn't timeout.
- </para>
- </listitem>
- <listitem>
- <para>
- Don't keep the client connection alive if any configuration file
- changed since the time the connection came in. This is closer to
- Privoxy's behaviour before keep-alive support for client connection
- has been added and also less confusing in general.
- </para>
- </listitem>
- <listitem>
- <para>
- Treat all Content-Type header values containing the pattern
- 'script' as a sign of text. Reported by pribog in #3134970.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Action file improvements:
- <itemizedlist>
- <listitem>
- <para>
- Moved the site-specific block pattern section below the one for the
- generic patterns so for requests that are matched in both, the block
- reason for the domain is shown which is usually more useful than showing
- the one for the generic pattern.
- </para>
- </listitem>
- <listitem>
- <para>
- Remove -prevent-compression from the fragile alias. It's no longer
- used anywhere by default and isn't known to break stuff anyway.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a (disabled) section to block various Facebook tracking URLs.
- Reported by Dan Stahlke in #3421764.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a (disabled) section to rewrite and redirect click-tracking
- URLs used on news.google.com.
- Reported by Dan Stahlke in #3421755.
- </para>
- </listitem>
- <listitem>
- <para>
- Unblock linuxcounter.net/.
- Reported by Dan Stahlke in #3422612.
- </para>
- </listitem>
- <listitem>
- <para>
- Block 'www91.intel.com/' which is used by Omniture.
- Reported by Adam Piggott in #3167370.
- </para>
- </listitem>
- <listitem>
- <para>
- Disable the handle-as-empty-doc-returns-ok option and mark it as deprecated.
- Reminded by tceverling in #2790091.
- </para>
- </listitem>
- <listitem>
- <para>
- Add ".ivwbox.de/" to the "Cross-site user tracking" section.
- Reported by Nettozahler in #3172525.
- </para>
- </listitem>
- <listitem>
- <para>
- Unblock and fast-redirect ".awin1.com/.*=http://".
- Reported by Adam Piggott in #3170921.
- </para>
- </listitem>
- <listitem>
- <para>
- Block "b.collective-media.net/".
- </para>
- </listitem>
- <listitem>
- <para>
- Widen the Debian popcon exception to "qa.debian.org/popcon".
- Seen in Debian's 05_default_action.dpatch by Roland Rosenfeld.
- </para>
- </listitem>
- <listitem>
- <para>
- Block ".gemius.pl/" which only seems to be used for user tracking.
- Reported by johnd16 in #3002731. Additional input from Lee and movax.
- </para>
- </listitem>
- <listitem>
- <para>
- Disable banners-by-size filters for '.thinkgeek.com/'.
- The filter only seems to catch pictures of the inventory.
- </para>
- </listitem>
- <listitem>
- <para>
- Block requests for 'go.idmnet.bbelements.com/please/showit/'.
- Reported by kacperdominik in #3372959.
- </para>
- </listitem>
- <listitem>
- <para>
- Unblock adainitiative.org/.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a fast-redirects exception for '.googleusercontent.com/.*=cache'.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a fast-redirects exception for webcache.googleusercontent.com/.
- </para>
- </listitem>
- <listitem>
- <para>
- Unblock http://adassier.wordpress.com/ and http://adassier.files.wordpress.com/.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Filter file improvements:
- <itemizedlist>
- <listitem>
- <para>
- Let the yahoo filter hide '.ads'.
- </para>
- </listitem>
- <listitem>
- <para>
- Let the msn filter hide overlay ads for Facebook 'likes' in search
- results and elements with the id 's_notf_div'. They only seem to be
- used to advertise site 'enhancements'.
- </para>
- </listitem>
- <listitem>
- <para>
- Let the js-events filter additionally disarm setInterval().
- Suggested by dg1727 in #3423775.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Documentation improvements:
- <itemizedlist>
- <listitem>
- <para>
- Clarify the effect of compiling Privoxy with zlib support.
- Suggested by dg1727 in #3423782.
- </para>
- </listitem>
- <listitem>
- <para>
- Point out that the SourceForge messaging system works like a black
- hole and should thus not be used to contact individual developers.
- </para>
- </listitem>
- <listitem>
- <para>
- Mention some of the problems one can experience when not explicitly
- configuring an IP addresses as listen address.
- </para>
- </listitem>
- <listitem>
- <para>
- Explicitly mention that hostnames can be used instead of IP addresses
- for the listen-address, that only the first address returned will be
- used and what happens if the address is invalid.
- Requested by Calestyo in #3302213.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Log message improvements:
- <itemizedlist>
- <listitem>
- <para>
- If only the server connection is kept alive, do not pretend to
- wait for a new client request.
- </para>
- </listitem>
- <listitem>
- <para>
- Remove a superfluous log message in forget_connection().
- </para>
- </listitem>
- <listitem>
- <para>
- In chat(), properly report missing server responses as such
- instead of calling them empty.
- </para>
- </listitem>
- <listitem>
- <para>
- In forwarded_connect(), fix a log message nobody should ever see.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix a log message in socks5_connect(), a failed write operation
- was logged as failed read operation.
- </para>
- </listitem>
- <listitem>
- <para>
- Let load_one_actions_file() properly complain about a missing
- '{' at the beginning of the file.
- Simply stating that a line is invalid isn't particularly helpful.
- </para>
- </listitem>
- <listitem>
- <para>
- Do not claim to listen on a socket until Privoxy actually does.
- Patch submitted by Petr Pisar #3354485
- </para>
- </listitem>
- <listitem>
- <para>
- Prevent a duplicated LOG_LEVEL_CLF message when sending out
- the "no-server-data" response.
- </para>
- </listitem>
- <listitem>
- <para>
- Also log the client socket when dropping a connection.
- </para>
- </listitem>
- <listitem>
- <para>
- Include the destination host in the 'Request ... marked for
- blocking. limit-connect{...} doesn't allow CONNECT ...' message
- Patch submitted by Saperski in #3296250.
- </para>
- </listitem>
- <listitem>
- <para>
- Prevent a duplicated log message if none of the resolved IP
- addresses were reachable.
- </para>
- </listitem>
- <listitem>
- <para>
- In connect_to(), do not pretend to retry if forwarded-connect-retries
- is zero or unset.
- </para>
- </listitem>
- <listitem>
- <para>
- When a specified user or group can't be found, put the name in
- single-quotes when logging it.
- </para>
- </listitem>
- <listitem>
- <para>
- In rfc2553_connect_to(), explain getnameinfo() errors better.
- </para>
- </listitem>
- <listitem>
- <para>
- Remove a useless log message in chat().
- </para>
- </listitem>
- <listitem>
- <para>
- When retrying to connect, also log the maximum number of connection
- attempts.
- </para>
- </listitem>
- <listitem>
- <para>
- Rephrase a log message in compile_dynamic_pcrs_job_list().
- Divide the error code and its meaning with a colon. Call the pcrs
- job dynamic and not the filter. Filters may contain dynamic and
- non-dynamic pcrs jobs at the same time. Only mention the name of
- the filter or tagger, but don't claim it's a filter when it could
- be a tagger.
- </para>
- </listitem>
- <listitem>
- <para>
- In a fatal error message in load_one_actions_file(), cover both
- URL and TAG patterns.
- </para>
- </listitem>
- <listitem>
- <para>
- In pcrs_strerror(), properly report unknown positive error code
- values as such. Previously they were handled like 0 (no error).
- </para>
- </listitem>
- <listitem>
- <para>
- In compile_dynamic_pcrs_job_list(), also log the actual error code as
- pcrs_strerror() doesn't handle all errors reported by pcre.
- </para>
- </listitem>
- <listitem>
- <para>
- Don't bother trying to continue chatting if the client didn't ask for it.
- Reduces log noise a bit.
- </para>
- </listitem>
- <listitem>
- <para>
- Make two fatal error message in load_one_actions_file() more descriptive.
- </para>
- </listitem>
- <listitem>
- <para>
- In cgi_send_user_manual(), log when rejecting a file name due to '/' or '..'.
- </para>
- </listitem>
- <listitem>
- <para>
- In load_file(), log a message if opening a file failed.
- The CGI error message alone isn't too helpful.
- </para>
- </listitem>
- <listitem>
- <para>
- In connection_destination_matches(), improve two log messages
- to help understand why the destinations don't match.
- </para>
- </listitem>
- <listitem>
- <para>
- Rephrase a log message in serve(). Client request arrival
- should be differentiated from closed client connections now.
- </para>
- </listitem>
- <listitem>
- <para>
- In serve(), log if a client connection isn't reused due to a
- configuration file change.
- </para>
- </listitem>
- <listitem>
- <para>
- Let mark_server_socket_tainted() always mark the server socket tainted,
- just don't talk about it in cases where it has no effect. It doesn't change
- Privoxy's behaviour, but makes understanding the log file easier.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- configure:
- <itemizedlist>
- <listitem>
- <para>
- Added a --disable-ipv6-support switch for platforms where support
- is detected but doesn't actually work.
- </para>
- </listitem>
- <listitem>
- <para>
- Do not check for the existence of strerror() and memmove() twice
- </para>
- </listitem>
- <listitem>
- <para>
- Remove a useless test for setpgrp(2). Privoxy doesn't need it and
- it can cause problems when cross-compiling.
- </para>
- </listitem>
- <listitem>
- <para>
- Rename the --disable-acl-files switch to --disable-acl-support.
- Since about 2001, ACL directives are specified in the standard
- config file.
- </para>
- </listitem>
- <listitem>
- <para>
- Update the URL of the 'Removing outdated PCRE version after the
- next stable release' posting. The old URL stopped working after
- one of SF's recent site "optimizations". Reported by Han Liu.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Privoxy-Regression-Test:
- <itemizedlist>
- <listitem>
- <para>
- Added --shuffle-tests option to increase the chances of detection race conditions.
- </para>
- </listitem>
- <listitem>
- <para>
- Added a --local-test-file option that allows to use Privoxy-Regression-Test without Privoxy.
- </para>
- </listitem>
- <listitem>
- <para>
- Added tests for missing socks4 and socks4a forwarders.
- </para>
- </listitem>
- <listitem>
- <para>
- The --privoxy-address option now works with IPv6 addresses containing brackets, too.
- </para>
- </listitem>
- <listitem>
- <para>
- Perform limited sanity checks for parameters that are supposed to have numerical values.
- </para>
- </listitem>
- <listitem>
- <para>
- Added a --sleep-time option to specify a number of seconds to
- sleep between tests, defaults to 0.
- </para>
- </listitem>
- <listitem>
- <para>
- Disable the range-requests tagger for tests that break if it's enabled.
- </para>
- </listitem>
- <listitem>
- <para>
- Log messages use the ISO 8601 date format %Y-%m-%d.
- </para>
- </listitem>
- <listitem>
- <para>
- Fix spelling in two error messages.
- </para>
- </listitem>
- <listitem>
- <para>
- In the --help output, include a list of supported tests and their default levels.
- </para>
- </listitem>
- <listitem>
- <para>
- Adjust the tests to properly deal with FEATURE_TOGGLE being disabled.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- Privoxy-Log-Parser:
- <itemizedlist>
- <listitem>
- <para>
- Perform limited sanity checks for command line parameters that
- are supposed to have numerical values.
- </para>
- </listitem>
- <listitem>
- <para>
- Implement a --unbreak-lines-only option to try to revert MUA breakage.
- </para>
- </listitem>
- <listitem>
- <para>
- Accept and highlight: Added header: Content-Encoding: deflate
- </para>
- </listitem>
- <listitem>
- <para>
- Accept and highlight: Compressed content from 29258 to 8630 bytes.
- </para>
- </listitem>
- <listitem>
- <para>
- Accept and highlight: Client request arrived in time on socket 21.
- </para>
- </listitem>
- <listitem>
- <para>
- Highlight: Didn't receive data in time: a.fsdn.com:443
- </para>
- </listitem>
- <listitem>
- <para>
- Accept log messages with ISO 8601 time stamps, too.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
- <para>
- uagen:
- <itemizedlist>
- <listitem>
- <para>
- Bump generated Firefox version to 8.0.
- </para>
- </listitem>
- <listitem>
- <para>
- Only randomize the release date if the new --randomize-release-date
- option is enabled. Firefox versions after 4 use a fixed date string
- without meaning.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- </itemizedlist>
+<sect3 id="installation-pack-win"><title>Windows</title>
+
+<para>
+ Just double-click the installer, which will guide you through
+ the installation process. You will find the configuration files
+ in the same directory as you installed <application>Privoxy</application> in.
+</para>
+<para>
+ Version 3.0.5 beta introduced full <application>Windows</application> service
+ functionality. On Windows only, the <application>Privoxy</application>
+ program has two new command line arguments to install and uninstall
+ <application>Privoxy</application> as a <emphasis>service</emphasis>.
+</para>
+ <variablelist>
+ <varlistentry>
+ <term>Arguments:</term>
+ <listitem>
+ <para>
+ <replaceable class="parameter">--install</replaceable>[:<replaceable class="parameter">service_name</replaceable>]
+ </para>
+ <para>
+ <replaceable class="parameter">--uninstall</replaceable>[:<replaceable class="parameter">service_name</replaceable>]
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ After invoking <application>Privoxy</application> with
+ <command>--install</command>, you will need to bring up the
+ <application>Windows</application> service console to assign the user you
+ want <application>Privoxy</application> to run under, and whether or not you
+ want it to run whenever the system starts. You can start the
+ <application>Windows</application> services console with the following
+ command: <command>services.msc</command>. If you do not take the manual step
+ of modifying <application>Privoxy's</application> service settings, it will
+ not start. Note too that you will need to give Privoxy a user account that
+ actually exists, or it will not be permitted to
+ write to its log and configuration files.
+</para>
+
+</sect3>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect3 id="installation-os2"><title>OS/2</title>
+
+<para>
+ First, make sure that no previous installations of
+ <application>Junkbuster</application> and / or
+ <application>Privoxy</application> are left on your
+ system. Check that no <application>Junkbuster</application>
+ or <application>Privoxy</application> objects are in
+ your startup folder.
+
+</para>
+
+<para>
+ Then, just double-click the WarpIN self-installing archive, which will
+ guide you through the installation process. A shadow of the
+ <application>Privoxy</application> executable will be placed in your
+ startup folder so it will start automatically whenever OS/2 starts.
+</para>
+
+<para>
+ The directory you choose to install <application>Privoxy</application>
+ into will contain all of the configuration files.
+</para>
+</sect3>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect3 id="installation-mac"><title>Mac OS X</title>
+<para>
+ Installation instructions for the OS X platform depend upon whether
+ you downloaded a ready-built installation package (.pkg or .mpkg) or have
+ downloaded the source code.
+</para>
+</sect3>
+<sect3 renderas="sect4" id="OS-X-install-from-package">
+<title>Installation from ready-built package</title>
+<para>
+ The downloaded file will either be a .pkg (for OS X 10.5 upwards) or a bzipped
+ .mpkg file (for OS X 10.4). The former can be double-clicked as is and the
+ installation will start; double-clicking the latter will unzip the .mpkg file
+ which can then be double-clicked to commence the installation.
+</para>
+<para>
+ The privoxy service will automatically start after a successful installation
+ (and thereafter every time your computer starts up) however you will need to
+ configure your web browser(s) to use it. To do so, configure them to use a
+ proxy for HTTP and HTTPS at the address 127.0.0.1:8118.
+</para>
+<para>
+ To prevent the privoxy service from automatically starting when your computer
+ starts up, remove or rename the file <literal>/Library/LaunchDaemons/org.ijbswa.privoxy.plist</literal>
+ (on OS X 10.5 and higher) or the folder named
+ <literal>/Library/StartupItems/Privoxy</literal> (on OS X 10.4 'Tiger').
+</para>
+<para>
+ To manually start or stop the privoxy service, use the scripts startPrivoxy.sh
+ and stopPrivoxy.sh supplied in /Applications/Privoxy. They must be run from an
+ administrator account, using sudo.
+</para>
+<para>
+ To uninstall, run /Applications/Privoxy/uninstall.command as sudo from an
+ administrator account.
+</para>
+</sect3>
+<sect3 renderas="sect4" id="OS-X-install-from-source">
+<title>Installation from source</title>
+<para>
+ To build and install the Privoxy source code on OS X you will need to obtain
+ the macsetup module from the Privoxy Sourceforge CVS repository (refer to
+ Sourceforge help for details of how to set up a CVS client to have read-only
+ access to the repository). This module contains scripts that leverage the usual
+ open-source tools (available as part of Apple's free of charge Xcode
+ distribution or via the usual open-source software package managers for OS X
+ (MacPorts, Homebrew, Fink etc.) to build and then install the privoxy binary
+ and associated files. The macsetup module's README file contains complete
+ instructions for its use.
+</para>
+<para>
+ The privoxy service will automatically start after a successful installation
+ (and thereafter every time your computer starts up) however you will need to
+ configure your web browser(s) to use it. To do so, configure them to use a
+ proxy for HTTP and HTTPS at the address 127.0.0.1:8118.
+</para>
+<para>
+ To prevent the privoxy service from automatically starting when your computer
+ starts up, remove or rename the file <literal>/Library/LaunchDaemons/org.ijbswa.privoxy.plist</literal>
+ (on OS X 10.5 and higher) or the folder named
+ <literal>/Library/StartupItems/Privoxy</literal> (on OS X 10.4 'Tiger').
+</para>
+<para>
+ To manually start or stop the privoxy service, use the Privoxy Utility
+ for Mac OS X (also part of the macsetup module). This application can start
+ and stop the privoxy service and display its log and configuration files.
+</para>
+<para>
+ To uninstall, run the macsetup module's uninstall.sh as sudo from an
+ administrator account.
+</para>
+</sect3>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect3 id="installation-tbz"><title>FreeBSD</title>
+
+<para>
+ Privoxy is part of FreeBSD's Ports Collection, you can build and install
+ it with <literal>cd /usr/ports/www/privoxy; make install clean</literal>.
+</para>
+<para>
+ If you don't use the ports, you can fetch and install
+ the package with <literal>pkg_add -r privoxy</literal>.
+</para>
+<para>
+ The port skeleton and the package can also be downloaded from the
+ <ulink url="https://sourceforge.net/project/showfiles.php?group_id=11118">File Release
+ Page</ulink>, but there's no reason to use them unless you're interested in the
+ beta releases which are only available there.
+</para>
+</sect3>
+
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="installation-source"><title>Building from Source</title>
+
+<para>
+ The most convenient way to obtain the <application>Privoxy</application> sources
+ is to download the source tarball from our
+ <ulink url="http://sourceforge.net/project/showfiles.php?group_id=11118&package_id=10571">project download
+ page</ulink>.
+</para>
+
+<para>
+ If you like to live on the bleeding edge and are not afraid of using
+ possibly unstable development versions, you can check out the up-to-the-minute
+ version directly from <ulink url="http://sourceforge.net/cvs/?group_id=11118">the
+ CVS repository</ulink>.
+<!--
+ deprecated...out of business.
+ or simply download <ulink
+ url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.bz2">the nightly CVS
+ tarball.</ulink>
+-->
+</para>
+
+<!-- include buildsource.sgml boilerplate: -->
+&buildsource;
+<!-- end boilerplate -->
+
+</sect2>
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="installation-keepupdated"><title>Keeping your Installation Up-to-Date</title>
+
+<para>
+ If you wish to receive an email notification whenever we release updates of
+ <application>Privoxy</application> or the actions file, <ulink
+ url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
+ to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
+</para>
+
+<para>
+ In order not to lose your personal changes and adjustments when updating
+ to the latest <literal>default.action</literal> file we <emphasis>strongly
+ recommend</emphasis> that you use <literal>user.action</literal> and
+ <literal>user.filter</literal> for your local
+ customizations of <application>Privoxy</application>. See the <link
+ linkend="actions-file">Chapter on actions files</link> for details.
</para>
+</sect2>
+
+
+</sect1>
+
+<!-- ~ End section ~ -->
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect1 id="whatsnew">
+<title>What's New in this Release</title>
+
+&changelog;
<!-- ~~~~~ New section ~~~~~ -->
files, thinking you will want to do that yourself.
</para>
</listitem>
- <listitem>
- <para>
- <filename>standard.action</filename> has been merged into
- the <filename>default.action</filename> file.
- </para>
- </listitem>
<listitem>
<para>
In the default configuration only fatal errors are logged now.
directory. Except on Win32 where it will try <filename>config.txt</filename>.
</para>
-<sect2 id="start-redhat">
-<title>Red Hat and Fedora</title>
-<para>
- A default Red Hat installation may not start &my-app; upon boot. It will use
- the file <filename>/etc/privoxy/config</filename> as its main configuration
- file.
-</para>
-<para>
- <screen>
- # /etc/rc.d/init.d/privoxy start
-</screen>
-</para>
-<para>
- Or ...
-</para>
-<para>
- <screen>
- # service privoxy start
-</screen>
-</para>
-</sect2>
-
<sect2 id="start-debian">
<title>Debian</title>
<para>
</sect2>
-<sect2 id="start-amigaos">
-<title>AmigaOS</title>
-<para>
- Start <application>Privoxy</application> (with RUN <>NIL:) in your
- <filename>startnet</filename> script (AmiTCP), in
- <filename>s:user-startup</filename> (RoadShow), as startup program in your
- startup script (Genesis), or as startup action (Miami and MiamiDx).
- <application>Privoxy</application> will automatically quit when you quit your
- TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
- <application>Privoxy</application> is still running).
-</para>
-</sect2>
-
-<sect2 id="start-gentoo">
-<title>Gentoo</title>
-<para>
- A script is again used. It will use the file <filename>/etc/privoxy/config
- </filename> as its main configuration file.
-</para>
-<para>
- <screen>
- /etc/init.d/privoxy start
- </screen>
-</para>
-<para>
- Note that <application>Privoxy</application> is not automatically started at
- boot time by default. You can change this with the <literal>rc-update</literal>
- command.
-</para>
-<para>
- <screen>
- rc-update add privoxy default
- </screen>
-</para>
-</sect2>
-
<!--
<para>
projects / privoxy.git / blobdiff