This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 2.50 2009/02/11 18:13:36 fabiankeil Exp $
+ $Id: faq.sgml,v 2.51 2009/02/12 16:08:26 fabiankeil Exp $
Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
See LICENSE.
</subscript>
</pubdate>
-<pubdate>$Id: faq.sgml,v 2.50 2009/02/11 18:13:36 fabiankeil Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 2.51 2009/02/12 16:08:26 fabiankeil Exp $</pubdate>
<!--
<para>
In <application>Privoxy's</application> 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 <application>Privoxy's</application>
default configuration doesn't block these requests.
</para>
<para>
+ 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.
</para>
</sect2>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
$Log: faq.sgml,v $
+Revision 2.51 2009/02/12 16:08:26 fabiankeil
+Declare the code stable.
+
Revision 2.50 2009/02/11 18:13:36 fabiankeil
State the obvious.