From b5c1758f32d542ca15c354c1e1c650c2c329cc4a Mon Sep 17 00:00:00 2001 From: Clinton Ebadi Date: Sun, 6 Jan 2013 17:06:03 -0500 Subject: [PATCH 1/1] Update instructions for firewall rules requesters --- sec.mlt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sec.mlt b/sec.mlt index 158159a..022ab65 100644 --- a/sec.mlt +++ b/sec.mlt @@ -338,9 +338,9 @@ end%>

Request a new firewall rule

-

You can find a description of rule formats on our wiki. Enter here the rule you want, without the initial user portion.

+

You can find a description of rule formats on our wiki. Enter here the rule you want, without the initial user portion.

-

Please note that your firewall rule will be useless if you don't first request the corresponding socket privileges at the top of this page. Also, common ports like 80 (HTTP) are open to everyone with socket permissions. Verify that you can't access a port after socket permissions have been granted before requesting a special rule here.

+

When requesting a Server or ProxiedServer rule, use a port above 50000 (there is a list of allocated ports). We may grant Server requests for ports under 50000 if it can be justified, but never for a ProxiedServer.

We very rarely grant requests for Client rules that don't include remote host whitelists. For example, important security concerns make it a bad idea for us to give anybody blanket IRC permissions. Instead, request specific servers. We will refuse such requests that include networks that are popularly considered fronts for illegal activity.

-- 2.20.1