Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755773Ab0F3A2O (ORCPT ); Tue, 29 Jun 2010 20:28:14 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:55957 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754393Ab0F3A2M (ORCPT ); Tue, 29 Jun 2010 20:28:12 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: Steve Grubb Subject: Re: [PATCH v2] sanitize task->comm to avoid leaking escape codes Cc: kosaki.motohiro@jp.fujitsu.com, Stefani Seibold , Kees Cook , linux-kernel@vger.kernel.org, "Greg Kroah-Hartman" , Andrew Morton , Tejun Heo , Veaceslav Falico , Alexander Viro , Oleg Nesterov , Neil Horman , Roland McGrath , Ingo Molnar , Peter Zijlstra , Hidetoshi Seto , Thomas Gleixner , Eric Paris , James Morris , "Andrew G. Morgan" , Dhaval Giani , "Serge E. Hallyn" , Christoph Hellwig , linux-fsdevel@vger.kernel.org In-Reply-To: <201006292022.53834.sgrubb@redhat.com> References: <20100630084217.38F2.A69D9226@jp.fujitsu.com> <201006292022.53834.sgrubb@redhat.com> Message-Id: <20100630092432.3900.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Wed, 30 Jun 2010 09:28:08 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1514 Lines: 38 > On Tuesday, June 29, 2010 08:16:08 pm KOSAKI Motohiro wrote: > > > For the audit system, we want the real, unsanitized task->comm. We record > > > it in a special format to the audit logs such that unprintable > > > characters are included. We want it exactly this way for certification > > > purposes as well as forensic evidence if someone was playing games. If > > > you do sanitize it for other areas of the kernel, please give us a way > > > to get the unsanitized text. > > > > Probably this mail is offtopic. I think audit is unrelated with this > > discusstion. because when forensic, admins shouldn't believe task->comm > > at all. because 1) no path information, perhaps "ls" might mean > > "/home/attackers-dir/evil-script/ls" 2) easily obscured by > > prctl(PR_SET_NAME). > > No, its on-topic and we want that information unchanged. Why? I think I've described why admins should't see task->comm during forensic. Do you disagree this? or Do you have another viewpoint? Can you help us clarify your point? > > That said, audit have to logged following two point if task name is > > necessary. 1) exec > > 2) prctl(PRT_SET_NAME) > > > > Thought ? > > The audit system is capable of grabbing that information, too. ok. thanks good information :) -- 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/