[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACdnJutpJa3nnH0Cs=x-=+GYp+9R5ZJkREhd7DvwDcmyjufSHA@mail.gmail.com>
Date: Fri, 16 Feb 2018 19:51:27 +0000
From: Matthew Garrett <mjg59@...gle.com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: pjones@...hat.com, joe.konno@...ux.intel.com, bp@...en8.de,
mingo@...nel.org, luto@...nel.org,
linux-efi <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jk@...abs.org, ak@...ux.intel.com, tony.luck@...el.com,
benjamin.drung@...fitbricks.com
Subject: Re: [PATCH 0/2] efivars: reading variables can generate SMIs
On Fri, Feb 16, 2018 at 11:31 AM Ard Biesheuvel <ard.biesheuvel@...aro.org>
wrote:
> This is why I was leaning towards applying these patches: not breaking
> userland is an important rule, but it does not imply every aspect of
> behavior observable by userland is set in stone. In other words, I
> agree with Peter that making this change does not *break* userland in
> a way anyone is likely to care deeply about.
In some modes tpmtotp will run as non-root and expect to be able to read an
EFI variable.
Powered by blists - more mailing lists