linux-kernel - Re: [PATCH] Add new TAINT_KSPLICE flag for when a Ksplice update has been loaded.

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-prev] [day] [month] [year] [list]

Date:	Tue, 23 Jun 2009 14:56:46 -0400 (EDT)
From:	Tim Abbott <tabbott@...lice.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Peter Zijlstra <peterz@...radead.org>,
	Jon Masters <jonathan@...masters.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Anders Kaseorg <andersk@...lice.com>,
	Jeffrey B Arnold <jbarnold@...lice.com>,
	"Waseem S. Daher" <wdaher@...lice.com>, devel@...lice.com
Subject: Re: [PATCH] Add new TAINT_KSPLICE flag for when a Ksplice update
 has been loaded.

On Mon, 22 Jun 2009, Andrew Morton wrote:
> Have the ksplice people considered using /proc/sys/kernel/tainted and
> TAINT_USER?

We're thinking about using TAINT_USER to indicate when a user has 
installed a Ksplice update that they generated on their own.  We'd like to 
be able to distinguish between the cases (1) where a user has generated a 
potentially-bad Ksplice update by providing their own naughty patch and 
(2) where a user is running binary Ksplice updates provided by a vendor 
that is taking care to use Ksplice properly.  Our patch currently uses 
TAINT_KSPLICE to indicate whether _any_ Ksplice update has been applied.

	-Tim Abbott

--
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/