Subject: 4 has been released What is coming: New features in Firewall Builder 2.

From: "ethically" <[email-masked]>
Date: Thu, 29 Mar 2007 10:10:42 +0100

My thanks to Jeffrey for the help. The "Help me build firewall policy" wizard was phased out and replaced with firewall templates. Finally beta testing is over and the  release is out. 6) will finally support printing; it is already included in the latest nightly builds starting with build 541. 5-beta This is the first "official" public beta testing release. By popular request, built-in installer can now save a copy of .
Fix implemented for this bug in v2.
4 I am currently working on several cool features that will be included in the upcoming v2. qm files Reasonably complete French translation is provided. We plan to run public beta for a few months and release final version in October.
Window size and position is remembered across multiple sessions for all dialogs.
If the file is checked out and locked by a different user, it can only be opened read-only. This feature helps to work around errors in the policy that block access to the firewall from the management workstation.
Atomic load means the whole filter or nat table is activated at once, and if there is an error, nothing is changed.
fw) but installer incorrectly uses name with suffix . 1 has been released This is a maintenance release that only includes bugfixes for a few bugs.
A critical bug in the policy compiler for ipfilter that has slipped through testing in v1. 12 Firewall Builder 2. 3 has been released Firewall Builder v2.
Not all platforms provide means to support run-time DNSName objects.
This preserves queue entries and states.
Complete Russian and Japanese translations have been added. The bug has been fixed in v2. Compiler is more tolerant while processing Address Table object with empty address file or with a file with empty lines. Installer has simple GUI interface and works on both Linux and Windows (uses putty or SecureCRT on Windows).
September 01, 2004 Firewall Builder v2. Run-time DNSName objects rely on the target firewall software to be able to convert symbolic names used in rules into actual IP addresses at a time when policy is activated. Tag can later be inspected using service object TagService.