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: <20111007110243.05115778@lxorguk.ukuu.org.uk>
Date:	Fri, 7 Oct 2011 11:02:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
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.

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

If you want to get into a sophisticated fight with someone over hiding
the presence of a module then that's a pointless exercise.

If you want to just make it easier to sort and detect out of tree modules
then fine but the only actual pressure you have controlling its
effectiveness is going to be the embarrasment of a vendor who gets caught
out. GPG is thus I think over-engineering it somewhat.

Alan
--
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/