From: Florian Weimer <fweimer@redhat.com>
To: Daniel J Walsh <dwalsh@redhat.com>, SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Impersonating a process for file creation purposes
Date: Mon, 20 Apr 2015 16:05:20 +0200 [thread overview]
Message-ID: <553507A0.1050902@redhat.com> (raw)
In-Reply-To: <552FFA39.3030909@redhat.com>
On 04/16/2015 08:06 PM, Daniel J Walsh wrote:
>
> On 04/16/2015 05:28 AM, Florian Weimer wrote:
>> The ABRT coredump handler has code to emulate default core file creation
>> (as if no such pipe-based handler was installed). The handler runs in a
>> separate process, initially as root. Currently, the handler just
>> switches effective IDs and creates the file. This does not replicate
>> the SELinux context of the zombie process.
>>
>> Is there a way to do that? Is there some recommended way to inherit
>> all the security-related process attributes?
>>
> You have two choices. 1 would be to setcon() call to change the label
> to the user process.
>
> The other choice would be to ask the kernel what label this user would
> create if he created a file
> in the specified directory. This is what systemd does.
Dan, could you please double-check if this change (implementing the
second option) looks reasonable?
<https://github.com/abrt/abrt/commit/3e4155bfcd9f6f5a20964080fa05724503b20761>
Thanks,
Florian
--
Florian Weimer / Red Hat Product Security
next prev parent reply other threads:[~2015-04-20 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:28 Impersonating a process for file creation purposes Florian Weimer
2015-04-16 12:18 ` Stephen Smalley
2015-04-16 12:34 ` Florian Weimer
2015-04-27 9:06 ` Florian Weimer
2015-04-27 13:27 ` Stephen Smalley
2015-04-27 14:20 ` Stephen Smalley
2015-04-16 18:06 ` Daniel J Walsh
2015-04-20 14:05 ` Florian Weimer [this message]
2015-04-28 17:12 ` Miroslav Grepl
2015-04-28 17:19 ` Florian Weimer
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=553507A0.1050902@redhat.com \
--to=fweimer@redhat.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.