Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4924329imm; Wed, 30 May 2018 15:01:47 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIZrfjRhwmLJsrA6TPY5mSzNiFeoRLAtwx/8IdsZboCKED/ex9/EP1N6c+HYuYzdzap51hG X-Received: by 2002:a63:745a:: with SMTP id e26-v6mr3420416pgn.377.1527717706972; Wed, 30 May 2018 15:01:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527717706; cv=none; d=google.com; s=arc-20160816; b=eItgLk7emjrGPtZNse6w1e7Szqtem3TtSga9u5vgfX3ZsZ+GzwoOSuxNfzZAVdzg0R 75sSI3udzx3hO6MEjMFEOpUxbf4+DBN317Lyd507xYwvgJt0gNtmUJU9fm91z7KLBpsD kB+pVSkBHfZorSDtCXn4cpi6UR/jtjVNxwZOGfbEaiU/GdOtpFkoJ3na8mkiQd7QKsaF 8PHlomKmWUZ4rQ0j71IbF2VJTm8jabeRu/dDlxQX+93GvIv7CSJHXBdHHWXGMX53hDrq nsB1s8yaf1tlEo/BAZ7ixHXhRRfZb4jaSRVBGVkAvNK7Xx8bgZi4dnh0LpddubtsNG7/ /qew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject :arc-authentication-results; bh=bbNROGKf3VsumYpL5FphCeQE/eQ4aMsTpczXKHNEH6U=; b=v+Ihc9Kh45HmVRJW+U9VCtPbJbilZMb1q0z+7QA83oTB8tKRhyuvChU489YumJzPy6 b4hxLL67OvqUhrmMpgaD+0pgCWVzFwgVNmi+DuY/YNTE74atp+olai08Uwdi8n32Dc7E 7U3tONd0i8ce50jKklATsOAALh1BH4TK0XRieGNV72WRMp9/PQOTS1dldQRzJlkN/KmD 6JACiOoxPaQwtaTT3N4ePxUCJTYITgn5eip76QJiAsVrf+yOoHxXkjVUDhWq0xHdPR8+ 4whhvsk7JH2Fs78pZ7Xx1hbg/21wxQfyWt/MvvGDWnMDTHTYz1i9JgyVwRE71yteSXgh eyDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k18-v6si35942542pfe.13.2018.05.30.15.01.32; Wed, 30 May 2018 15:01:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932513AbeE3WAu (ORCPT + 99 others); Wed, 30 May 2018 18:00:50 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:54078 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932222AbeE3WAt (ORCPT ); Wed, 30 May 2018 18:00:49 -0400 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4ULwc1L034555 for ; Wed, 30 May 2018 18:00:47 -0400 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0a-001b2d01.pphosted.com with ESMTP id 2ja0de33t0-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 30 May 2018 18:00:46 -0400 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 30 May 2018 23:00:44 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp04.uk.ibm.com (192.168.101.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 30 May 2018 23:00:41 +0100 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w4UM0eAX23986192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 30 May 2018 22:00:40 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 19535A4055; Wed, 30 May 2018 22:51:51 +0100 (BST) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E860DA406B; Wed, 30 May 2018 22:51:49 +0100 (BST) Received: from localhost.localdomain (unknown [9.80.108.143]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 30 May 2018 22:51:49 +0100 (BST) Subject: Re: [PATCH 8/8] ima: Differentiate auditing policy rules from "audit" actions From: Mimi Zohar To: Stefan Berger , Paul Moore Cc: Steve Grubb , linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, linux-audit@redhat.com Date: Wed, 30 May 2018 18:00:28 -0400 In-Reply-To: <85d2a40a-884c-c63d-50f6-024f7bbea4a8@linux.vnet.ibm.com> References: <20180524201105.3179904-1-stefanb@linux.vnet.ibm.com> <15281606.YptaXzsEVL@x2> <00f66ee1-7494-8249-f148-688616deca0c@linux.vnet.ibm.com> <3607733.4k8ofLVAdP@x2> <1160afb4-4184-b30c-5f67-c21536b5f7d3@linux.vnet.ibm.com> <85d2a40a-884c-c63d-50f6-024f7bbea4a8@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18053022-0016-0000-0000-000001D62191 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18053022-0017-0000-0000-0000322896BD Message-Id: <1527717628.3534.79.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-05-30_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805300233 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-05-30 at 17:49 -0400, Stefan Berger wrote: > > So the other choice is to only keep patches 1,2, 6, and 7, so leave most > of the integrity audit messages untouched. Then only create a different > format for the new AUDIT_INTEGRITY_POLICY_RULE (current 8/8) that shares > (for consistency reasons) the same format with the existing integrity > audit messages but also misses tty= and exe= ? Another option would be for the new AUDIT_INTEGRITY_POLICY_RULE to call audit_log_task_info() similar to what ima_audit_measurement() does. Mimi