From: Matt Fleming <matt@codeblueprint.co.uk>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@coreos.com>,
Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH] Add fwupdate and Mok GUID's to the EFI variable immutable whitelist
Date: Wed, 23 Mar 2016 21:07:45 +0000 [thread overview]
Message-ID: <20160323210745.GJ11676@codeblueprint.co.uk> (raw)
In-Reply-To: <56F20129.9020202@dell.com>
On Tue, 22 Mar, at 09:36:25PM, Mario Limonciello wrote:
>
> Actually, I think this patch should be discarded unless there is a
> desire to make the kernel work with older userspace tools.
>
> I later realized that efivar 0.22 will actually handle working with
> immutable variables properly. This means that mokutil 0.2 won't work
> with this kernel commit, but mokutil 0.3 which uses efivar
> (https://github.com/lcp/mokutil/commit/7b49e834284659527c9f7cf554f223748c00564b)
> should work properly.
>
> fwupdate works properly in most instances except for an install time
> cleanup script that removes stale variables. This is fixed with a
> trivial change:
> https://github.com/rhinstaller/fwupdate/pull/50/commits/535d3a0f9c096d452cc7e2b5be79cf964e2d6d5b
Indeed. Given that the kernel patch works around such a serious
problem, I'm inclined to encourage distributions to upgrade mokutil
and fwupdate.
prev parent reply other threads:[~2016-03-23 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 21:37 [PATCH] Add fwupdate and Mok GUID's to the EFI variable immutable whitelist Mario Limonciello
2016-03-23 2:36 ` Mario Limonciello
2016-03-23 21:07 ` Matt Fleming [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160323210745.GJ11676@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mjg59@coreos.com \
--cc=pjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox