From: Richard Haines <richard_c_haines@btinternet.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
"Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 1/3] libselinux: Evaluate inodes in selinux_restorecon(3)
Date: Tue, 31 May 2016 13:05:33 +0000 (UTC) [thread overview]
Message-ID: <532278537.3784656.1464699933281.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <08abe881-e195-92d0-fa20-87eadaccf645@tycho.nsa.gov>
> On Friday, 20 May 2016, 17:24, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > On 05/10/2016 11:22 AM, Richard Haines wrote:
>> This patch transfers matchpathcon.c inode evaluation services to
>> selinux_restorecon.c and modifies them to also support setfiles(8)
>> inode services.
>>
>> The overall objective is to modify restorecon(8) and setfiles(8)
>> to use selinux_restorecon(3) services and then, when ready
>> remove the deprecated matchpathcon services from libselinux.
>>
>> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
>> ---
>> libselinux/include/selinux/restorecon.h | 4 +
>> libselinux/man/man3/selinux_restorecon.3 | 5 +-
>> libselinux/src/matchpathcon.c | 139 +------------
>> libselinux/src/selinux_restorecon.c | 333
> ++++++++++++++++++++++++++++---
>> libselinux/utils/selinux_restorecon.c | 14 +-
>> 5 files changed, 330 insertions(+), 165 deletions(-)
>>
----- snip ------
>
> Maybe we ought to just leave the matchpathcon ones alone (aside from
> deprecating and ultimately removing them), and bring over the versions
> added to setfiles when it was converted to using selabel_open().
>
I'll leave matchpathcon alone and port over the setfiles code.
prev parent reply other threads:[~2016-05-31 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 15:22 [PATCH 1/3] libselinux: Evaluate inodes in selinux_restorecon(3) Richard Haines
2016-05-20 16:26 ` Stephen Smalley
2016-05-20 17:04 ` Christopher J. PeBenito
2016-05-31 13:05 ` Richard Haines [this message]
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=532278537.3784656.1464699933281.JavaMail.yahoo@mail.yahoo.com \
--to=richard_c_haines@btinternet.com \
--cc=cpebenito@tresys.com \
--cc=sds@tycho.nsa.gov \
--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.