> Just prepare it as you have time and I'll look at it. I don't think it is
> critical to include a change in this release.
The more I dig into this, the more idiosyncrasies I find...
When I try and copy my (test case) shorewall.conf, actions, rules, blrules, and
even shorewallrc files into a separate directory and then try to execute
"shorewall compile firewall" I get this:
ERROR: Ordinary users may not compile the /etc/shorewall configuration [Oh,
really?]
My shorewall.conf *explicitly* states that
"CONFIG_PATH=.:${SHAREDIR}/shorewall" so why the hell is shorewall trying to
access /etc/shorewall? Even if I move my own copy of shorewallrc to the test
case directory and amend CONFDIR to point to my own (test case) directory, this
has no effect whatsoever.
When I execute "shorewall compile . firewall", this time I get
"/usr/share/shorewall/lib.cli-std: line 41: /etc/shorewall/params: Permission
denied".
Again, why the hell is shorewall looking in /etc/shorewall? lib.cli-std uses
"find_file", which is in lib.common and when I do a quick hack into this
function, I see that ${CONFDIR} is actually "/etc" and {CONFIG_PATH} is "<my
test case dir>:/etc/:/usr/share/shorewall".
So, why is shorewall disregarding my own shorewallrc, then "constructs" some
mickey-mouse CONFIG_PATH which has absolutely nothing whatsoever to do with the
one I specified in my (test case) shorewall.conf?
Executing "shorewall compile -e . filrewall" or "shorewall compile -e firewall"
is no good either.
How am I supposed to compile a shorewall configuration independent of the host
system then, using my own test case directory and the CONFIG_PATH I have
specified in my own shorewall.conf? I was able to do this before, but now, it
seems, this has been messed up again.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
