From: Richard Haines <richard_c_haines@btinternet.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: [RFC PATCH V3] libselinux: Add selabel_digest function
Date: Mon, 12 Oct 2015 12:26:21 +0000 (UTC) [thread overview]
Message-ID: <1884047573.3637566.1444652781647.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <56181972.8000901@tycho.nsa.gov>
> On Friday, 9 October 2015, 20:46, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > On 09/30/2015 11:29 AM, Richard Haines wrote:
>> selabel_digest(3) if enabled by the SELABEL_OPT_DIGEST option during
>> selabel_open(3) will return an SHA1 digest of the spec files, plus
>> a list of the specfiles used to calculate the digest. There is a
>> test utility supplied that will demonstrate the functionality.
>>
>> The use case for selabel_digest(3) is to implement an selinux_restorecon
>> function based on the Android version that writes a hash of the
>> file_contexts files to an extended attribute to enhance performance
>> (see external/libselinux/src/android.c selinux_android_restorecon()).
>>
>> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
>
> Seems sane to me. Is there a reason it is still an RFC?
>
No - Would you like it submitted without the RFC
>> ---
>> V2 Changes:
>> Minor general cleanups and updated as per comments from:
>> http://marc.info/?l=selinux&m=144233357510422&w=2
>> V3 Changes:
>> As per comments from:
> http://marc.info/?l=selinux&m=144355202127208&w=2
next prev parent reply other threads:[~2015-10-12 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 15:29 [RFC PATCH V3] libselinux: Add selabel_digest function Richard Haines
2015-10-09 19:45 ` Stephen Smalley
2015-10-12 12:26 ` Richard Haines [this message]
2015-10-13 21:17 ` Stephen Smalley
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=1884047573.3637566.1444652781647.JavaMail.yahoo@mail.yahoo.com \
--to=richard_c_haines@btinternet.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.