Received: by 10.213.65.68 with SMTP id h4csp253183imn; Tue, 13 Mar 2018 03:17:41 -0700 (PDT) X-Google-Smtp-Source: AG47ELtQ9FIZtLD7mkDW2yGOppvtoJ3JM3i/1zWR5ZDlaVWRnS3KeEQMD9O1Pku2hYVEmEkG9UYv X-Received: by 10.98.8.219 with SMTP id 88mr80499pfi.4.1520936261061; Tue, 13 Mar 2018 03:17:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1520936261; cv=none; d=google.com; s=arc-20160816; b=UCm34u70AsUgvp1kxpoGQTag59OxPN5S2Ls5aS+3jFmFNLEX9KCLeD0fL/FHIw28MT fdjcmuu5WExM6ZfeDe0vewe5ssQhU6TqMgo+B+vUUMvdV69LqyN1Cc4ZkXDRpoJE/qox lBtklXHvIJ98pCidCaPFpVAJewzczIT7kQcZLaEm2Dd849AQyohnuYWJneq9VU7j+MKC XRNBfM50j0ZxShh3YSV3bZV7eVS633xFywNZEgJlYiYhoJ2BdvPAp26sCUvmdnLgQ9zH E6vV02itHiWMLjjku9Bn5fTb4hr2DJBninGT7SBpA+mMROgLH6Y7LKYCCzAzzPCUEieg llLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=vol8O9Hh4c8E4Ow6qMqWWy5IC3w1PaxER8UmaUhkqHg=; b=nQBD5lmrt7H4VtM9SJCvpa6lGKQD5Y4b3mSavBpi/yn1veEoCiePFsdhf+MHQLQX0d BgnBJ3/WlFxUsTdCS6vxzXN4+mjGKiXc6mx50eCrMSimEh2iq2BQSwE9Kyjen/CthzGQ QI6Pr5xgs3OqgtP9r7Aaf6uEZZYN9+6+MMMB861jyvHU6hJeTJRgDveK0fJehXD94aZj 3vd0CNtT30bG4tAkvDaKPgDzsFGNaZ0V+bhtcVAn7VBWXFjnJAJxz3nIaXP0HxVOR8oA Cr5Ym9P3O13Lh6luPlIPVFupQDPXJEB+dKbIsnBm0glsOsrTYpZ4+RuMzLuS/m1YZgtZ ewwQ== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s16-v6si7725240plk.550.2018.03.13.03.17.26; Tue, 13 Mar 2018 03:17:41 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932612AbeCMKP4 (ORCPT + 99 others); Tue, 13 Mar 2018 06:15:56 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:48808 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932521AbeCMKPz (ORCPT ); Tue, 13 Mar 2018 06:15:55 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9B1E44023BB3 for ; Tue, 13 Mar 2018 10:15:54 +0000 (UTC) Received: from madcap2.tricolour.ca (ovpn-112-12.rdu2.redhat.com [10.10.112.12]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 712217C5D; Tue, 13 Mar 2018 10:15:49 +0000 (UTC) Date: Tue, 13 Mar 2018 06:11:08 -0400 From: Richard Guy Briggs To: Steve Grubb Cc: Linux-Audit Mailing List , LKML Subject: Re: [PATCH ghak21 V2 3/4] audit: add refused symlink to audit_names Message-ID: <20180313101108.s6o7jec57rsxpsmc@madcap2.tricolour.ca> References: <20180312152614.qvcxng3biug46lms@madcap2.tricolour.ca> <20180312155256.4j7uglv7jiyppozm@madcap2.tricolour.ca> <20180313093517.28c99b48@ivy-bridge> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180313093517.28c99b48@ivy-bridge> User-Agent: NeoMutt/20171027 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Tue, 13 Mar 2018 10:15:54 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.7]); Tue, 13 Mar 2018 10:15:54 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'rgb@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-03-13 09:35, Steve Grubb wrote: > On Mon, 12 Mar 2018 11:52:56 -0400 > Richard Guy Briggs wrote: > > > On 2018-03-12 11:53, Paul Moore wrote: > > > On Mon, Mar 12, 2018 at 11:26 AM, Richard Guy Briggs > > > wrote: > > > > On 2018-03-12 11:12, Paul Moore wrote: > > > >> On Mon, Mar 12, 2018 at 2:31 AM, Richard Guy Briggs > > > >> wrote: > > > >> > Audit link denied events for symlinks had duplicate PATH > > > >> > records rather than just updating the existing PATH record. > > > >> > Update the symlink's PATH record with the current dentry and > > > >> > inode information. > > > >> > > > > >> > See: https://github.com/linux-audit/audit-kernel/issues/21 > > > >> > Signed-off-by: Richard Guy Briggs > > > >> > --- > > > >> > fs/namei.c | 1 + > > > >> > 1 file changed, 1 insertion(+) > > > >> > > > >> Why didn't you include this in patch 4/4 like I asked during the > > > >> previous review? > > > > > > > > Please see the last comment of: > > > > https://www.redhat.com/archives/linux-audit/2018-March/msg00070.html > > > > > > Yes, I just saw that ... I hadn't seen your replies on the v1 > > > patches until I had finished reviewing v2. I just replied to that > > > mail in the v1 thread, but basically you need to figure out what is > > > necessary here and let us know. If I have to figure it out it > > > likely isn't going to get done with enough soak time prior to the > > > upcoming merge window. > > > > Steve? I was hoping you could chime in here. > > If the CWD record will always be the same as the PARENT record, then we > do not need the parent record. Duplicate information is bad. Like all > the duplicate SYSCALL information. The CWD record could be different from the PARENT record, since I could have SYMLINK=/tmp/test/symlink, CWD=/tmp, PARENT=/tmp/test. Does the parent record even matter since it might not be a directory operation like creat, unlink or rename? > -Steve > > > I'd just include it for completeness unless Steve thinks it will stand > > on its own and doesn't want the overhead. > > > > > >> > diff --git a/fs/namei.c b/fs/namei.c > > > >> > index 50d2533..00f5041 100644 > > > >> > --- a/fs/namei.c > > > >> > +++ b/fs/namei.c > > > >> > @@ -945,6 +945,7 @@ static inline int may_follow_link(struct > > > >> > nameidata *nd) if (nd->flags & LOOKUP_RCU) > > > >> > return -ECHILD; > > > >> > > > > >> > + audit_inode(nd->name, nd->stack[0].link.dentry, 0); > > > >> > audit_log_link_denied("follow_link", > > > >> > &nd->stack[0].link); return -EACCES; > > > >> > } > > > >> > > > >> paul moore > > > > > > > > - RGB > > > > > > paul moore > > > > - RGB - RGB -- Richard Guy Briggs Sr. S/W Engineer, Kernel Security, Base Operating Systems Remote, Ottawa, Red Hat Canada IRC: rgb, SunRaycer Voice: +1.647.777.2635, Internal: (81) 32635