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.
RPMs can be installed with rpm -Uvh privoxy-3.0.4-1.rpmrpm -Uvh privoxy-3.0.6-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.0.4-1.src.rpmrpm --rebuild privoxy-3.0.6-1.src.rpm. This will use your locally installed libraries and RPM version.
Junkbuster - automatically, before installing Privoxy.
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.
Privoxy in.Version 3.0.4 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.
gcc are required.
When building from a source tarball (either release version or - a nightly CVS tarball, first unpack the source:
When building from a source tarball, + first unpack the source:
tar xzvf privoxy-3.0.4-beta-src* [.tgz or .tar.gz] - cd privoxy-3.0.4-betatar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz] + cd privoxy-3.0.6 |
For retrieving the current CVS sources, you'll need CVS installed. - Note that sources from CVS are development quality, and may not be +> 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:
Privoxy - as root, and instead it is suggested to create a Privoxy as + an unprivileged user, preferably by creating a "privoxy" user - and group for this purpose. See your local documentation for the correct - command line to do this.
adduser, but the command syntax may vary from platform + to platform).
If you have GNU Using GNU make, you can have the first four steps @@ -604,6 +699,32 @@ CLASS="SCREEN" >
in the freshly downloaded or unpacked source directory.
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.
Privoxy, it should be run as this same user to - insure write access to configuration and log files.
, it must be run as this same user to + insure write access to configuration and log files!Alternately, you can specify ./configure path options. If you are doing - a root install to anywhere else besides /usr/local, be @@ -695,7 +816,8 @@ CLASS="FILENAME" (./configure --help).
). Non-privileged users must of course + have write access permissions to wherever the target installation is going. If you do install to If installing to /usr/local, the docs will go by default
- to , the documentation will go
+ by default to $prefix/share/doc. But if this directory doesn't
- exist, it will then try . But if this directory
+ doesn't exist, it will then try $prefix/doc and install there before
- creating a new and install
+ there before creating a new $prefix/share/doc just for
@@ -778,8 +900,8 @@ CLASS="COMMAND"
in config (main configuration file). You may want
- to check this to make sure all values are correct. If appropriate,
+> (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 If install finds previous versions of any configuration files, these will not
- be overwritten, and the new ones will be installed with a 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. You will then need to manually update the installed configuration
- files as needed. All template files will be overwritten. If you have
- customized, local templates, you should save these first. If a previous
+> 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 and SuSE RPMs,
+> For more detailed instructions on how to build Redhat RPMs,
Windows self-extracting installers, building on platforms with
special requirements etc, please consult the that you use user.action for your
- customization of and
+ user.filter for your local
+ customizations of Privoxy. See the