<!entity newfeatures SYSTEM "newfeatures.sgml">
<!entity p-intro SYSTEM "privoxy.sgml">
<!entity seealso SYSTEM "seealso.sgml">
+<!entity contacting SYSTEM "contacting.sgml">
+<!entity history SYSTEM "history.sgml">
+<!entity copyright SYSTEM "copyright.sgml">
+<!entity p-version "2.9.13">
+<!entity p-status "beta">
+<!entity % p-not-stable "INCLUDE">
+<!entity % p-stable "IGNORE">
+<!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 -->
]>
<!--
File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 1.38 2002/04/02 03:49:10 hal9 Exp $
+ $Id: faq.sgml,v 1.43 2002/04/04 21:59:53 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
</QandAEntry>
</QandASet>
+ ========================================================================
+ NOTE: Please read developer-manual/documentation.html before touching
+ anything in this, or other Privoxy documentation. You have been warned!
+ Failure to abide by this rule will result in the revocation of your license
+ to live a peaceful existence!
+ ========================================================================
+
-->
<artheader>
<title>Privoxy Frequently Asked Questions</title>
-<pubdate>$Id: faq.sgml,v 1.38 2002/04/02 03:49:10 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 1.43 2002/04/04 21:59:53 hal9 Exp $</pubdate>
<authorgroup>
<author>
]]>
<para>
This FAQ gives users and developers alike answers to frequently asked
- questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>.
+ questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>
+ <![%p-stable;[ v.&p-version]]>.
</para>
-<!--
- Include privoxy.sgml boilerplate:
--->
+<!-- Include privoxy.sgml boilerplate: -->
&p-intro;
+<!-- end boilerplate -->
<para>
You can find the latest version of the document at <ulink
url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
- Please see the Contact section in the <ulink
- url="../user-manual/contact.html">user-manual</ulink> if
- you want to contact the developers.
+ Please see the Contact section if you want to contact the developers.
</para>
<!-- <para> -->
significantly at this point.
</para>
<para>
- Please see the <ulink
- url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for more
+ Please see the <link linkend="copyright">History section</link> for more
information on the history of <application>Junkbuster</application> and
<application>Privoxy</application>.
</para>
<quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>.
</para>
<para>
- There are possible legal complications from the continued use of the
- <application>Junkbuster</application> name, which is a trademark of
+ There are potential legal complications from the continued use of the
+ <application>Junkbuster</application> name, which is a registered trademark of
<ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
+ And thus they <quote>own</quote> the rights to the name.
(There are, however, no objections from Junkbusters Corporation to the
<application>Privoxy</application> project itself, and they, in fact, still
share our ideals and goals.)
</para>
<para>
- The developers also believed that there so many changes from the original
+ The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make
- a name in their own right, especially now with the pending release of
- version 3.0.
+ a name in their own right<![%p-not-stable;[, especially now with the pending
+ release of version 3.0]]>.
</para>
</sect2>
</para>
<para>
The configuration has changed significantly as well. This is something that
- users will notice right off the bat. The <quote>blocklist</quote> file does
- not exist any more. This is replaced by <quote>actions</quote> files, such
- as <filename>default.actions</filename>. This is where most of the per site
- configuration is now.
+ users will notice right off the bat if you are upgrading from
+ <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
+ file does not exist any more. This is replaced by <quote>actions</quote>
+ files, such as <filename>default.actions</filename>. This is where most of
+ the per site configuration is now.
</para>
</sect2>
<sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
-<!--
- Include newfeatures.sgml
--->
-&newfeatures;
+<!-- Include newfeatures.sgml: -->
+ &newfeatures;
+<!-- end include -->
</sect2>
<application>Privoxy</application> configuration is very flexible, and
includes tools to help identify these types of situations so they can be
addressed as needed, allowing you to customize your installation.
- (<link linkend="badsite">See the appendix below</link>.)
+ (<link linkend="badsite">See the Troubleshooting section below</link>.)
</para>
</sect2>
<sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
warranty? Registration?</title>
<para>
- <application>Privoxy</application> is licensed under the
- GNU General Public License (GPL). It is free to use, copy,
- modify or distribute as you wish under the terms of this license.
- Please see the
-<ulink url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for
- more information on the license and copyright.
+ <application>Privoxy</application> is licensed under the GNU General Public
+ License (GPL). It is free to use, copy, modify or distribute as you wish
+ under the terms of this license. Please see the Copyright section for more
+ information on the license and copyright.
</para>
<para>
<para>
See the <ulink
url="../user-manual/index.html">user-manual</ulink> for
- platform specific installation instructions. [FIXME: This is meant for after
- the name change for 3.0!]
+ platform specific installation instructions.
</para>
<para>
Note: Some installers may automatically uninstall
<sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
<para>
- There are major changes to <application>Junkbuster</application>,
- <application>Privoxy</application>, configuration from version 2.0.x to
+ There are major changes to <application>Junkbuster</application>/
+ <application>Privoxy</application> configuration from version 2.0.x to
2.9.x and later. Most of the older files will not work at all. This is
especially true of <filename>blocklist</filename>. If this is the case, you
will need to re-enter your old data into the new configuration structure.
</sect2>
<sect2 renderas="sect3" id="actionss">
-<title>The <quote>actions</quote>concept confuses me. Please list
+<title>The <quote>actions</quote> concept confuses me. Please list
some of these <quote>actions</quote>.</title>
<para>
These are all explained in the
browser? Does that not raise security issues?</title>
<para>
What I don't understand, is how I can browser edit the config file as a
-regular user, while the whole /etc/privoxy hierarchy belongs to the user
-"privoxy", with only 644 perms.
+regular user, while the whole <filename>/etc/privoxy</filename> hierarchy
+belongs to the user <quote>privoxy</quote>, with only 644 permissions.
</para>
<para>
When you use the browser-based editor, <application>Privoxy</application>
itself is writing to the config files. Because
-<application>Privoxy</application> is running as the user "privoxy", it can
+<application>Privoxy</application> is running as the user <quote>privoxy</quote>, it can
update the config files.
</para>
<para>
-If you don't like this, setting "enable-edit-actions 0" in the config file
-will disable the browser-based editor. If you're that paranoid, you should
-also consider setting "enable-remote-toggle 0" to prevent browser-based
-enabling/disabling of <application>Privoxy</application>.
+If you don't like this, setting <quote>enable-edit-actions 0</quote> in the
+config file will disable the browser-based editor. If you're that paranoid,
+you should also consider setting <quote>enable-remote-toggle 0</quote> to prevent
+
browser-based enabling/disabling of <application>Privoxy</application>.
</para>
<para>
-Note that normally only local users can connect to <application>Privoxy</application>, so this is not
-(normally) a security problem.
+Note that normally only local users can connect to
+<application>Privoxy</application>, so this is not (normally) a security
+problem.
</para>
</sect2>
</para>
</sect2>
+<sect2 renderas="sect3" id="srvany">
+<title>Can <application>Privoxy</application> run as a service
+on Win2K/NT?</title>
+<para>
+ Yes, it can run as a system service using <command>srvany.exe</command>.
+ The only catch is that this will effectively disable the
+ <application>Privoxy</application> icon in the taskbar. You can have
+ one or the other, but not both at this time :(
+</para>
+<para>
+ There is a pending feature request for this functionality. See
+ thread: <ulink
+ url="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</ulink>,
+ for details, and a sample configuration.
+
+</para>
+</sect2>
+
+
<sect2 renderas="sect3" id="otherproxy">
<title>How can I make <application>Privoxy</application> work with other
proxies like <application>Squid</application>?</title>
<para>
If you have version 2.0.2, then the equivalent is
http://example.com/show-proxy-args (but you get far less information, and you
-should really consider upgrading to 2.9.x).
+should really consider upgrading to &p-version;).
</para>
</sect2>
<sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
<para>
- No. The format of the blocklists has changed significantly in the versions
- 2.9.x. Once we have released the new stable version, v3.0, there will
- again be blocklists that you can update automatically.
+ No. The format of the blocklists has changed significantly in versions
+ 2.9.x and later. <![%p-not-stable;[Once we have released the new stable
+ version, v3.0, there will again be blocklists that you can update
+ automatically.]]>
</para>
</sect2>
<para>
<application>Privoxy</application> can remove various information about you,
and allows <emphasis>you</emphasis> more freedom to decide which sites
- you can trust. But it's still possible that web sites can find out who you
- are. Here's one way this can happen.
+ you can trust, and what details you want to reveal. But it's still possible
+ that web sites can find out who you are. Here's one way this can happen.
</para>
<para>
A few browsers disclose the user's email address in certain situations, such
If you have problems with a site, you will have to adjust your configuration
accordingly. Cookies are probably the most likely adjustment that may
be required, but by no means the only one.
-
</para>
</sect2>
<sect2 renderas="sect3" id="seealso">
<title>Where can I find more information about <application>Privoxy</application>
and related issues?</title>
-
-<!--
- Include seealso.sgml
--->
-
+<!-- Include seealso.sgml boilerplate: -->
&seealso;
+<!-- end boilerplate -->
<!--
<para>
</sect1>
-->
-<!-- ~~~~~ New section ~~~~~ -->
-<!--
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
+<!-- Include contacting.sgml -->
+ &contacting;
+<!-- end contacting -->
+ </sect1>
+
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect1 id="copyright"><title>Copyright and History</title>
+
+<sect2><title>Copyright</title>
+<!-- Include copyright.sgml -->
+ ©right;
+<!-- end -->
+</sect2>
-This is referenced in the doc header already. HB 03/25/02
+<sect2><title>History</title>
+<!-- Include history.sgml -->
+ &history;
+<!-- end -->
+</sect2>
-<sect1 id="contact"><title>Contact the developers</title>
-<para>Please see the user manual for information on how to contact the developers.
-</para>
+ </sect1>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<!--
+<sect1 id="seealso"><title>See also</title>
+-->
+<!-- Include seealso.sgml -->
+<!--
+ &see;
+-->
+<!-- end -->
+<!--
</sect1>
-->
-
<!-- hhmts end -->
<!--
Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: faq.sgml,v $
+Revision 1.43 2002/04/04 21:59:53 hal9
+Added NT/W2K service/icon situation.
+
+Revision 1.42 2002/04/04 18:46:47 swa
+consistent look. reuse of copyright, history et. al.
+
+Revision 1.41 2002/04/04 06:48:37 hal9
+Structural changes to allow for conditional inclusion/exclusion of content
+based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
+definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
+eventually be set by Makefile.
+More boilerplate text for use across multiple docs.
+
+Revision 1.40 2002/04/03 04:22:03 hal9
+Fixed several typos.
+
+Revision 1.39 2002/04/03 03:53:03 hal9
+Revert some changes, and then make some news, to layout, and appearance.
+
Revision 1.38 2002/04/02 03:49:10 hal9
Major changes to doc structure and layout. Sections are not automatically
numbered now. TOC is on page by itself.
projects / privoxy.git / blobdiff