Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3879900imm; Tue, 29 May 2018 15:59:58 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL90KqAqLxvrd/rMz8IYBDQD+1yxAtNQ+N7uVEGyMH1PbtFa5uKTIyF7wzi9Zkrj630EbU0 X-Received: by 2002:a17:902:343:: with SMTP id 61-v6mr341462pld.39.1527634798187; Tue, 29 May 2018 15:59:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527634798; cv=none; d=google.com; s=arc-20160816; b=hJ9z+eR5qvBCpbNU8IJMTRtOJy7ptijTZGP3CgYgU6FVFhZxmihZYzXE6bpGPdERjs OGqGpYqezoivGseXrpP9gxd/y5bs05G2KyQ0sOL/koTDHzj9rESf8AxDwbWPwS6HNOa4 xgANELJNqt4V+aObNYMlIxqJ4v21yWHf/d2moZ0kVzR9Hk7VkeKJTk0+rUkSZ3QBwuY8 HAYDjP+8HYpeuIMUF+1SH+Q5COPHsF+rMSn2TOc7u6A/YEpwznQttgJE+2n51ZosUqQ9 PokM/Lb/SLAWIj1BNOhDS5etJXlxBZ36OpIcVG57To506yHil4U3Tqy3mQ+r9MeHETro 6GMg== 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=8+gMvyh5QssMebrahhdyYUaxzu92nSpHDGnn4F9I/AM=; b=fA3lYAw57HxnceRDum4IurRVrgRy0JBY2lABcrJzLbRLYknxw92Y3nUSc3co5xQa34 i64GZd2iDq8ZfcwFBR93wl9EYWxxFu7BfXMpnOFUSytDFw5WxslIJTcMJZK2aJN+zqzE U8Np8btJcaeIP4WiVpH4akw+IPBWUg1aQK7C7WUVlp5ng0QLylNWjYYPH9q3+8guY3Ha wj9fSN/vR3no1EqrsIn/lGK7FTkl4gwIqKatPRwEOQuMp9PVIaHDSGME6Te6wpCl5YA9 97bf6bVGl1DjjorVnZCpSVHYbi5bnpVOKqgrRTZGUhmb5BcLXLpQVL4K+3doB38s5XOw W1jg== 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 e92-v6si32795703pld.601.2018.05.29.15.59.44; Tue, 29 May 2018 15:59:58 -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 S967901AbeE2W6P (ORCPT + 99 others); Tue, 29 May 2018 18:58:15 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:53290 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S967857AbeE2W6M (ORCPT ); Tue, 29 May 2018 18:58:12 -0400 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4TMsS2g144026 for ; Tue, 29 May 2018 18:58:12 -0400 Received: from e06smtp10.uk.ibm.com (e06smtp10.uk.ibm.com [195.75.94.106]) by mx0b-001b2d01.pphosted.com with ESMTP id 2j9ewmj85y-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 29 May 2018 18:58:11 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 29 May 2018 23:58:10 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp10.uk.ibm.com (192.168.101.140) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 29 May 2018 23:58:08 +0100 Received: from d06av24.portsmouth.uk.ibm.com (d06av24.portsmouth.uk.ibm.com [9.149.105.60]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w4TMw7Xo26804288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 29 May 2018 22:58:07 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 144BD42047; Tue, 29 May 2018 23:48:40 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5CB6942041; Tue, 29 May 2018 23:48:39 +0100 (BST) Received: from dhcp-9-2-54-219.watson.ibm.com (unknown [9.2.54.219]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 29 May 2018 23:48:39 +0100 (BST) Subject: Re: [PATCH 5/8] integrity: Add exe= and tty= before res= to integrity audits From: Mimi Zohar To: Paul Moore , Steve Grubb , Stefan Berger Cc: linux-integrity@vger.kernel.org, linux-audit@redhat.com, linux-kernel@vger.kernel.org Date: Tue, 29 May 2018 18:58:06 -0400 In-Reply-To: References: <20180524201105.3179904-1-stefanb@linux.vnet.ibm.com> <20180524201105.3179904-6-stefanb@linux.vnet.ibm.com> <4331521.GQBdaJNAj6@x2> 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: 8bit X-TM-AS-GCONF: 00 x-cbid: 18052922-0040-0000-0000-0000043F15A1 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18052922-0041-0000-0000-0000264466AF Message-Id: <1527634686.3534.27.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-05-29_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=3 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-1805290243 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-05-29 at 17:47 -0400, Paul Moore wrote: > On Tue, May 29, 2018 at 5:35 PM, Steve Grubb wrote: > > On Tuesday, May 29, 2018 5:19:39 PM EDT Paul Moore wrote: > >> On Thu, May 24, 2018 at 4:11 PM, Stefan Berger > >> > >> wrote: > >> > Use the new public audit functions to add the exe= and tty= > >> > parts to the integrity audit records. We place them before > >> > res=. > >> > > >> > Signed-off-by: Stefan Berger > >> > Suggested-by: Steve Grubb > >> > --- > >> > > >> > security/integrity/integrity_audit.c | 2 ++ > >> > 1 file changed, 2 insertions(+) > >> > > >> > diff --git a/security/integrity/integrity_audit.c > >> > b/security/integrity/integrity_audit.c index db30763d5525..8d25d3c4dcca > >> > 100644 > >> > --- a/security/integrity/integrity_audit.c > >> > +++ b/security/integrity/integrity_audit.c > >> > @@ -56,6 +56,8 @@ void integrity_audit_msg(int audit_msgno, struct inode > >> > *inode,> > >> > audit_log_untrustedstring(ab, inode->i_sb->s_id); > >> > audit_log_format(ab, " ino=%lu", inode->i_ino); > >> > > >> > } > >> > > >> > + audit_log_d_path_exe(ab, current->mm); > >> > + audit_log_tty(ab, current); > >> > >> NACK > >> > >> Please add the new fields to the end of the audit record, thank you. > > > > Let's see what an example event looks like before NACK'ing this. Way back in > > 2013 the IMA events were good. I think this is repairing the event after some > > drift. > > Can you reference a specific commit, or point in time during 2013? > Looking at the git log quickly, if I go back to commit d726d8d719b6 > ("integrity: move integrity_audit_msg()") from March 18, 2013 (the > commit that created integrity_audit.c) the field ordering appears to > be the same as it today. > > My NACK still stands. There hasn't been any changes up to now.  This patch set refactors integrity_audit_msg(), creating integrity_audit_msg_common(), which will be called from both ima_audit_measurement() and ima_parse_rule().  Previously the audit record generated by ima_parse_rule() did not include this info.  The change in this patch will affect both the existing and the new INTEGRITY_AUDIT_POLICY_RULE audit records. Mimi