From: James Morris <jmorris@namei.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Sebastien Buisson <sbuisson.ddn@gmail.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
Sebastien Buisson <sbuisson@ddn.com>,
james.l.morris@oracle.com
Subject: Re: [PATCH 3/3] selinux: expose policy SHA256 checksum via selinuxfs
Date: Thu, 27 Apr 2017 11:08:32 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704271107450.28011@namei.org> (raw)
In-Reply-To: <1493231502.32540.12.camel@tycho.nsa.gov>
On Wed, 26 Apr 2017, Stephen Smalley wrote:
> > + return simple_read_from_buffer(buf, count, ppos, tmpbuf,
> > length);
> > +}
>
> Should we also include information about the hash used, in case it
> changes in the future?
>
Good idea, yes.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-04-27 1:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 15:02 [PATCH 1/3] selinux: Implement LSM notification system Sebastien Buisson
2017-04-26 15:02 ` [PATCH 2/3] selinux: add checksum to policydb Sebastien Buisson
2017-04-26 18:30 ` Stephen Smalley
2017-04-27 8:41 ` Sebastien Buisson
2017-04-27 15:18 ` Stephen Smalley
2017-04-27 17:12 ` Sebastien Buisson
2017-04-27 18:47 ` Stephen Smalley
2017-04-28 15:16 ` Sebastien Buisson
2017-04-28 15:50 ` Stephen Smalley
2017-04-28 16:08 ` Sebastien Buisson
2017-04-28 16:38 ` Stephen Smalley
2017-04-26 15:02 ` [PATCH 3/3] selinux: expose policy SHA256 checksum via selinuxfs Sebastien Buisson
2017-04-26 18:31 ` Stephen Smalley
2017-04-27 1:08 ` James Morris [this message]
2017-04-26 15:38 ` [PATCH 1/3] selinux: Implement LSM notification system Casey Schaufler
2017-04-26 15:48 ` Daniel Jurgens
2017-04-26 15:57 ` Sebastien Buisson
2017-04-26 16:11 ` Casey Schaufler
2017-04-26 17:36 ` Stephen Smalley
2017-04-26 17:47 ` Casey Schaufler
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=alpine.LRH.2.20.1704271107450.28011@namei.org \
--to=jmorris@namei.org \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sbuisson.ddn@gmail.com \
--cc=sbuisson@ddn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).