From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH v2] security: Yama LSM Date: Wed, 23 Jun 2010 17:34:08 +0200 Message-ID: <20100623153408.GA15787@basil.fritz.box> References: <20100623065236.GH5876@outflux.net> <877hlqas9e.fsf@basil.nowhere.org> <20100623145437.GJ5876@outflux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andi Kleen , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Kees Cook Return-path: Content-Disposition: inline In-Reply-To: <20100623145437.GJ5876@outflux.net> Sender: linux-security-module-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Jun 23, 2010 at 07:54:37AM -0700, Kees Cook wrote: > Oh, er, I actually added these configs because Eric Paris recommended them > as handy for distributions. I'm fine with dropping them, but will I be Distributions should use init scripts for that imho. > asked to add them back later? And what about the case of CONFIG_SYSCTL > being unset? "depends on SYSCTL" > > > However the help texts are useful, these should be in the sysctl > > documentatin in Documentation instead. > > I documented the sysctls in Documentation/Yama.txt (where SELinux.txt and > Smack.txt live) should I create an additional file in Documentation/sysctl/ > with that information (moved from Yama.txt) or move Yama.txt there? Ok missed that. what you prefer. > I actually think this is a flaw in get_task_comm. (Though actually it's > the fault of terminals if they process dangerous escape sequences. Worst > case tends to just be confusing output, but that's not important -- > nothing should spew non-printables regardless.) Would a patch to > get_task_comm be accepted to replace non-printables with "?" or something > when filling the buffer? Probably makes sense, although you might annoy someone who wants Kanji process names in UTF-8 or similar. -Andi -- ak@linux.intel.com -- Speaking for myself only.