APPLIED: Signed module enforcement patches for

[Tim Gardner]

On 06/17/2016 05:55 AM, Mathieu Trudel-Lapierre wrote:
> 
> 
> On Fri, Jun 17, 2016 at 2:30 PM, Tim Gardner <tim.gardner at canonical.com
> <mailto:tim.gardner at canonical.com>> wrote:
> 
>     Applied with CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=n
> 
> 
> What does this mean?
> Where did you apply this?
> 
> Is this in accordance with what was discussed by email and in person
> (me, Steve, Andy) today?
> 

Applied to Trusty, LTS-Utopic, Vivid, and Wily. With enforcement
disabled this patch set should have no functional impact (which is what
I'm wanting to test). There is new code that accesses UEFI, but the
results are discarded until such time as
CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y.

-- 
Tim Gardner tim.gardner at canonical.com