[Bug 1618726] Update Released

[Chris J Arges]

The verification of the Stable Release Update for ifupdown has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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