Note:
- On some platforms, the installer may remove previously installed versions, if
+> Note:
+ On some platforms, the installer may remove previously installed versions, if
found. (See below for your platform). In any case RPMs can be installed with rpm -Uvh privoxy-3.0.7-1.rpm,
- and will use /etc/privoxy for the location
- of configuration files. Note that on Red Hat, Privoxy will
- not be automatically started on system boot. You will
- need to enable that using chkconfig,
- ntsysv, or similar methods. If you have problems with failed dependencies, try rebuilding the SRC RPM:
- rpm --rebuild privoxy-3.0.7-1.src.rpm. This
- will use your locally installed libraries and RPM version. Also note that if you have a Junkbuster RPM installed
- on your system, you need to remove it first, because the packages conflict.
- Otherwise, RPM will try to remove Junkbuster
- automatically if found, before installing Privoxy. DEBs can be installed with /etc/privoxy for the location of
+> for the location of
configuration files. Just double-click the installer, which will guide you through
@@ -208,7 +151,7 @@ NAME="INSTALLATION-PACK-WIN"
in the same directory as you installed Privoxy in. Version 3.0.5 beta introduced full 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
+ actually exists, or it will not be permitted to
write to its log and configuration files. 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. First, make sure that no previous installations of
Junkbuster and / or
+> and / or
PrivoxyPrivoxy 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
@@ -364,155 +291,105 @@ CLASS="SECT3"
CLASS="SECT3"
>2.1.6. Mac OSX2.1.4. Mac OS X Unzip the downloaded file (you can either double-click on the file
- from the finder, or from the desktop if you downloaded it there).
- Then, double-click on the package installer icon named
- 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. 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. 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. To prevent the privoxy service from automatically starting when your computer
+ starts up, remove or rename the file Privoxy.pkg/Library/LaunchDaemons/org.ijbswa.privoxy.plist
- and follow the installation process.
- Privoxy will be installed in the folder
- /Library/Privoxy.
- It will start automatically whenever you start up. To prevent it from
- starting automatically, remove or rename the folder
+ (on OS X 10.5 and higher) or the folder named
/Library/StartupItems/Privoxy. To start Privoxy by hand, double-click on
- StartPrivoxy.command in the
- /Library/Privoxy folder.
- Or, type this command in the Terminal: You will be prompted for the administrator password. Copy and then unpack the lha archive to a suitable location.
- All necessary files will be installed into Privoxy2.1.6. Installation from source 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. 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. To prevent the privoxy service from automatically starting when your computer
+ starts up, remove or rename the file /Library/LaunchDaemons/org.ijbswa.privoxy.plist
- 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
- File 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 Privoxy is part of FreeBSD's Ports Collection, you can build and install
+ it 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/privoxycd /usr/ports/www/privoxy; make install clean.2.1.1. Red Hat and Fedora RPMs
2.1.2. Debian and Ubuntu2.1.1. Debian and Ubuntu
2.1.4. Solaris
2.1.5. OS/22.1.3. OS/2
2.1.5. Installation from ready-built package
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. /Library/Privoxy/StartPrivoxy.command
-
2.1.7. AmigaOS
2.1.8. FreeBSD
2.1.9. Gentoo2.1.7. FreeBSD
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 project download page, + or you can get the up-to-the-minute, possibly unstable, development version from + the - CVS repository.
https://www.privoxy.org/.To build Privoxy from source, +> from source, GNU make - (gmake), and, of course, a C compiler like 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-3.0.7-beta-src* [.tgz or .tar.gz] - cd privoxy-3.0.7-betatar xzvf privoxy-3.0.27-beta-src.tar.gz + cd privoxy-3.0.27-beta |
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@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current - cd currentcd <root-dir> + git clone https://www.privoxy.org/git/privoxy.git |
This will create a directory named current/, which will - contain the source tree.
<root-dir>/privoxy/, + which will contain the source tree.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).
Note that source code in GIT is development quality, and may not be + stable or well tested.It is also strongly recommended to not run It is strongly recommended to not run Privoxy @@ -633,7 +488,7 @@ CLASS="APPLICATION" CLASS="APPLICATION" >Privoxy as - an unprivileged user, preferably by creating a "privoxy" user @@ -643,14 +498,13 @@ CLASS="QUOTE" CLASS="COMMAND" >adduser, but the command syntax may vary from platform - to platform).
/etc/passwd might then look like:
And then /etc/group, like:
Some binary packages may do this for you.
Then, to build from either unpacked tarball or CVS source:
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.
To build an executable with security enhanced features so that +> To build an executable with security enhanced features so that users cannot easily bypass the proxy (e.g. "Go There Anyway"configure like this:
Then build as above. In Privoxy 3.0.7 and later, all of these options -can also be disabled through the configuration file.
Note that all of these options can also be disabled through the configuration file.make command line, but be sure both already exist:
The default installation path for make install is +> is /usr/local. This may of course be customized with +>. This may of course be customized with the various ./configure path options. If you are doing +> path options. If you are doing an install to anywhere besides /usr/local/var/run/privoxy.pid.
.make install will attempt to set the correct values +> will attempt to set the correct values in config (main configuration file). You should +> (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 + an init script will be installed, but it is up to the user to determine how and where to start Privoxy. The init +>. The init script should be checked for correct paths and values, if anything other than a default install is done.
"new" extension. default.action, default.filter, and - standard.action extension. default.action and default.filter + 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 + 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" 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.
Install the Cygwin utilities needed to build Privoxy. + If you have a 64 bit CPU (which most people do by now), get the + Cygwin setup-x86_64.exe program here + (the .sig file is here). +
Run the setup program and from View / Category select: +
Devel + autoconf 2.5 + automake 1.15 + binutils + cmake + gcc-core + gcc-g++ + git + make + mingw64-i686-gcc-core + mingw64-i686-zlib + Editors + vim + Libs + libxslt: GNOME XSLT library (runtime) + Net + curl + openssh + Text + docbook-dssl + docbook-sgml31 + docbook-utils + openjade + Utils + gnupg + Web + w3m |
If you haven't already downloaded the Privoxy source code, get it now: +
mkdir <root-dir> + cd <root-dir> + git clone https://www.privoxy.org/git/privoxy.git |
Get the source code (.zip or .tar.gz) for tidy from + https://github.com/htacg/tidy-html5/releases, + unzip into <root-dir> and build the software: +
cd <root-dir> + cd tidy-html5-x.y.z/build/cmake + cmake ../.. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIB:BOOL=OFF -DCMAKE_INSTALL_PREFIX=/usr/local + make && make install |
If you want to be able to make a Windows release package, get the NSIS .zip file from + + https://sourceforge.net/projects/nsis/files/NSIS%203/ + and extract the NSIS directory to privoxy/windows. + Then edit the windows/GNUmakefile to set the location of the NSIS executable - eg: +
# Path to NSIS +MAKENSIS = ./nsis/makensis.exe |
To build just the Privoxy executable and not the whole installation package, do: +
cd <root-dir>/privoxy + ./windows/MYconfigure && make |
Privoxy uses the GNU Autotools + for building software, so the process is: +
$ autoheader # creates config.h.in + $ autoconf # uses config.h.in to create the configure shell script + $ ./configure [options] # creates GNUmakefile + $ make [options] # builds the program |
The usual configure options for building a native Windows application under cygwin are +
--host=i686-w64-mingw32 + --enable-mingw32 + --enable-zlib + --enable-static-linking + --disable-pthread + --disable-dynamic-pcre |
You can set the CFLAGS and LDFLAGS envars before + running configure to set compiler and linker flags. For example: +
$ export CFLAGS="-O2" # set gcc optimization level + $ export LDFLAGS="-Wl,--nxcompat" # Enable DEP + $ ./configure --host=i686-w64-mingw32 --enable-mingw32 --enable-zlib \ + > --enable-static-linking --disable-pthread --disable-dynamic-pcre + $ make # build Privoxy |
See the Developer's Manual + for building a Windows release package. +
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, ijbswa-announce@lists.sourceforge.net.
, privoxy-announce@lists.privoxy.org.In order not to lose your personal changes and adjustments when updating to the latest that you use user.action and +> and user.filter