Regenerate with completed selinux section.

diff --git a/doc/webserver/faq/index.html b/doc/webserver/faq/index.html
index 7c37db2..ab53e58 100644 (file)
--- a/doc/webserver/faq/index.html
+++ b/doc/webserver/faq/index.html
@@ -48,7 +48,7 @@ TARGET="_top"
 ><BR></P
 ><P
 CLASS="PUBDATE"
->$Id: faq.sgml,v 2.51 2009/02/12 16:08:26 fabiankeil Exp $<BR></P
+>$Id: faq.sgml,v 2.52 2009/02/14 10:27:52 fabiankeil Exp $<BR></P
 ><DIV
 ><DIV
 CLASS="ABSTRACT"

diff --git a/doc/webserver/faq/trouble.html b/doc/webserver/faq/trouble.html
index 7a5277b..1f5530f 100644 (file)
--- a/doc/webserver/faq/trouble.html
+++ b/doc/webserver/faq/trouble.html
@@ -1148,15 +1148,18 @@ CLASS="APPLICATION"
 >Privoxy's</SPAN
 > case the problem usually
  is that the policy only allows outgoing connections for certain
- destination ports (e.g. 80 and 443). While the standard ports
- maybe covered, websites occasionally use other ports as well.
+ destination ports (e.g. 80 and 443). While this may cover the
+ standard ports, websites occasionally use other ports as well.
  This isn't a security problem and therefore <SPAN
 CLASS="APPLICATION"
 >Privoxy's</SPAN
 >
  default configuration doesn't block these requests.</P
 ><P
-></P
+> If you really want to block these ports (and don't be able
+ to load websites that don't use standard ports), you should
+ configure Privoxy to block these ports as well, so it doesn't
+ trigger the selinux warnings.</P
 ></DIV
 ></DIV
 ><DIV