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] [thread-next>] [day] [month] [year] [list]
Message-ID: <0cf1d78a-8781-e31e-00a3-3ca68af5a025@infradead.org>
Date:   Tue, 22 Nov 2022 10:56:50 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Ard Biesheuvel <ardb@...nel.org>, linux-efi@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Michael Roth <michael.roth@....com>
Subject: Re: [PATCH v3 17/17] efi: x86: Make the deprecated EFI handover
 protocol optional



On 11/22/22 08:10, Ard Biesheuvel wrote:
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 8c6da5e42d5a6c25..121f1fdca3145fd2 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1981,6 +1981,23 @@ config EFI_STUB
>  
>  	  See Documentation/admin-guide/efi-stub.rst for more information.
>  
> +config EFI_HANDOVER_PROTOCOL
> +	bool "EFI handover protocol (DEPRECATED)"
> +	depends on EFI_STUB
> +	default y
> +	help
> +	  Select this in order to include support for the deprecated EFI
> +	  handover protocol, which defines alternative entry points into the
> +	  EFI stub.  This is a practice that has no basis in the UEFI
> +	  specification, and requires a priori knowledge on the part of the
> +	  bootloader about Linux/x86 specific ways of passing the command line
> +	  and initrd, and where in memory those assets may be loaded.
> +
> +	  If in doubt, say Y. Even though he corresponding support is not

	                                  the

> +	  present in upstream GRUB or other bootloaders, most distros build
> +	  GRUB with numerous downstream patches applied, and may rely on the
> +	  handover protocol as as result.

-- 
~Randy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ