From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033380AbdD0BIw (ORCPT ); Wed, 26 Apr 2017 21:08:52 -0400 Received: from namei.org ([65.99.196.166]:42742 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S938002AbdD0BIo (ORCPT ); Wed, 26 Apr 2017 21:08:44 -0400 Date: Thu, 27 Apr 2017 11:08:32 +1000 (AEST) From: James Morris To: Stephen Smalley cc: Sebastien Buisson , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov, Sebastien Buisson , james.l.morris@oracle.com Subject: Re: [PATCH 3/3] selinux: expose policy SHA256 checksum via selinuxfs In-Reply-To: <1493231502.32540.12.camel@tycho.nsa.gov> Message-ID: References: <1493218936-18522-1-git-send-email-sbuisson@ddn.com> <1493218936-18522-3-git-send-email-sbuisson@ddn.com> <1493231502.32540.12.camel@tycho.nsa.gov> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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