linux-kernel - Re: New format Intel microcode...

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <460789E0.1000600@linux.intel.com>
Date:	Mon, 26 Mar 2007 01:52:48 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Marcel Holtmann <marcel@...tmann.org>
CC:	Shaohua Li <shaohua.li@...el.com>,
	Daniel J Blueman <daniel.blueman@...il.com>,
	jamagallon@....com, tigran@...azian.fsnet.co.uk,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: New format Intel microcode...

Marcel Holtmann wrote:
> that is the whole point. The slash was never meant to be used. It was
> designed to take a filename or a pattern that will be later matched by
> userspace. However some developers are now trying to abuse this since
> the simple firmware helper script matches this directly to a filename
> (and directory in this case) on the disk.
> 
> Putting a slash in the request_firmware() call now enforces a
> subdirectory 

I don't see how this follows from the former. Userspace is free to 
translate the kernel string into anything it wants, even a simple 
replacement of / with _. So I don't see how this "enforces" a 
subdirectory. Firmware gets a namespace basically, and a / is a 
logical namespace separator.
-
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/