On Sat, 23 Mar 2019 18:05:23 +0000 Steve McIntyre <st...@einval.com> wrote:
> I'm hoping that our current set of packages will fix this bug, as > we've moved to a much newer upstream version of shim which includes > the commit you point at. Once we have our new shim signed with the > Microsoft CA, could you retry your test and confirm please? I just checked shim-signed=1.30+15+1533136590.3beb971-5 from unstable. The bug was fixed. Thanks a lot!