Red Hat Bugzilla – Bug 54160
iptables-save and iptables-restore parse and produce quotes differently from each other
Last modified: 2008-05-01 11:38:00 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (Windows NT 5.0; U) Description of problem: If one has a rule with the --log-prefix parameter, everytime one saves the rule with iptables-save and then restores it with iptables-restore, the log prefix is wrapped in an extra layer of quotes. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.iptables -A firewall -j LOG --log-prefix Firewall: --log-level 6 2.iptables-save | iptables-restore ; iptables-save | iptables-restore ; iptables-save | iptables-restore 3.iptables-save Actual Results: Line for rule listed as: -A firewall -j LOG --log-prefix """"Firewall:"""" --log-level 6 Expected Results: Line should be listed as -A firewall -j LOG --log-prefix Firewall: --log-level 6 or: -A firewall -j LOG --log-prefix "Firewall:" --log-level 6 Depending on how quotes should be parsed Additional info: iptables-save and iptables-restore should understand the same language.
# iptables -F firewall # iptables -X firewall # iptables -N firewall # iptables -A firewall -j LOG --log-prefix Firewall: --log-level 6 # iptables-save | iptables-restore ; iptables-save | iptables-restore ; iptables-save | iptables-restore # iptables-save FWIW, I'm unable to reproduce this, although I can confirm that the code adds quotes at the start and end of the prefix string if there are none. Which shell do you use? Do you have any special shell settings that backslash-escape double-quotes maybe?
Is this a duplicate of bug #52550?
Not exactly, but it's fixed in 1.2.3-1 as well.