linux-kernel - Re: [PATCH] firmware: Automatically pull missing FW files

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:	Thu, 21 Aug 2014 09:31:33 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Tadeusz Struk <tadeusz.struk@...el.com>
Cc:	David Woodhouse <dwmw2@...radead.org>, linux-firmware@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: Automatically pull missing FW files

On Wed, 20 Aug 2014, Tadeusz Struk wrote:
> What for? The point is that you don't have the FW binary file and you
> have to download it, which can happen automatically and this is what
> this patch does. The director where it will be stored doesn't really
> matter here.

"git pull" will at least tell you something is seriously wrong (if you know
the firmware tree should never require a forced update, that is).

I'd really appreciate if the firmware tree had signed tags or signed
commits, though.  Those at least provide decent end-to-end security (both at
rest, and while in transit) for data once it has been "git push"'d.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/