** Changed in: iptables (Ubuntu Bionic)
Status: New => In Progress
** Changed in: iptables (Ubuntu Focal)
Status: New => In Progress
** Changed in: iptables (Ubuntu Jammy)
Status: New => In Progress
** Changed in: iptables (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: iptables (Ubuntu Bionic)
Assignee: (unassigned) => Louis Bouchard (louis)
** Changed in: iptables (Ubuntu Focal)
Assignee: (unassigned) => Louis Bouchard (louis)
** Changed in: iptables (Ubuntu Jammy)
Assignee: (unassigned) => Louis Bouchard (louis)
** Changed in: iptables (Ubuntu Kinetic)
Assignee: (unassigned) => Louis Bouchard (louis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1992454
Title:
iptables: segfault when renaming a chain
Status in iptables package in Ubuntu:
In Progress
Status in iptables source package in Bionic:
In Progress
Status in iptables source package in Focal:
In Progress
Status in iptables source package in Jammy:
In Progress
Status in iptables source package in Kinetic:
In Progress
Bug description:
This is the description for the upstream fix of this bug[1] :
This is an odd bug: If the number of chains is right and one renames the
last one in the list, libiptc dereferences a NULL pointer.
Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug
upstream. This bug is to have the fix included in Ubuntu in order to
avoid such segmentation faults.
[1]
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
