.
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.
How to install the binary packages depends on your operating system:
RPMs can be installed with rpm -Uvh privoxy-3.1.1-1.rpmrpm -Uvh privoxy-3.0.7-1.rpm, and will use 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-3.1.1-1.src.rpmrpm --rebuild privoxy-3.0.7-1.src.rpm. This will use your locally installed libraries and RPM version.
Junkbuster - automatically, before installing Privoxy.
DEBs can be installed with dpkg -i - privoxy_3.1.1-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.
--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.
Create a new directory, 2.1.5. OS/2
2.1.5. OS/2
First, make sure that no previous installations of
Unzip the downloaded file (you can either double-click on the file
from the finder, or from the desktop if you downloaded it there).
@@ -324,7 +423,9 @@ CLASS="SECT3"
> Copy and then unpack the 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.6. Mac OSX
2.1.6. Mac OSX2.1.7. AmigaOS
2.1.7. AmigaOS2.1.8. Gentoo
2.1.8. FreeBSD
Gentoo source packages (Ebuilds) for , the
documentation is in /usr/share/doc/privoxy-3.1.1/usr/share/doc/privoxy-3.0.7
and the Log directory is in The most convenient way to obtain the Privoxy sources
- is to download the source tarball from our project
+>project download
page. the
CVS repository or simply download the nightly CVS
- tarball.2.2. Building from Source
2.2. Building from Source
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:
tar xzvf privoxy-3.1.1-beta-src* [.tgz or .tar.gz] - cd privoxy-3.1.1-betatar xzvf privoxy-3.0.7-beta-src* [.tgz or .tar.gz] + cd privoxy-3.0.7-beta |
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:
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 | , which will
contain the source tree.
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:
Warningmake |
in the freshly downloaded or unpacked source directory.
- The To build an executable with security enhanced features so that + users cannot easily bypass the proxy (e.g. "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. -
"Go There Anyway"), or + alter their own configurations, configure like this:
./configure --disable-toggle --disable-editor --disable-force |
If you have gnu make, you can have the first four steps - automatically done for you by just typing:
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:
makemake -s install USER=privoxy GROUP=privoxy |
in the freshly downloaded or unpacked source directory.
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.
For more detailed instructions on how to build Redhat and SuSE RPMs, +> 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, default.filter, and + standard.action 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 2.3. Keeping your Installation Up-to-Date
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 , ijbswa-announce@lists.sourceforge.net.
In order not to loose your personal changes and adjustments when updating +> In order not to lose your personal changes and adjustments when updating to the latest default.action that you use user.action for your - customization of and + user.filter for your local + customizations of Privoxy. See the NextNote to UpgradersWhat's New in this Release