This change would be very interesting with a view to making machine
parsing more automated... (well self documenting anyway, won't affect
Shorewall code)
Ed
On 08/11/2015 10:51, 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?
>
------------------------------------------------------------------------------
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
