linux-kernel - Re: [PATCH] Make dmi_name_in

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: <20111109142557.70cb43cb.akpm@linux-foundation.org>
Date:	Wed, 9 Nov 2011 14:25:57 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH] Make dmi_name_in_vendors more focused

On Fri, 4 Nov 2011 10:26:47 +0100
Jean Delvare <khali@...ux-fr.org> wrote:

> The current implementation of dmi_name_in_vendors() is an invitation
> to lazy coding and false positives [1]. Searching for a string in 8
> different DMI fields is something nobody should ever need to do. You
> know what you're looking for, so you should know where to look. strstr
> isn't fast, especially when it fails, so we should avoid calling it
> when it just can't succeed.
> 
> Looking at the current users of the function, it seems clear to me
> that they are looking for a system or board vendor name, so let's
> limit dmi_name_in_vendors to these two DMI fields. This much better
> matches the function name, BTW.
> 
> [1] We currently have code looking for short names in DMI data, such
> as "IBM" or "ASUS". I let you guess what will happen the day other
> vendors ship products named, for example, "SCHREIBMEISTER" or "PEGASUS".
> 
> Signed-off-by: Jean Delvare <khali@...ux-fr.org>
> Cc: Andi Kleen <andi@...stfloor.org>
> ---
> This patch was already sent on 2011-05-15. I thought Andrew had picked
> it up but apparently not, otherwise it should already be upstream by
> now.

I did merge it in May and have carried it in -mm (and hence in
linux-next) since then.  I have sent it to Jesse at least twice, with
no effect.

I'll send it to Linus for 3.3-rc1, OK?
--
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/