Re: Linux Firmware Signing
From: Luis R. Rodriguez
Date: Thu Aug 27 2015 - 15:37:11 EST
On Thu, Aug 27, 2015 at 11:38:58AM +0100, David Howells wrote:
> Luis R. Rodriguez <mcgrof@xxxxxxxx> wrote:
> > "PKCS#7: Add an optional authenticated attribute to hold firmware name"
> > https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/commit/?h=fwsign-pkcs7&id=1448377a369993f864915743cfb34772e730213good
> > 126.96.36.199.4.1.2312.16 Linux kernel
> > 188.8.131.52.4.1.2312.16.2 - PKCS#7/CMS SignerInfo attribute types
> > 184.108.40.206.4.1.23220.127.116.11 - firmwareName
> > I take it you are referring to this?
> > If we follow this model we'd then need something like:
> > 18.104.22.168.4.1.2322.214.171.124 - seLinuxPolicyName
> > That should mean each OID that has different file names would need to be
> > explicit about and have a similar entry on the registry. I find that pretty
> > redundant and would like to avoid that if possible.
> firmwareName is easy for people to understand - it's the name the kernel asks
> for and the filename of the blob. seLinuxPolicyName is, I think, a lot more
> tricky since a lot of people don't use SELinux, and most that do don't
> understand it (most people that use it aren't even really aware of it).
> If you can use the firmwareName as the SELinux/LSM key, I would suggest doing
> so - even if you dress it up as a path (/lib/firmware/<firmwareName>).
It seems we don't have to worry about it now, and perhaps SELinux folks might
go another route.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/