This bug was fixed in the package apport - 2.20.1-0ubuntu2.13
---------------
apport (2.20.1-0ubuntu2.13) xenial-security; urgency=medium
* REGRESSION UPDATE: Fix regression in previous upload by re-enabling
container support. (LP: #1732518)
* REGRESSION UPDATE: Fix the core_pattern for upstart based systems to
include the dump mode.
* Add code preventing a user from confusing apport by using
a manually crafted filesystem inside a combination of a user and mount
namespace.
* Add a check in apport receiver for the number of arguments so that
should another argument be added later, the receiver will simply ignore
the crash until it itself gets updated.
-- Stéphane Graber <stgra...@ubuntu.com> Wed, 15 Nov 2017 17:00:24
-0500
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732518
Title:
Please re-enable container support in apport
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Xenial:
Fix Released
Status in apport source package in Zesty:
Fix Released
Status in apport source package in Artful:
Fix Released
Status in apport source package in Bionic:
Triaged
Bug description:
The latest security update for apport disabled container crash
forwarding, this is a feature which users do rely on in production and
while it may have been appropriate to turn it off to put a security
update out, this needs to be re-enabled ASAP.
I provided a patch which fixed the security issue before the security
issue was publicly disclosed so pushing an SRU to all Ubuntu releases
re-enabling this code should be pretty trivial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+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
