| 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: Fri, 7 Oct 2011 10:01:32 +0200 (CEST) From: Jiri Kosina <jkosina@...e.cz> 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, 6 Oct 2011, Dave Jones 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 ? What stops virtualbox developers from renaming the module in every release? That's the same story. The only fool-proof way of doing is indeed is the GPG-signing thing. -- Jiri Kosina SUSE Labs -- 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