linux-kernel - Re: show all modules which taint the kernel ?

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] [day] [month] [year] [list]

Date:	Sun, 17 Sep 2006 18:06:45 +0100
From:	Alistair John Strachan <s0348365@....ed.ac.uk>
To:	devzero@....de
Cc:	Dave Jones <davej@...hat.com>, Lee Revell <rlrevell@...-job.com>,
	linux-kernel@...r.kernel.org
Subject: Re: show all modules which taint the kernel ?

On Sunday 17 September 2006 10:34, devzero@....de wrote:
> if there is a "contaminant" inside the kernel, why should one see this only
> when it`s being inserted (i.e. usually at boot time) ?
>
> i don`t know about the "nvidia(P)..." thing, but i would find it really
> useful to be able to easily distinguish between the "good" and the "not
> belonging to this kernel" modules.
>
> i have seem several discussions about "modules which taint the kernel are
> evil" - so why not pillory them by listing appropriate information with
> lsmod ?

I think the point being made is that we don't want to confuse this with 
vendors disclaiming support for non-shipped kernel modules. Vanilla kernels 
shouldn't consider GPL modules to be "unsupported" just because they aren't 
shipped or "digitally signed"; however we certainly should be highlighting 
the use of proprietary modules (which are obviously impossible to debug).

I agree with Lee, there should be some more black marks on proprietary drivers 
than there are currently.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
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/