linux-kernel - Re: [PATCH 5/5] efi: Capsule update support and pstore backend

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: <20131016201416.GG7456@tassilo.jf.intel.com>
Date:	Wed, 16 Oct 2013 13:14:16 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tony Luck <tony.luck@...el.com>,
	Seiji Aguchi <seiji.aguchi@....com>, x86@...nel.org,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH 5/5] efi: Capsule update support and pstore backend

> +	  It should be noted that enabling this opton will pass a capsule
> +	  to the firmware on every boot. Some firmware will not allow a
> +	  user to enter the BIOS setup when a capsule has been registered
> +	  on the previous boot.

That sounds like a problem. Can this be fixed to only do it on demand?

> +
> +	  Many EFI machines have buggy implementations of the UpdateCapsule()
> +	  runtime service. This option will enable code that may not function
> +	  correctly with your firmware.

Do we need white/black lists? 

Controlling such things form CONFIG is not very good.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/