linux-kernel - Re: RFC: virtualbox tainting.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <14371.1317930822@turing-police.cc.vt.edu>
Date:	Thu, 06 Oct 2011 15:53:42 -0400
From:	Valdis.Kletnieks@...edu
To:	Dave Jones <davej@...hat.com>
Cc:	Greg KH <greg@...ah.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: virtualbox tainting.

On Thu, 06 Oct 2011 15:50:07 EDT, Dave Jones said:

> I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos).
> Should I introduce a TAINT_OUT_OF_TREE perhaps instead ?

That would fix my biggest issue with the patch - it's a slippery slope.  But if
we bite the bullet and go straight to the bottom of the slope with an
OUT_OF_TREE taint, I'd be happy with that.

Is there a good way to identify at modprobe time if a module is in-tree or
out-of-tree?

Content of type "application/pgp-signature" skipped