From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE0F7C2BA83 for ; Thu, 13 Feb 2020 06:42:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9EE8A2082F for ; Thu, 13 Feb 2020 06:42:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="q/D+kHXK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727123AbgBMGmB (ORCPT ); Thu, 13 Feb 2020 01:42:01 -0500 Received: from mail-lj1-f195.google.com ([209.85.208.195]:38240 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726368AbgBMGmB (ORCPT ); Thu, 13 Feb 2020 01:42:01 -0500 Received: by mail-lj1-f195.google.com with SMTP id w1so5263987ljh.5; Wed, 12 Feb 2020 22:41:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mMmuNpdrddhrOWh+4K56L0YF6Be/7s8PGs+t3nQ9XBc=; b=q/D+kHXKQDgR3fVVwhifALKcssH8rymF8OkkigRJ302Sa9VjPP4heu3ZtnMqMs8SWS XLPb3FgDKBPMSWeu6sBU2k7bJZZY5mxwdfBDKVH2vG+qwbJUgymN/AujzSnIagkpxI8B 6IwKRdth3Zw+n5TUFfbmmfKzR43Iv0b79GWIjqXfELXZy4lQWLgLSvuy+Pe+SinogQXV DFIka3jUmL7L2OdQDyh8pzvkFvrUGmOHBHsiW5GIFzJzlVvItSTQyyKNlBqhglDkJW36 l35RuZ+o9SfVEpIwM2nUIAoj4Qaz+IBhHPe25z+ffapxWwPj6Bx2eMsdnxjwbVhuIx65 MLnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mMmuNpdrddhrOWh+4K56L0YF6Be/7s8PGs+t3nQ9XBc=; b=RiZIQs4OWwu9m4IJjhLdOiAYiZyTlE1hsSMXQhh8y0O4aCyeK6zlP6F5KD+71WQpBX 94cLd3pxZs6R+pnPb42pIcWPWnHzZI7MA9JXB+Kyu3KgXGpkB8yRiicSsMprPYY5MfKS g3s/oI+4jM45qopXkbpQ/IH+0tAXgDo0ZcUp3kSp4JWiUTgprhrvYtEem0hKYd7EKZBE DBZVUhgXffgNFpveEzxAxoTe4l8dlTzrjgQx12yZtmaq0EO3Zb1wexeA2uMjGcB4rzBf M4120sTV426pJTJq0qYpT/zIfSx3oxR3JQpT7S92hJeJaqjxBxAQ/ZnntPGWy+/y7Hk/ RiLQ== X-Gm-Message-State: APjAAAU3Fu+qJ6qvArydgSkF5EbriArZJTCr61ZrV3Yln/wN/CTu3UGP iHtaUOe1jC84OuZ+A5WCXAs54L44Kh4xU2btrAw= X-Google-Smtp-Source: APXvYqxCY8Esw9mb9wmG/UGxD0UUKDvMB5s9SYeKowx88j1tinMMSnQmnoAJmOf7qqFYYldszD00sy05EvzJKFOoz2U= X-Received: by 2002:a2e:a553:: with SMTP id e19mr5046527ljn.64.1581576118811; Wed, 12 Feb 2020 22:41:58 -0800 (PST) MIME-Version: 1.0 References: <20200108111743.23393-1-janne.karhunen@gmail.com> <1580998432.5585.411.camel@linux.ibm.com> <40f780ffe2ddc879e5fa4443c098c0f1d331390f.camel@gmail.com> <1581366258.5585.891.camel@linux.ibm.com> <1581462616.5125.69.camel@linux.ibm.com> <6b787049b965c8056d0e27360e2eaa8fa2f38b35.camel@gmail.com> <1581555796.8515.130.camel@linux.ibm.com> In-Reply-To: <1581555796.8515.130.camel@linux.ibm.com> From: Janne Karhunen Date: Thu, 13 Feb 2020 08:41:47 +0200 Message-ID: Subject: Re: [PATCH v2] ima: export the measurement list when needed To: Mimi Zohar Cc: david.safford@gmail.com, linux-integrity@vger.kernel.org, linux-security-module , Ken Goldman , "Wiseman, Monty (GE Global Research, US)" , Amir Goldstein , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Thu, Feb 13, 2020 at 3:03 AM Mimi Zohar wrote: > > This is a pretty important new feature. > > A lot of people can't use IMA because of the memory issue. > > Also, I really think we need to let administrators choose the tradeoffs > > of keeping the list in memory, on a local file, or only on the > > attestation server, as best fits their use cases. > > Dave, I understand that some use cases require the ability of > truncating the measurement list. We're discussing how to truncate the > measurement list. For example, in addition to the existing securityfs > binary_runtime_measurements file, we could define a new securityfs > file indicating the number of records to delete. I don't have strong opinions either way, just let me know how to adapt the patch and we will get it done asap. I'd prefer a solution where the kernel can initiate the flush, but if not then not. Thanks everyone for all the help. -- Janne