><A
NAME="INSTALLATION-PACK-RPM"
></A
->2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
+>2.1.1. Red Hat and Fedora RPMs</H3
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
CLASS="APPLICATION"
>Privoxy</SPAN
> sources
- is to download the source tarball from our <A
-HREF="http://sf.net/projects/ijbswa/"
+ is to download the source tarball from our
+ <A
+HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&package_id=10571"
TARGET="_top"
->project
+>project download
page</A
>.</P
><P
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-3.0.6-beta-src* [.tgz or .tar.gz]
- cd privoxy-3.0.6-beta</PRE
+> tar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.6</PRE
></TD
></TR
></TABLE
></P
><P
> 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:</P
><P
CLASS="APPLICATION"
>Privoxy</SPAN
>
- as root, and instead it is suggested to create a <SPAN
+ as root. You should configure/install/run <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> as
+ an unprivileged user, preferably by creating a <SPAN
CLASS="QUOTE"
>"privoxy"</SPAN
> user
- and group for this purpose. See your local documentation for the correct
- command line to do this. </P
+ and group just for this purpose. See your local documentation for the correct
+ command line to do add new users and groups (something like
+ <B
+CLASS="COMMAND"
+>adduser</B
+>, but the command syntax may vary from platform
+ to platform). </P
><P
> <TT
CLASS="FILENAME"
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)</PRE
></TD
></TABLE
></P
><P
-> If you have GNU <B
+> Using GNU <B
CLASS="COMMAND"
>make</B
>, you can have the first four steps
><P
> in the freshly downloaded or unpacked source directory.</P
><P
+> To build an executable with security enhanced features so that
+ users cannot easily bypass the proxy (e.g. <SPAN
+CLASS="QUOTE"
+>"Go There Anyway"</SPAN
+>), or
+ alter their own configurations, <B
+CLASS="COMMAND"
+>configure</B
+> like this:</P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> ./configure --disable-toggle --disable-editor --disable-force</PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Then build as above.</P
+><P
> <SPAN
CLASS="emphasis"
><I
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, it should be run as this same user to
- insure write access to configuration and log files.</P
+>, it must be run as this same user to
+ insure write access to configuration and log files!</P
><P
> Alternately, you can specify <TT
CLASS="LITERAL"
CLASS="COMMAND"
>./configure</B
> path options. If you are doing
- a root install to anywhere else besides <TT
+ an install to anywhere besides <TT
CLASS="FILENAME"
>/usr/local</TT
>, be
(<B
CLASS="COMMAND"
>./configure --help</B
->).</P
+>). Non-privileged users must of course
+ have write access permissions to wherever the target installation is going.</P
><P
> If you do install to <TT
CLASS="FILENAME"
> If installing to <TT
CLASS="FILENAME"
>/usr/local</TT
->, the docs will go by default
- to <TT
+>, the documentation will go
+ by default to <TT
CLASS="FILENAME"
>$prefix/share/doc</TT
->. But if this directory doesn't
- exist, it will then try <TT
+>. But if this directory
+ doesn't exist, it will then try <TT
CLASS="FILENAME"
>$prefix/doc</TT
-> and install there before
- creating a new <TT
+> and install
+ there before creating a new <TT
CLASS="FILENAME"
>$prefix/share/doc</TT
> just for
in <TT
CLASS="FILENAME"
>config</TT
-> (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 <SPAN
CLASS="APPLICATION"
script should be checked for correct paths and values, if anything other than
a default install is done.</P
><P
-> 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
<SPAN
CLASS="QUOTE"
>"new"</SPAN
> 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 <SPAN
+ standard.action <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>will be overwritten</I
+></SPAN
+>. 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 <SPAN
+CLASS="QUOTE"
+>"just in case"</SPAN
+>. If a previous
+ version of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is
- already running, you will have to restart it manually.</P
+> is already running, you will
+ have to restart it manually.</P
><P
> For more detailed instructions on how to build Redhat RPMs,
Windows self-extracting installers, building on platforms with
projects / privoxy.git / blobdiff