Beta 1 had some significant issues, so I've uploaded Beta 2.
1) When the new shorewallrc file was installed (such as from the RPM),
VARDIR was being interpreted the same as VARLIB in the CLI. In
a generated script, VARDIR was being set to $VARDIR/$PRODUCT.
2) If the CONFIG_PATH setting required variable expansion and the
"-e" compiler option was specified, the settings in the export
shorewallrc were being used rather than those from the local
shorewallrc.
3) The new stoppedrules files contained a bogus 'FORMAT 2' directive
that caused compilation to fail.
Known Issues:
1) Both the "routestopped" and "stoppedrules" file are being processed
currently and in that order. It would be more appropriate to
process "stoppedrules" first and then process "routestopped" only
if "stoppedrules" contained no rules.
New Features:
When "-e" is specified and no output script is named on the
run-line, the default script is now "firewall" in the current
working directory.
Thank you for testing,
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
