linux-kernel - Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter to efi_storage

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]

Date:	Mon, 11 Nov 2013 17:52:59 +0900
From:	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
To:	Matt Fleming <matt@...sole-pimps.org>
CC:	Richard Weinberger <richard@....at>, <linux-efi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <matt.fleming@...el.com>,
	<matthew.garrett@...ula.com>, <jlee@...e.com>
Subject: Re: [PATCH] x86, efi: change name of efi_no_storage_paranoia parameter
 to efi_storage_paranoia

Hi Matt,

I uses FUJITSU's x86 box.
This does not become bricked even if I use all efi variable storage.
Thus I want a way to not need to specify efi_no_storage_paranoia
parameter.

Thanks,
Yasuaki Ishimatsu


(2013/11/08 23:34), Matt Fleming wrote:
> On Fri, 08 Nov, at 07:32:51PM, Yasuaki Ishimatsu wrote:
>>> Everything started with an issue that killed Samsung laptops:
>>> http://mjg59.dreamwidth.org/22855.html
>>>
>>> Later it was found that if you write too much into UEFI variables many
>>> UEFI implementations will do bad things.
>>
>> Thanks for the information.
>> I will read it.
>
> Out of curiosity, what hardware are you using?
>


--
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/