From: Tom Eastep <teastep@shorewall.net>
To: Patrick McHardy <kaber@trash.net>, netfilter-devel@lists.netfilter.org
Subject: Spurious newline in iptables-save output/policy match
Date: Wed, 18 Aug 2004 11:24:46 -0700 [thread overview]
Message-ID: <41239EEE.3090908@shorewall.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There is an unwarrented "printf("\n") at the end of the static function
'save' in libipt_policy.c. This causes output from iptables-save to be
rejected by a subsequent iptables-restore.
Sample output from iptables-save:
- -A OUTPUT -o eth0 -m policy --dir out --pol ipsec
- -j fw2loc
- -Tom
- --
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBI57uO/MAbZfjDLIRArRhAKCc/qMdRqqo+cDSGJqEwd/iI0XP+gCcDvaa
GflrHppQVOb94NY5A9TzV+o=
=8dYn
-----END PGP SIGNATURE-----
next reply other threads:[~2004-08-18 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 18:24 Tom Eastep [this message]
2004-08-19 9:48 ` Spurious newline in iptables-save output/policy match Harald Welte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41239EEE.3090908@shorewall.net \
--to=teastep@shorewall.net \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.