| 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
| ||
|
Date: Thu, 6 Oct 2011 16:04:40 -0400 From: Dave Jones <davej@...hat.com> To: Greg KH <greg@...ah.com> Cc: Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: RFC: virtualbox tainting. On Thu, Oct 06, 2011 at 12:58:24PM -0700, Greg Kroah-Hartman wrote: > > I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos). > > Should I introduce a TAINT_OUT_OF_TREE perhaps instead ? > > We could do that in a "generic" way by setting a "in-tree" flag type > thing for everything that is built from within the kernel build, and > then taint if that flag is not found. what stops an out of tree module from setting that flag ? I guess I need to see the implementation to understand this. Dave -- 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/
Powered by blists - more mailing lists