linux-kernel - Re: access efi variables

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:	Fri, 13 Sep 2013 18:39:26 +0200
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Matt Fleming" <matt.fleming@...el.com>
cc:	linux-efi@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: access efi variables

On 09/13/2013 05:37 PM, Arend van Spriel wrote:
> I need to obtain a uefi variable so I went looking at the API in
> include/linux/efi.h. I found the following definition:
>
> /*
>   * The maximum size of VariableName + Data = 1024
>   * Therefore, it's reasonable to save that much
>   * space in each part of the structure,
>   * and we use a page for reading/writing.
>   */
>
> struct efi_variable {
>      efi_char16_t  VariableName[1024/sizeof(efi_char16_t)];
>      efi_guid_t    VendorGuid;
>      unsigned long DataSize;
>      __u8          Data[1024];
>      efi_status_t  Status;
>      __u32         Attributes;
> } __attribute__((packed));
>
> But according to the specs the variable I need to obtain is 2k bytes.

Maybe clarify that "the specs" is basically the feature information I 
received internally here.

> Should I expect trouble :-p
>
> Regards,
> Arend
>
> --
> 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/
>


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