On Sun, 08 Nov 2015 07:33:44 -0800
Tom Eastep <[email protected]> wrote:

> On 11/08/2015 02:51 AM, Tuomo Soini wrote:
> > I have a big change suggested for shorewall config file format.
> > 
> > Now when shorewall supports new config file format with
> > { proto=tcp, dport=25 } format or { PROTO=tcp, DPORT=25 } I'd like
> > to suggest biggest change to shorewall config file headers ever...
> > 
> > I have been playing with idea to change two-line config header
> > format to one line only format. Here is a example from one config
> > file, stoppedrules:
> > 
> > #######################################################################
> > #ACTION         SOURCE          DEST            PROTO   DEST
> > SOURCE #
> > PORT(S) PORT(S)
> > 
> > stoppedrules with one line config header format:
> > 
> > 
> > #######################################################################
> > #ACTION         SOURCE          DEST            PROTO   DPORT
> > SPORT
> > 
> > Real point is, this way the short names would be visible directly
> > from config file header so people could just start using the new
> > config file format which is especially useful for USER column or
> > any other column far on right in rules.
> > 
> > What do you think about this idea?
> > 
> 
> I think it requires a very large change to the documentation...

Yes it does, but we can use wonderful grep tool to find places to
change :-) I can do that if that sounds a change we want to do.

-- 
Tuomo Soini <[email protected]>
Foobar Linux services
+358 40 5240030
Foobar Oy <http://foobar.fi/>

Attachment: pgpBFdr14lH9w.pgp
Description: OpenPGP digital signature

------------------------------------------------------------------------------
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to