| Privoxy User Manual | Privoxy 3.0.7 User Manual|
|---|---|
| Prev | Next |
/Library/Privoxy/StartPrivoxy.command + |
You will be prompted for the administrator password.
At present, Copy and then unpack the lha archive to a suitable location. + All necessary files will be installed into Privoxy is known to run on Win32, Mac - OSX, OS/2, AmigaOS, Linux (RedHat, Suse, Debian), FreeBSD, and many flavors - of Unix. There are source and binary releases for these available for - download at + directory, including all configuration and log files. To uninstall, just + remove this directory.
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 + http://sourceforge.net/project/showfiles.php?group_id=11118File Release + Page, but there's no reason to use them unless you're interested in the + beta releases which are only available there.
Gentoo source packages (Ebuilds) for Privoxy 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 Version is added to the Portage Tree).
Before installing Privoxy under Gentoo just do + first emerge rsync 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.7 + and the Log directory is in /var/log/privoxy.
There are several ways to install The most convenient way to obtain the Privoxy sources + is to download the source tarball from our + project download + 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.
To build Privoxy from source, - autoconf and GNU make (gmake) are required. Source is available as gzipped - tar archives. For this, first unpack the source:
autoconf, + GNU make + (gmake), and, of course, a C compiler like gcc are required.When building from a source tarball, + first unpack the source:
tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz] - cd privoxy-2.9.14-beta -tar 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 the CVS - package installed first. Note CVS source is 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 - cd 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 |
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:
autoheader - autoconf - ./configure (--help to see options) - make (the make from gnu, gmake for *BSD) - su - make -n install (to see where all the files will go) - make install (to really install) -privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell |
Redhat and SuSE src and binary RPMs can be built with - "make redhat-dist" or - "make suse-dist" from unpacked sources. You - will need to run "autoconf; autoheader; - ./configure" beforehand. *BSD will require gmake (from - http://www.gnu.org). -
For Redhat and SuSE Linux RPM packages, see below.
To build Redhat RPM packages from source, install source as above. Then:
And then /etc/group, like:
autoheader - autoconf - ./configure - make redhat-dist -privoxy:*:7777: |
This will create both binary and src RPMs in the usual places. Example:
/usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
/usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm
Some binary packages may do this for you.To install, of course:
Then, to build from either unpacked tarball or CVS source:
rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm -autoheader + autoconf + ./configure # (--help to see options) + make # (the make from GNU, sometimes called gmake) + su # Possibly required + make -n install # (to see where all the files will go) + make -s install # (to really install, -s to silence output) |
This will place the Privoxy configuration - files in /etc/privoxy/, and log files in - /var/log/privoxy/. Run - Using GNU ckconfig privoxy on to have - Privoxy start automatically during init.
To build SuSE RPM packages, install source as above. Then:
make, you can have the first four steps + automatically done for you by just typing:
autoheader - autoconf - ./configure - make suse-dist -make |
This will create both binary and src RPMs in the usual places. Example:
/usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
/usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm
in the freshly downloaded or unpacked source directory.To install, of course:
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:
rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm -./configure --disable-toggle --disable-editor --disable-force |
This will place the Privoxy configuration - files in /etc/privoxy/, and log files in - /var/log/privoxy/.
Privoxy is packaged in a WarpIN self- - installing archive. The self-installing program will be named depending - on the release version, something like: - privoxyos2_setup_2.9.14.exe. In order to install it, simply - run this executable or double-click on its icon and follow the WarpIN - installation panels. A shadow of the PrivoxyWARNING: If installing as root, the install will fail + unless a non-root user or group is specified, or a privoxy - executable will be placed in your startup folder so it will start - automatically whenever OS/2 starts.
"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.The directory you choose to install 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 - into will contain all of the configuration files.
, it must be run as this same user to + insure write access to configuration and log files!If you would like to build binary images on OS/2 yourself, you will need - a few Unix-like tools: autoconf, autoheader and sh. These tools will be - used to create the required config.h file, which is not part of the - source distribution because it differs based on platform. You will also - need a compiler. - The distribution has been created using IBM VisualAge compilers, but you - can use any compiler you like. GCC/EMX has the disadvantage of needing - to be single-threaded due to a limitation of EMX's implementation of the - select() socket call.
Alternately, you can specify user and group + on the make command line, but be sure both already exist:In addition to needing the source code distribution as outlined earlier, - you will want to extract the os2seutp directory from CVS: -
cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup -make -s install USER=privoxy GROUP=privoxy |
The default installation path for make install is Makefile.vac makefile and /usr/local. This may of course be customized with + the various ./configure path options. If you are doing + an install to anywhere besides os2build.cmd - which is used to completely create the binary distribution. The sequence - of events for building the executable for yourself goes something like this: -
cd current - autoheader - autoconf - sh configure - cd ..\os2setup - nmake -f Makefile.vac - |
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 - You will see this sequence laid out in "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 os2build.cmd$prefix/doc and install + there before creating a new $prefix/share/doc just for + Privoxy.
Click-click. (I need help on this. Not a clue here. Also for -configuration section below. HB.)
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. All + template files will be overwritten. If you have customized, local templates, + you should save these first, and in fact it is wise to always save 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.
Some quick notes on other Operating Systems.
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.For FreeBSD (and other *BSDs?), the build will require gmake - instead of the included make. gmake is - available from If you wish to receive an email notification whenever we release updates of + Privoxy or the actions file, http://www.gnu.org. - The rest should be the same as above for Linux/Unix.
In order not to lose your personal changes and adjustments when updating + to the latest default.action file we strongly + recommend that you use user.action and + user.filter for your local + customizations of Privoxy. See the Chapter on actions files for details.