This bug was fixed in the package apport - 2.0.1-0ubuntu17.4
---------------
apport (2.0.1-0ubuntu17.4) precise-proposed; urgency=low
* Enable suid_dumpable (core dumps of setuid binaries). This has
always been safe for us, as we set a core pipe handler, but the
kernel now protects against one not being set:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
raring.git;a=blob;f=Documentation/sysctl/fs.txt;h=88152f214f48cb69c6
43d4bf2ff2ac9a61ad2eb0;hb=HEAD (LP: #1194541).
-- Evan Dandrea <e...@ubuntu.com> Tue, 25 Jun 2013 16:40:45 +0100
** Changed in: apport (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1194541
Title:
Create core dumps for setuid binaries
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport” source package in Precise:
Fix Released
Status in “apport” source package in Quantal:
Fix Released
Status in “apport” source package in Raring:
Fix Released
Bug description:
Kees has looked into setting /proc/sys/fs/setuid_dumpable to 2, which
will enable core dumps for setuid binaries. This is now safe in all
cases for kernels in raring and later. For quantal and earlier, a core
pipe handler must be set when /proc/sys/fs/setuid_dumpable is set to
2.
TEST CASE:
passwd
# In another shell
killall -SEGV passwd
ls -la /var/crash/_usr_bin_passwd.0.crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
