Phil Sutter <phil@xxxxxx> wrote: > In general, shells eating the quotes is problematic and users may not be > aware of it. This includes scripts that mangle ruleset dumps by > accident, etc. (Not sure if it is really a problem as we quote some > strings already). > > Using JSON, there are no such limits, BTW. I really wonder if there's > really no fix for bison parser to make it "context aware". Right. We can probably make lots of keywords available for table/chain names by only recognizing them while parsing rules, i.e. via 'start conditions' in flex. But I don't think there is anyone with the time to do the needed scanner changes.
