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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20111006200652.GA22225@kroah.com>
Date:	Thu, 6 Oct 2011 13:06:52 -0700
From:	Greg KH <greg@...ah.com>
To:	Valdis.Kletnieks@...edu
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: virtualbox tainting.

On Thu, Oct 06, 2011 at 03:53:42PM -0400, Valdis.Kletnieks@...edu wrote:
> 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?

See my previous email, yes, we can do this.

greg k-h
--
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/