From: Martin Pitt <martin.pitt@ubuntu.com>
To: Eugene Teo <eteo@redhat.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jeremy@goop.org, martin.pitt@ubuntu.com, wwoods@redhat.com
Subject: Re: [PATCH 0/3] core_pattern: cleaned up repost/continuing post of core_pattern enhancements
Date: Sun, 29 Jul 2007 17:53:00 +0200 [thread overview]
Message-ID: <20070729155300.GC5794@piware.de> (raw)
In-Reply-To: <46AC900E.9090405@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Hi Eugene,
Eugene Teo [2007-07-29 21:03 +0800]:
> >> Also, it is probably good to think how we can "drop privileges" while piping
> >> the core dump output to an external program. A malicious user can potentially
> >> use it as a possible backdoor since anything that is executed by "|program" will
> >> be executed with root privileges.
> >>
> > It was my understanding that apport already did this.
>
> I haven't looked at apport yet, but are you talking about the userspace portion of
> apport or the kernel changes in the Ubuntu kernel?
Similarly to Neil's patches, the Ubuntu kernel calls the userspace
helper as root, too. Apport drops privileges to the target process as
soon as possible (there are a few things it needs to do before, like
opening an fd to the crash file in /var/crash/ if that is only
writeable by root).
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-29 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 20:00 [PATCH 0/3] core_pattern: cleaned up repost/continuing post of core_pattern enhancements Neil Horman
2007-07-29 10:40 ` Eugene Teo
2007-07-29 12:14 ` Neil Horman
2007-07-29 13:03 ` Eugene Teo
2007-07-29 15:53 ` Martin Pitt [this message]
2007-07-29 23:45 ` Eugene Teo
2007-07-30 0:54 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070729155300.GC5794@piware.de \
--to=martin.pitt@ubuntu.com \
--cc=akpm@linux-foundation.org \
--cc=eteo@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=wwoods@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox