Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932471AbaDVMoj (ORCPT ); Tue, 22 Apr 2014 08:44:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33171 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932152AbaDVMod (ORCPT ); Tue, 22 Apr 2014 08:44:33 -0400 Message-ID: <53566428.9080005@redhat.com> Date: Tue, 22 Apr 2014 14:44:24 +0200 From: Florian Weimer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: David Herrmann CC: linux-kernel , Kay Sievers , Daniel Mack , Lennart Poettering , "dri-devel@lists.freedesktop.org" , linux-fsdevel , linux-mm Subject: Re: [PATCH 0/6] File Sealing & memfd_create() References: <1395256011-2423-1-git-send-email-dh.herrmann@gmail.com> <5343F2EC.3050508@redhat.com> <535631EB.4060906@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/22/2014 01:55 PM, David Herrmann wrote: > Hi > > On Tue, Apr 22, 2014 at 11:10 AM, Florian Weimer wrote: >> Ah. What do you recommend for recipient to recognize such descriptors? >> Would they just try to seal them and reject them if this fails? > > This highly depends on your use-case. Please see the initial email in > this thread. It describes 2 example use-cases. In both cases, the > recipients read the current set of seals and verify that a given set > of seals is set. I didn't find that very convincing. But in v2, seals are monotonic, so checking them should be reliable enough. What happens when you create a loop device on a write-sealed descriptor? -- Florian Weimer / Red Hat Product Security Team -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/