linux-kernel - [PATCH] security: TOMOYO should clean policy files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F3ACCE2.6040200@xenotime.net>
Date:	Tue, 14 Feb 2012 13:06:42 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Kentaro Takeda <takedakn@...data.co.jp>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	tomoyo-dev-en@...ts.sourceforge.jp,
	James Morris <jmorris@...ei.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH] security: TOMOYO should clean policy files

From: Randy Dunlap <rdunlap@...otime.net>

TOMOYO creates some empty/default policy files during build.
It should remove them during 'make clean'.

I noticed that they were not being removed because the
"Creating ..." messages always occurred a maximum of one time
during 25 randconfig builds, so it was sometimes using the
files from a previous build (which is not a problem, but
still, 'make clean' should remove them).

Signed-off-by: Randy Dunlap <rdunlap@...otime.net>
Cc:	Kentaro Takeda <takedakn@...data.co.jp>
Cc:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:	tomoyo-dev-en@...ts.sourceforge.jp
---
 security/tomoyo/Makefile |    2 ++
 1 file changed, 2 insertions(+)

--- linux-next-20120214.orig/security/tomoyo/Makefile
+++ linux-next-20120214/security/tomoyo/Makefile
@@ -46,3 +46,5 @@ $(obj)/builtin-policy.h: $(obj)/policy/p
 	@mv $@...p $@
 
 $(obj)/common.o: $(obj)/builtin-policy.h
+
+clean-dirs := $(objtree)/security/tomoyo/policy/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/