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: <14168.1318003445@turing-police.cc.vt.edu>
Date:	Fri, 07 Oct 2011 12:04:05 -0400
From:	Valdis.Kletnieks@...edu
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Dave Jones <davej@...hat.com>, Greg KH <greg@...ah.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: virtualbox tainting.

On Fri, 07 Oct 2011 10:01:32 +0200, Jiri Kosina said:
> On Thu, 6 Oct 2011, Dave Jones wrote:

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

It would also be a second in-tree user for the kernel MPI library code that
somebody posted recently... Just sayin' ;)

Content of type "application/pgp-signature" skipped