lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 24 May 2017 07:04:21 -0700
From:   Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:     David Howells <dhowells@...hat.com>
Cc:     Matthew Garrett <matthew.garrett@...ula.com>,
        linux-security-module <linux-security-module@...r.kernel.org>,
        "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/5] efi: Move the x86 secure boot switch to generic code

On 24 May 2017 at 06:54, David Howells <dhowells@...hat.com> wrote:
> Ard Biesheuvel <ard.biesheuvel@...aro.org> wrote:
>
>> > +         UEFI Secure Boot provides a mechanism for ensuring that the firmware
>> > +         will only load signed bootloaders and kernels.  Secure boot mode may
>> > +         be determined from EFI variables provided by the BIOS if not
>>
>> Please replace 'the BIOS' with something more generic.
>
> "Firmware" or "System firmware" maybe?
>

Either is fine by me

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ