X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fbuildsource.sgml;h=b250502086d760e179e2a6cf5a93ccfe9974042a;hp=f6a7c676ae6c25f6ca7c5277ba9184c40a0cc806;hb=ec6c97624f9959aa0283d9311f29056623d76e10;hpb=b67871ce6e1570bc6afdfe3ff8db4c9c659d64ed
diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml
index f6a7c676..b2505020 100644
--- a/doc/source/buildsource.sgml
+++ b/doc/source/buildsource.sgml
@@ -3,9 +3,9 @@
Purpose : Entity included in other project documents.
- $Id: buildsource.sgml,v 2.8 2006/09/22 01:27:55 hal9 Exp $
+ $Id: buildsource.sgml,v 2.14 2007/11/22 17:38:40 hal9 Exp $
- Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org
+ Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
See LICENSE.
======================================================================
@@ -18,7 +18,7 @@
This file is included into:
user-manual
- README
+ INSTALL
-->
@@ -49,7 +49,7 @@
For retrieving the current CVS sources, you'll need a CVS client installed.
- Note that sources from CVS are typicially development quality, and may not be
+ 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:
@@ -76,9 +76,12 @@
It is also strongly recommended to not run Privoxy
- as root, and instead it is suggested to create a privoxy
user
- and group for this purpose. See your local documentation for the correct
- command line to do this.
+ 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).
@@ -111,13 +114,13 @@
autoconf
./configure # (--help to see options)
make # (the make from GNU, sometimes called gmake)
- su
+ su # Possibly required
make -n install # (to see where all the files will go)
make -s install # (to really install, -s to silence output)
- 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:
@@ -131,6 +134,19 @@
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. 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
@@ -146,8 +162,8 @@
--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 should be run as this same user to
- insure write access to configuration and log files.
+ Privoxy, it must be run as this same user to
+ insure write access to configuration and log files!
@@ -164,9 +180,10 @@
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
- a root install to anywhere else besides /usr/local, be
+ an install to anywhere besides /usr/local, be
sure to set the appropriate paths with the correct configure options
- (./configure --help).
+ (./configure --help). Non-privileged users must of course
+ have write access permissions to wherever the target installation is going.
@@ -180,10 +197,10 @@
- If installing to /usr/local, the docs 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
+ 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.
@@ -197,8 +214,8 @@
make install will attempt to set the correct values
- in config (main configuration file). You may want
- to check this to make sure all values are correct. If appropriate,
+ 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
@@ -206,14 +223,18 @@
- If install finds previous versions of any local 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. 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. If a previous version of Privoxy is
- already running, you will have to restart it manually.
+ 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.