• Sending data to (and receiving it from) port 53 on an attacker-controlled system - this would bypass the vast majority of firewalls that allow DNS by default.
• Enclosing the data within a valid DNS request (DNS offers options to handle other data including plain text) before sending it to an attacker-controlled system - this would bypass firewalls performing validity or syntax checks on DNS traffic.
• Enclosing such data within a valid DNS request before sending it to your normal DNS server which would then forward it to the attacker-controlled system (using a feature called "iterative DNS" where a DNS server sends a query to another server - this would require the attacker to set up their own domain with a pointer to their own compromised system). This would be permitted by any global rules settings for DNS however strict - only controlling DNS on a per-application basis would stop this, and only if Windows' DNS Client Service is disabled (monitoring Windows' API calls relating to DNS would remove the need to disable this service, which the latest versions of some firewalls, including Outpost 4.0, do)."

P.S. disable DNS service on your OS , you should then add one more rule (in Outpost) for every new network alowed application :

Protocol: UDP 

Remote host: "Your ISP"

Remote port: 53 (dns)

"It is another line of defence."

Of course you will passed DNS detour.

i autoupdate with no problem at all ;)

cheers..

THE ONE & ONLY

FNS

Works! Gives Free Way Business 101 days remaining.

Furthermore the key provided by LAZY earlier also works! xi chen Single (no limit given for expiration).

So thanks a lot LAZY

Allow most - All network connections are allowed except those that are explicitly blocked by global or application rules.

Rules Wizarddocument.write(PRODUCT)document.write(PRODUCT) - According to this policy, Outpost Firewall Pro displays a prompt each time a new application or process (for which no rules are specified) requests network access or when an application requests a connection that is not covered by its rules. Thus Outpost Firewall Pro lets you decide whether an application should be allowed a network connection to a specific address and port.

Block most - All network connections are blocked except those that are explicitly allowed by global or application rules.

P.S. I allways run in Rules wizard , but I recommend to run it in rules wizard till all rules are created (e.g. prompts are very rare or non) , then switch it to Block most.

Run it in alow most I dont recommend , maybe to my enemies e.g. Mr. Evil , Bush , Road runner , Hitler , Eminem ...etc.

"Btw, its amazing people still have not learned that using old dlls and exes on the new version is totally dumb. You are just downgrading the program again with old files and whatever updates that were added in the new version will just be nulled, not to mention it could cause the firewall to work eratically/unstable. Stop being noobs already, sheesh."

Can you demonstrate your point in this particular situation?

If you can't, shut up and let others play risky sometimes if they wish.