Again, please don't trim CC lists.
Grant Taylor wrote:
On 07/01/08 09:10, Patrick McHardy wrote:
In any case, its unreasonable to expect us to never *extend* (not
change) the output to accomodate buggy parsers. This is by the way
the same way that is often used to extend binary structures, even
though someone stupid might use exact size checks.
*nod*
Agreed.
However as I sit here and think about it, it may be worth adding a new
field *as early as possible* (read closes to the start of line) in the
field list that indicates a version, which can be used to determine
the fields and their position there in. This would make it very easy
for people to write strict parsers down the road. A simple three
character hex field (4 bytes including the leading space) would allow
for 4k of strict layouts. (Even more 0-9 and a-z or additionally
A-Z.) Just a thought.
I don't it would be very useful at this time since we already made
those changes over the time of multiple years, so basically the
damage (if any) is already done.
And we have ULOG and nfnetlink_log that should be used for anything
serious for the reasons I stated earlier (more reliable, doesn't block
when using serial consoles, ...).
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
