This bug was fixed in the package ifupdown - 0.8.10ubuntu1.1
---------------
ifupdown (0.8.10ubuntu1.1) xenial; urgency=medium
* Fix a crash when multiple interfaces are specified for no-scripts
(LP: #1618726)
-- Richard Laager <rlaa...@wiktel.com> Wed, 31 Aug 2016 02:29:11 -0500
** Changed in: ifupdown (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1618726
Title:
ifup & ifdown crash if multiple interfaces are listed in no-scripts
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Xenial:
Fix Released
Status in ifupdown package in Debian:
Fix Released
Bug description:
[Impact]
ifup and ifupdown segfault if multiple interfaces are listed in no-scripts
This is a trivially reproducible crash in ifup/ifdown, with a patch
attached.
[Test Case]
Steps to reproduce:
1) echo no-scripts foo bar >> /etc/network/interfaces
2) ifup baz
Expected results:
Unknown interface baz
Actual results:
Segmentation fault (core dumped)
It's irrelevant whether the second interface is on the same no-scripts line
or separate one. This will crash just the same:
echo no-scripts foo >> /etc/network/interfaces
echo no-scripts bar >> /etc/network/interfaces
[Regression potential]
Seems slight. The patch fixes a clear bug in code that is only used to
process the no-scripts (and apparently no-auto-down) stanzas.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+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
