Comment 8 for bug 1465396

Mathieu: my goof... I thought the "Booting in insecure mode" message was actually coming from the firmware, didn't realize it was coming from shim. We confirmed that the shim package in proposed indeed fixes this behaviour.

And this also unblocks us when it comes to having a signed syslinux. We're not necessarily super attached to shipping with secure boot enabled (although we would like the option). What we are attached to is shipping UEFI systems and not having the "Booting in insecure mode" message cause customers needless concern and confusion.

Thanks for clearing this up for me, even though it took a bit for it to sink in! :D