[Windows Security] Windows Firewall hides its own port

According to CNET News.com, Windows XP and Windows Server 2003 self-contained Windows Firewall cannot view all opened ports on the Windows Firewall interface through some registry settings, these include the ports used by Windows Firewall.

Of course, as soon as the message is sent, Microsoft's website provides a patch that will be included in the future service pack. Of course, Microsoft also has its position that this is not a system vulnerability. However, for a system that has been attacked, this security risk can allow attackers to hide their real identities.

It also pointed out that through the command line
Netsh firewall show state verbose = Enable
You can see all opened ports, including those hidden by Windows Firewall. In this case, it seems that Microsoft has not intentionally hidden anything, but since Windows GUI is so easy to use, how many people will actually use the command line to type a long line of command to see which ports are opened?

The firewall is the first line of defense against external attacks on our system. I believe many people agree that it should faithfully tell users which ports are blocked and which ones are allowed, right? There are some problems that may cause user headaches at this stage.

For the original article, see:
Http://news.com.com/Windows+Firewall+flaw+may+hide+open+ports/2100-7355_3-5845850.html