奇怪的iptables封闭的端口模式

抓住我的头在这一个…我使用屏蔽，而代理服务器，我只是与Rackspace安装。 这是我的iptablesconfiguration：

*filter # Allow all loopback (lo0) traffic and drop all traffic to 127/8 that doesn't use lo0 -A INPUT -i lo -j ACCEPT -A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT # Accept all established inbound connections -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # Allow all outbound traffic - you can modify this to only allow certain traffic -A OUTPUT -j ACCEPT # Allow HTTP and HTTPS connections from anywhere (the normal ports for websites and SSL). -A INPUT -p tcp --dport 80 -j ACCEPT -A INPUT -p tcp --dport 443 -j ACCEPT # Allow SSH connections -A INPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT # Allow ping -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT # Reject all other inbound - default deny unless explicitly allowed policy -A INPUT -j REJECT -A FORWARD -j REJECT COMMIT 

我把它保存到一个configuration文件中，并使用iptables-restore进行加载。 这是我的端口扫描是什么样子的：

什么可能导致这种封闭的港口模式？

• 什么将是一个更好的做法，而不是chmod g + r / etc / shadow所以我可以使用Unix用户/组数据库进行Jenkins身份validation？
• 有什么好方法来防止公众访问服务器/应用程序？
• 奇怪的攻击（日志文件充满Suhoshin消息）
• 是否有相当于Linux的Windows软件限制策略的开源代码？
• 如何从浏览器（ISPConfig）无法mail.example.com？

编辑：iptables -L的输出

 Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere REJECT all -- anywhere 127.0.0.0/8 reject-with icmp-port-unreachable ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:http ACCEPT tcp -- anywhere anywhere tcp dpt:https ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT icmp -- anywhere anywhere icmp echo-request REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere 

 -A INPUT -j REJECT