linux-kernel - Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1212143919.29244.9.camel@shinybook.infradead.org>
Date:	Fri, 30 May 2008 13:38:38 +0300
From:	David Woodhouse <dwmw2@...radead.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Greg KH <greg@...ah.com>, Yinghai Lu <yhlu.kernel@...il.com>,
	Matthew Wilcox <matthew@....cx>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	James.Bottomley@...senpartnership.com,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the
	kernel.

On Fri, 2008-05-30 at 10:20 +0100, Alan Cox wrote:
> > Not all firmware has the ability to check the version :(
> > 
> > So while Arjan's goal would be nice, Matthew is right, this can't happen
> > for all types of firmware.
> 
> Well for loaded or packaged firmware it can happen. Just stick a revision
> number on the start of the firmware file and check it rather than load it
> into the hardware in that specific driver.

Or append it to the name of the firmware file, in some cases.

-- 
dwmw2

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