Spurious newline in iptables-save output/policy match

Spurious newline in iptables-save output/policy match

[Tom Eastep]

-----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-----

Re: Spurious newline in iptables-save output/policy match

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On Wed, Aug 18, 2004 at 11:24:46AM -0700, Tom Eastep wrote:
 
> 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.

thanks, fixed in CVS.

 

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]