NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ ">

2. Installation

Privoxy is available both in convenient pre-compiled packages for a wide range of operating systems, and as raw source code. For most users, we recommend using the packages, which can be downloaded from our Privoxy Project Page.

Note: If you have a previous Junkbuster or Privoxy installation on your system, you will need to remove it. On some platforms, this may be done for you as part of their installation procedure. (See below for your platform). In any case be sure to backup your old configuration if it is valuable to you. See the note to upgraders section below.

2.1. Binary Packages

How to install the binary packages depends on your operating system:

2.2. Building from Source

The most convenient way to obtain the Privoxy sources is to download the source tarball from our project page.

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 the CVS repository or simply download the nightly CVS tarball.

To build Privoxy from source, autoconf, GNU make (gmake), and, of course, a C compiler like gcc are required.

When building from a source tarball (either release version or nightly CVS tarball), first unpack the source:

 tar xzvf privoxy-3.0.0-src* [.tgz or .tar.gz]
 cd privoxy-3.0.0

For retrieving the current CVS sources, you'll need CVS installed. Note that sources from CVS are development quality, and may not be stable, or well tested. To download CVS source:

  cvs login
  cvs -z3 co current
  cd current

This will create a directory named current/, which will contain the source tree.

Then, in either case, to build from unpacked tarball or CVS source:

 ./configure      # (--help to see options)
 make             # (the make from gnu, gmake for *BSD) 
 make -n install  # (to see where all the files will go)
 make install     # (to really install)


The "make install" target is temporary quite broken! It is recommended to use a binary package, or do a source build, and manually install the components. Sorry.

If you have gnu make, you can have the first four steps automatically done for you by just typing:


in the freshly downloaded or unpacked source directory.

For more detailed instructions on how to build Redhat and SuSE RPMs, Windows self-extracting installers, building on platforms with special requirements etc, please consult the developer manual.

2.3. Keeping your Installation Up-to-Date

As user feedback comes in and development continues, we will make updated versions of both the main actions file (as a separate package) and the software itself (including the actions file) available for download.

If you wish to receive an email notification whenever we release updates of Privoxy or the actions file, subscribe to our announce mailing list,

In order not to loose your personal changes and adjustments when updating to the latest default.action file we strongly recommend that you use user.action for your customization of Privoxy. See the Chapter on actions files for details.