Shorewall users - May 2009 - Case Change in Shorewall Rules & Logcheck

I did a quick search in the archives and I didn''t find anything about
this.  I apologize if this is a duplicate topic.

It seems that the "reject", "accept", "drop", etc,
keywords in the rule filtering have changed from uppercase to lowercase.  I
noticed this a few Shorewall releases ago but I simply haven''t gotten
around to asking about it.  I''m running Shorewall version 4.2.8 on
Debian squeeze/testing.

For instance, the previous syslog entry would look like this:
May 23 13:01:10 rockenfield kernel: [4400612.216917]
Shorewall:loc2net:REJECT:IN=eth1...

...and now it looks like this:
May 23 13:01:10 rockenfield kernel: [4400612.216917]
Shorewall:loc2net:reject:IN=eth1...

So I was just curious if this change was intentional and permanent so I can make
the appropriate modifications to my logcheck regular expression checking, or
perhaps it is something you''d like to know about so you can fix it and
put it back to the way it used to be.

Thanks,
-MikeD

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com

Mike wrote:
> I did a quick search in the archives and I didn''t find anything
about
> this.  I apologize if this is a duplicate topic.
> 
> It seems that the "reject", "accept", "drop",
etc, keywords in the
> rule filtering have changed from uppercase to lowercase.  I noticed
> this a few Shorewall releases ago but I simply haven''t gotten
around
> to asking about it.  I''m running Shorewall version 4.2.8 on Debian
> squeeze/testing.
> 
> For instance, the previous syslog entry would look like this: May 23
> 13:01:10 rockenfield kernel: [4400612.216917]
> Shorewall:loc2net:REJECT:IN=eth1...
> 
> ...and now it looks like this: May 23 13:01:10 rockenfield kernel:
> [4400612.216917] Shorewall:loc2net:reject:IN=eth1...
> 
> So I was just curious if this change was intentional and permanent so
> I can make the appropriate modifications to my logcheck regular
> expression checking, or perhaps it is something you''d like to know
> about so you can fix it and put it back to the way it used to be.
It isn''t intentional and I don''t see it occurring in my own
ruleset. So
if you will:

	- shorewall show -f capabilities > /etc/shorewall/caps
	- tar -zcf shorewall.tgz /etc/shorewall
	- Send shorewall.tgz to upload@shorewall.net. If
          SHOREWALL_COMPILER isn''t set in shorewall.conf, please
	  indicate if you are using Shorewall-shell or Shorewall-perl.

I will take a look at it.

Thanks,
-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 \________________________________________________



------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals.
Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com