Re: Linux Firmware Signing
From: David Woodhouse
Date: Thu Aug 27 2015 - 08:04:14 EST
> Luis R. Rodriguez <mcgrof@xxxxxxxx> wrote:
>> "PKCS#7: Add an optional authenticated attribute to hold firmware name"
>> 22.214.171.124.4.1.2312.16 Linux kernel
>> 126.96.36.199.4.1.2312.16.2 - PKCS#7/CMS SignerInfo attribute types
>> 188.8.131.52.4.1.23184.108.40.206 - firmwareName
>> I take it you are referring to this?
>> If we follow this model we'd then need something like:
>> 220.127.116.11.4.1.2318.104.22.168 - 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
>> redundant and would like to avoid that if possible.
> firmwareName is easy for people to understand - it's the name the kernel
> for and the filename of the blob. seLinuxPolicyName is, I think, a lot
> 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
> so - even if you dress it up as a path (/lib/firmware/<firmwareName>).
In conversation with Mimi last week she was very keen on the model where
we load modules & firmware in such a fashion that the kernel has access to
the original inode -- by passing in a f2f, or in the firmware case by
doing the rd lookup directly. So surely you have all the SELinux labelling
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/