Re: Linux Firmware Signing
From: Mimi Zohar
Date: Wed Sep 02 2015 - 19:54:40 EST
On Wed, 2015-09-02 at 01:43 +0200, Luis R. Rodriguez wrote:
> On Mon, Aug 31, 2015 at 10:18:55AM -0400, Mimi Zohar wrote:
> > On Sat, 2015-08-29 at 04:16 +0200, Luis R. Rodriguez wrote:
> > > On Thu, Aug 27, 2015 at 07:54:33PM -0400, Mimi Zohar wrote:
> > > > On Thu, 2015-08-27 at 23:29 +0200, Luis R. Rodriguez wrote:
> Right so there are different solutions to this problem, it will depend on the
> distribution and solution they have in place for this. For instance maybe some
> distros may be satisfied with the integrity of the initramfs for kexec *iff*
> they can vet for the integrity of the components that build the initramfs on
> the target system, or perhaps they distribute the initramfs used by some
> systems so they use singing facilities trusted by the kernel, or in the IMA
> case you do boot up vetting through xatrrs and IMA.
> A lot of this means a lot of these signing facilities then should be optional
> and work in a permissive mode. Part of my earlier work (already merged) on the firmware
> signing stuff was to take out from module signing code the part that let it be
> permissive with my goal to re-share the same strategy for other purposes. This
> is accomplished by using the bool_enable_only module parameter, for instance fw
> signing will use:
> +static bool sysdata_sig_enforce = IS_ENABLED(CONFIG_SYSTEM_DATA_SIG_FORCE);
> +#ifndef CONFIG_SYSTEM_DATA_SIG_FORCE
> +module_param(sysdata_sig_enforce, bool_enable_only, 0644);
> +#endif /* !CONFIG_SYSTEM_DATA_SIG_FORCE */
> Technically it should also be possible to remove the #ifndef provided we can
> all rest assured no bullets can be put through it. Anyway, that's the gist of
> the permissive model copied from module signing. If we have a lot of similar
> users it begs the question if we should somehow drivertize a generic interface
> for these things so that the actual implemenation that deals with permissivity
> is shared, its perhaps too early to do that now but something to keep in mind
> as it does sound like we will have a bit of users of the same mechanisms /
> strategy. Exactly how they need to be differentiated remains to be seen.
Ok. Each "hook" would require a separate config option to allow
flexibility. With this design, the decision for requiring signatures
would be made at build. Do we really want policy hard coded into the
kernel? (IMA is policy based.)
> > > > initramfs,
> > >
> > > Hm, what code path?
> > In addition, the files within the initramfs should be measured and
> > verified. There isn't a need for a new hook, but for xattr support in
> > CPIO. I started adding that support last winter -
> > http://lwn.net/Articles/630101/ . Others have requested other changes,
> > not related to xattrs, before bumping the CPIO magic number. There
> > should be a discussion as to what else needs to be done.
> I see, thanks. Another way to do this is to copy the module signing
> strategy and since the initramfs is linked in just peg the sinagure of the
> blog at the end. This of course would mean you have to be permissive to
> only enable folks who want this feature.
At the same time the boot loader verifies the kernel signature, it could
verify the the initramfs signature. kexec should emulate whatever the
boot loader's method for verifying the initramfs signature.
> > > > that have
> > > > been or need to be addressed. Since then, a new kexec syscall, file
> > > > descriptor based, was upstreamed that appraises the image. Until we can
> > > > preserve the measurement list across kexec,
> > >
> > > I'm sorry I do not follow, can you elaborate on what you mean by this.
> > > Its not clear to me what you mean by the measurement list. Do you mean
> > > all the above items?
> > A measurement is a hash of the file which is stored in the measurement
> > list <securityfs>/ima/ascii_runtime_measurements and is used to extend
> > the TPM (eg. PCR 10). The measurement list, in conjunction with a
> > quote of the TPM PCRs, can be used to remotely detect whether a system
> > has been compromised.
> I see thanks. In light of that its unclear why you'd want to "preserve"
> the measurement list from one boot onto another.
The TPM is reset on a hard reboot, not a soft one like kexec. Without
preserving the measurement list across kexec, we would not be able to
validate the quote.
> > > >.) Lastly, measuring/appraising policies
> > > > (eg. IMA, SELinux, Smack, iptables/ebtables)
> > >
> > > OK for each of these:
> > >
> > > how do we load the data?
> > I'm not real happy about it, but since we can't break the existing ABI
> > of loading data into the kernel via a buffer, a stop gap method of
> > signing and verifying a buffer would be needed.
> Right so if such a solution were really desirable it would seem we'd be
> wanting to change a histical approach to user <--> kernel interfaces.
> This is a pretty significant change in paradigm. Is everyone on board?
Perhaps defining a common method and converting an example or two would
make sense, before making sure "everyone" is on board. The IMA policy
could be the first. Dmitry has already added support for verifying the
policy's signature for those systems without an initramfs. I can look
into generalizing that solution.
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/