linux-kernel - Re: [PATCH 00/18] firmware: moving drivers to request

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]

Date:	Thu, 05 Jun 2008 17:01:41 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware()

David Woodhouse wrote:
> On Thu, 2008-06-05 at 16:12 -0400, Jeff Garzik wrote:
>> Well, I should ask, is this purely an internal build detail?
>>
>> The developer (and user) should never ever see a .ihex file, outside of 
>> an active kernel compile.  Wrapping the original firmware makes it more 
>> difficult to verify, compare and/or change.  In-tree, we should see the 
>> vendor firmware blobs as shipped, with no wrapping or modification or 
>> anything.
> 
> It's a build-and-shipping detail, at least in the kernel source tree.
> 
> Rather than putting binary blobs into git (which admittedly we could,
> but it's suboptimal), we just run them through 'objcopy -Oihex' first.
> 
> It's not 'wrapped'; it's not any more difficult to verify, compare or
> change.

If the sha1 sum of what is in the kernel tree differs from what the 
vendor provided, then it is OBVIOUSLY more difficult to verify that you 
have the original firmware as provided by the vendor.

Put the binary blobs into the git tree, __without modification or 
wrapping__.

	Jeff



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