+ whitelist.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="no-adblock">
+<title>How can I turn off ad-blocking?</title>
+<para>
+ Ad blocking is hard-coded into the default configuration files. It has been
+ assumed that everyone using &my-app; is interested in this feature. If you want
+ to do without this, there are several approaches you can take: You can
+ manually undo the many block rules in <filename>default.action</filename>. Or
+ even easier, just create your own <filename>default.action</filename> file
+ from scratch without the many ad blocking rules, and corresponding exceptions.
+ Or lastly, if you are not concerned about the additional blocks that are
+ done for privacy reasons, you can very easily over-ride
+ <emphasis>all</emphasis> blocking with the following very simple rule in
+ <filename>user.action</filename>:
+ </para>
+ <para>
+ <screen>
+ # Unblock everybody, everywhere
+ { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
+ / # UN-Block *all* URLs
+ </screen>
+</para>
+<para>
+ Or even a more comprehensive reversing of various ad related actions:
+</para>
+<para>
+ <screen>
+ # Unblock everybody, everywhere, and turn off appropriate filtering, etc
+ { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> \
+ <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE">-filter{banners-by-size}</ulink> \
+ <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE">-filter{banners-by-link}</ulink> \
+ <literal>allow-popups</literal> \
+ }
+ / # UN-Block *all* URLs and allow ads
+ </screen>
+</para>
+<para>
+ This last <quote>action</quote> in this compound statement,
+ <literal>allow-popups</literal>, is an <ulink
+ url="../user-manual/actions-file.html#ALIASES">alias</ulink> that disables
+ various pop-up blocking features.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="templates">
+<title>How can I have custom template pages, like the
+<emphasis>BLOCKED</emphasis> page?</title>
+<para>
+ All the template pages are installed in a sub-directory appropriately named:
+ <filename>templates</filename>. These are specialized text files utilized
+ by &my-app; and can easily be modified using any text editor. Knowing something
+ about HTML will of course be helpful. You cannot rename any of these files,
+ or create completely new templates, that is not possible. But you can change
+ the page content to whatever you like. Be forewarned that these files are
+ subject to being overwritten during upgrades, so be sure to save any
+ customizations.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="blockall">
+<title>How can I remove the <quote>Go There Anyway</quote> link from
+the <emphasis>BLOCKED</emphasis> page?</title>
+<para>
+ Editing the template page (see above) may dissuade some users, but this
+ method is easily circumvented. Where you want this level of control, you should
+ build &my-app; from source, and enable various features that are
+ available as compile-time options. You should use
+ <command>configure</command> as follows:
+</para>
+<para>
+ <screen>
+ ./configure --disable-toggle --disable-editor --disable-force
+ </screen>
+</para>
+<para>
+ This will create an executable with hard-coded security features so that
+ &my-app; does not allow easy bypassing of blocks or changing the current
+ configuration. Some of these features can also by toggled on/off via options
+ in <application>Privoxy's</application> main
+ <ulink
+ url="../user-manual/config.html#ACCESS-CONTROL">config</ulink> file. But
+ compiled-in compliance is a much better method of ensuring that a block is
+ really a block.
+</para>
+<para>
+ Default builds of &my-app; are typically built with these features
+ disabled.
projects / privoxy.git / commitdiff