http://qa.mandrakesoft.com/show_bug.cgi?id=2567
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2003-03-07 05:44 -------
Please don't assign bugs to other people. I have no power to apply the patch.
Since the "bug" isn't a problem as long as you feed the program correct data...
Considering that we are in a freeze except for *CRITICAL* bugs. This will not
be fixed for 9.1. When iptables 1.2.8 gets picked up post 9.1 the fix will be
applied.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
Hi,
I create some rules that I list with iptables-save:
# Generated by iptables-save v1.2.7a on Sat Mar 1 15:10:14 2003
*nat
:PREROUTING ACCEPT [1670:81196]
:POSTROUTING ACCEPT [56:5326]
:OUTPUT ACCEPT [337:22639]
-A POSTROUTING -o ppp0 -j MASQUERADE
COMMIT
When I run iptables-restore and write some rule using STDIN (for example
:PREROUTING ACCEPT [1670:81196]), iptables-restore core dumps.
gdb backtrace tells:
(...)
#0 0x0804ee83 in iptc_builtin ()
#1 0x0804a296 in main ()
#2 0x4003f7f7 in __libc_start_main () from /lib/i686/libc.so.6
