<!entity history SYSTEM "history.sgml">
<!entity copyright SYSTEM "copyright.sgml">
<!entity license SYSTEM "license.sgml">
-<!entity p-version "3.0.16">
-<!entity p-status "UNRELEASED">
-<!entity % p-not-stable "INCLUDE">
-<!entity % p-stable "IGNORE">
+<!entity p-version "3.0.17">
+<!entity p-status "stable">
+<!entity % p-not-stable "IGNORE">
+<!entity % p-stable "INCLUDE">
<!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
<!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
<!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 2.67 2009/11/15 14:24:12 fabiankeil Exp $
+ $Id: faq.sgml,v 2.77 2011/03/03 14:22:12 fabiankeil Exp $
Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: faq.sgml,v 2.67 2009/11/15 14:24:12 fabiankeil Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 2.77 2011/03/03 14:22:12 fabiankeil Exp $</pubdate>
<!--
</para>
<para>
- We intend to use the donations to pay for our domain after transfering
+ We intend to use the donations to pay for our domain after transferring
it to SPI. Our goal is to make sure there's no single point of failure
and the bill gets paid and the site keeps running even if a some of
the currently active developers were to suddenly disappear for a while.
<para>
If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
a LAN) or aren't entirely in control of your own browser, you will probably want
- to make sure that the the web-based editor and remote toggle features are
+ to make sure that the web-based editor and remote toggle features are
<quote>off</quote> by setting <quote><literal><ulink
url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
0</literal></quote> and <quote><literal><ulink
<ulink
url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
action</ulink> in one of the actions files. Content filtering is automatically
- disabled for inappropriate MIME types, but if you now better than Privoxy
+ disabled for inappropriate MIME types, but if you know better than Privoxy
what should or should not be filtered you can filter any content you like.
</para>
<para>
<sect2 renderas="sect3" id="otherproxy">
-<title>How can I make Privoxy work with other
-proxies like Squid or Tor?</title>
+<title>How can I make Privoxy work with other proxies?</title>
<para>
This can be done and is often useful to combine the benefits of
- <application>Privoxy</application> with those of a another proxy.
+ <application>Privoxy</application> with those of a another proxy,
+ for example to cache content.
See the <ulink
url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
in the <ulink url="../user-manual/index.html">User Manual</ulink> which
- describes how to do this, and the <link linkend="TOR">
- How do I use Privoxy together with
- Tor</link> section below.
+ describes how to do this. If you intend to use Privoxy with Tor,
+ please also have a look at
+ <link linkend="TOR">How do I use Privoxy together with Tor</link>.
</para>
</sect2>
<para>
No, its more complicated than that. This only works with special kinds
- of proxies known as <quote>intercepting</quote> proxies (see below).
+ of proxies known as <quote>intercepting</quote> proxies
+ (<link linkend="INTERCEPTING">see below</link>).
</para>
</sect2>
<para>
However, some people say <quote>transparent proxy</quote> when they
mean <quote>intercepting proxy</quote>. If you are one of them,
- please read the <ulink url="#intercepting">next entry</ulink>.
+ please read the <link linkend="INTERCEPTING">next entry</link>.
</para>
</sect2>
If you verified that <application>Privoxy</application> and <application>Tor</application>
are working, it is time to connect them. As far as <application>Privoxy</application>
is concerned, <application>Tor</application> is just another proxy that can be reached
- by socks4 or socks4a. Most likely you are interested in <application>Tor</application>
- to increase your anonymity level, therefore you should use socks4a, to make sure DNS requests are
- done through <application>Tor</application> and thus invisible to your local network.
+ by socks4, socks4a and socks5. Most likely you are interested in <application>Tor</application>
+ to increase your anonymity level, therefore you should use socks5, to make sure DNS
+ requests are done through <application>Tor</application> and thus invisible to your
+ local network. Using socks4a would work too, but with socks5 you get more precise error
+ messages.
</para>
<
projects / privoxy.git / blobdiff