Installation

Privoxy 3.0.12 User Manual.

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 - Note: + On some platforms, the installer may remove previously installed versions, if + found. (See below for your platform). In any case be sure to backup your old configuration if it is valuable to - you.be sure to backup + your old configuration if it is valuable to you. See the note to - upgradersnote to upgraders section below.

2.1.1. Red Hat, SuSE RPMs and Conectiva2.1.1. Red Hat and Fedora RPMs

RPMs can be installed with rpm -Uvh privoxy-2.9.15-1.rpmrpm -Uvh privoxy-3.0.12-1.rpm, and will use Privoxy will - not be automatically started on system boot. You will need to enable that using ntsysv, or similar methods. Note that SuSE will -automatically start Privoxy in the boot process.

, or similar methods. If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-2.9.15-1.src.rpm;rpm --rebuild privoxy-3.0.12-1.src.rpm. This will use your locally installed libraries and RPM version.
Junkbuster - automatically, before installing Privoxy.
2.1.2. Debian2.1.2. Debian and Ubuntu
DEBs can be installed with dpkg -i - privoxy_2.9.15-1.deb, and will use - apt-get install privoxy, + and will use /etc/privoxy for the location of configuration - files.
for the location of + configuration files.

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 Privoxy in. We do not - use the registry of Windows.

Privoxy in.
Version 3.0.5 beta introduced full Windows service + functionality. On Windows only, the Privoxy + program has two new command line arguments to install and uninstall + Privoxy as a service.
Arguments:
--install[:service_name] +
--uninstall[:service_name] +
After invoking Privoxy with + --install, you will need to bring up the + Windows service console to assign the user you + want Privoxy to run under, and whether or not you + want it to run whenever the system starts. You can start the + Windows services console with the following + command: services.msc. If you do not take the manual step + of modifying Privoxy's 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.

2.1.4. Solaris, NetBSD, FreeBSD, HP-UX2.1.4. Solaris
Create a new directory, cd to it, then unzip and untar the archive. For the most part, you'll have to figure out where - things go. FIXME.

Privoxy are left on your - system. You can do this by
Junkbuster + or Privoxy objects are in + your startup folder.
Then, just double-click the WarpIN self-installing archive, which will guide you through the installation process. A shadow of the @@ -263,30 +367,26 @@ CLASS="SECT3" CLASS="SECT3" >2.1.6. Max OSX2.1.6. Mac OS X
Unzip the downloaded package (you can either double-click on the file - in the finder, or on the desktop if you downloaded it there). Then, - double-click on the package installer icon and follow the installation - process. - Privoxy will be installed in the subdirectory - /Applications/Privoxy.app. - Privoxy will set itself up to start - automatically on system bring-up via +> Unzip the downloaded file (you can either double-click on the zip file + icon from the Finder, or from the desktop if you downloaded it there). + Then, double-click on the package installer icon and follow the + installation process.
The privoxy service will automatically start after a successful + installation (in addition to every time your computer starts up). To + prevent the privoxy service from automatically starting when your + computer starts up, remove or rename the folder named /System/Library/StartupItems/Privoxy.
/Library/StartupItems/Privoxy.
To manually start or stop the privoxy service, use the Privoxy Utility + for Mac OS X. This application controls the privoxy service (e.g. + starting and stopping the service as well as uninstalling the software).

directory, including all configuration and log files. To uninstall, just remove this directory.

2.1.8. FreeBSD

Start Privoxy is part of FreeBSD's Ports Collection, you can build and install + it with cd /usr/ports/www/privoxy; make install clean.

If you don't use the ports, you can fetch and install + the package with pkg_add -r privoxy.

The port skeleton and the package can also be downloaded from the + File Release + Page, but there's no reason to use them unless you're interested in the + beta releases which are only available there.

2.1.9. Gentoo

Gentoo source packages (Ebuilds) for Privoxy (with RUN <>NIL:) in your - startnet script (AmiTCP), in - s:user-startup (RoadShow), as startup program in your - startup script (Genesis), or as startup action (Miami and MiamiDx). +> 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 Privoxy will automatically quit when you quit your - TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that - Version is added to the Portage Tree).

Before installing Privoxy is still running).

under Gentoo just do + first emerge --sync to get the latest changes from the + Portage tree. With emerge privoxy you install the latest + version.
Configuration files are in /etc/privoxy, the + documentation is in /usr/share/doc/privoxy-3.0.12 + and the Log directory is in /var/log/privoxy.

Privoxy sources - is to download the source tarball from our project +>project download page.
the CVS repository or simply download the nightly CVS - tarball.
.
To build gcc are required.
When building from a source tarball (either release version or - nightly CVS - tarball), first unpack the source:
When building from a source tarball, + first unpack the source:

Privoxy User Manual
Prev	Next

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

tar xzvf privoxy-3.0.12-stable-src.tar.gz + cd privoxy-3.0.12-stable

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:

For retrieving the current CVS sources, you'll need a CVS client installed. + Note that sources from CVS are typically development quality, and may not be + stable, or well tested. To download CVS source, check the Sourceforge + documentation, which might give commands like:
, which will contain the source tree.
Then, in either case, to build from unpacked tarball or CVS source:
You can also check out any Privoxy + "branch", just exchange the current + name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs + tree).
It is also strongly recommended to not run Privoxy + as root. You should configure/install/run Privoxy as + an unprivileged user, preferably by creating a "privoxy" user + and group just for this purpose. See your local documentation for the correct + command line to do add new users and groups (something like + adduser, but the command syntax may vary from platform + to platform).
/etc/passwd might then look like:

cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current +> cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current cd current
privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell
And then /etc/group, like:

privoxy:*:7777:
Some binary packages may do this for you.
Then, to build from either unpacked tarball or CVS source:
autoheader autoconf ./configure # (--help to see options) - make # (the make from gnu, gmake for *BSD) - su + make # (the make from GNU, sometimes called gmake) + su # Possibly required make -n install # (to see where all the files will go) - make install # (to really install)
If you have gnu make, you can have the first four steps +> Using 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, +> To build an executable with security enhanced features so that + users cannot easily bypass the proxy (e.g. "Go There Anyway"), or + alter their own configurations, configure like this:

./configure --disable-toggle --disable-editor --disable-force
Then build as above. In Privoxy 3.0.7 and later, all of these options +can also be disabled through the configuration file.
WARNING: If installing as root, the install will fail + unless a non-root user or group is specified, or a privoxy + user and group already exist on the system. If a non-root user is specified, + and no group, then the installation will try to also use a group of the same name + as "user". If a group is specified (and no user), then the + support files will be installed as writable by that group, and owned by the + user running the installation.
configure accepts --with-user and + --with-group options for setting user and group ownership + of the configuration files (which need to be writable by the daemon). The + specified user must already exist. When starting + Privoxy, it must be run as this same user to + insure write access to configuration and log files!
Alternately, you can specify user and group + on the make command line, but be sure both already exist:

make -s install USER=privoxy GROUP=privoxy
The default installation path for make install is + /usr/local. This may of course be customized with + the various ./configure path options. If you are doing + an install to anywhere besides /usr/local, be + sure to set the appropriate paths with the correct configure options + (./configure --help). Non-privileged users must of course + have write access permissions to wherever the target installation is going.
If you do install to /usr/local, the install will use + sysconfdir=$prefix/etc/privoxy by default. All other + destinations, and the direct usage of --sysconfdir flag + behave like normal, i.e. will not add the extra privoxy + directory. This is for a safer install, as there may already exist another + program that uses a file with the "config" name, and thus makes + /usr/local/etc cleaner.
If installing to /usr/local, the documentation will go + by default to $prefix/share/doc. But if this directory + doesn't exist, it will then try $prefix/doc and install + there before creating a new $prefix/share/doc just for + Privoxy.
Again, if the installs goes to /usr/local, the + localstatedir (ie: var/) will default + to /var instead of $prefix/var so + the logs will go to /var/log/privoxy/, and the pid file + will be created in /var/run/privoxy.pid.
make install will attempt to set the correct values + in config (main configuration file). You should + check this to make sure all values are correct. If appropriate, + an init script will be installed, but it is up to the user to determine + how and where to start Privoxy. The init + script should be checked for correct paths and values, if anything other than + a default install is done.
If install finds previous versions of local configuration files, most of + these will not be overwritten, and the new ones will be installed with a + "new" extension. default.action and default.filter + will be overwritten. You will then need + to manually update the other installed configuration files as needed. The + default template files will be overwritten. If you have + customized, local templates, these should be stored safely in a separate + directory and defined in config by the + "templdir" directive. It is of course wise to always back-up any + important configuration files "just in case". If a previous + version of Privoxy is already running, you will + have to restart it manually.
For more detailed instructions on how to build Redhat RPMs, Windows self-extracting installers, building on platforms with special requirements etc, please consult the developer manual.

2.1.8. FreeBSD

2.1.9. Gentoo

2.3. Keeping your Installation Up-to-Date