Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Feng Tian <feng.tian@intel.com>
Add support for RSA 2048 SHA 256 signing and verification encoded in a PI FFS GUIDED Encapsulation Section. The primary use case of this feature is in support of signing and verification of encapsulated FVs for Recovery and Capsule Update, but can potentially be used for signing and verification of any content that can be stored in a PI conformant FFS file. Signing operations are performed from python scripts that wrap OpenSsl command line utilities. Verification operations are performed using the OpenSsl libraries in the CryptoPkg.
The guided encapsulation sections uses the UEFI 2.4 Specification defined GUID called EFI_CERT_TYPE_RSA2048_SHA256_GUID. The data layout for the encapsulation section starts with the UEFI 2.4 Specification defined structure called EFI_CERT_BLOCK_RSA_2048_SHA256 followed immediately by the data. The signing tool included in these patches performs encode/decode operations using this data layout. HashType is set to the UEFI 2.4 Specification defined GUID called EFI_HASH_ALGORITHM_SHA256_GUID.
MdePkg/Include/Guid/WinCertificate.h
=================================
//
// WIN_CERTIFICATE_UEFI_GUID.CertType
//
#define EFI_CERT_TYPE_RSA2048_SHA256_GUID \
{0xa7717414, 0xc616, 0x4977, {0x94, 0x20, 0x84, 0x47, 0x12, 0xa7, 0x35, 0xbf } }
///
/// WIN_CERTIFICATE_UEFI_GUID.CertData
///
typedef struct {
EFI_GUID HashType;
UINT8 PublicKey[256];
UINT8 Signature[256];
} EFI_CERT_BLOCK_RSA_2048_SHA256;
MdePkg/Include/Protocol/Hash.h
=================================
#define EFI_HASH_ALGORITHM_SHA256_GUID \
{ \
0x51aa59de, 0xfdf2, 0x4ea3, {0xbc, 0x63, 0x87, 0x5f, 0xb7, 0x84, 0x2e, 0xe9 } \
}
The verification operations require the use of public key(s). A new PCD called gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer is added to the SecurityPkg that supports one or more SHA 256 hashes of the public keys. A SHA 256 hash is performed to minimize the FLASH overhead of storing the public keys. When a verification operation is performed, a SHA 256 hash is performed on EFI_CERT_BLOCK_RSA_2048_SHA256.PublicKey and a check is made to see if that hash matches any of the hashes in the new PCD. It is recommended that this PCD always be configured in the DSC file as storage type of [PcdsDynamixExVpd], so the public keys are stored in a protected read-only region.
While working on this feature, I noticed that the CRC32 signing and verification feature was incomplete. It only supported CRC32 based verification in the DXE Phase, so the attached patches also provide support for CRC32 based verification in the PEI Phase.
I also noticed that the most common method for incorporating guided section extraction libraries was to directly link them to the DXE Core, which is not very flexible. The attached patches also add a generic section extraction PEIM and a generic section extraction DXE driver that can each be linked against one or more section extraction libraries. This provides a platform developer with the option of providing section extraction services with the DXE Core or providing section extraction services with these generic PEIM/DXE Drivers.
Patch Summary
==============
1) BaseTools - Rsa2049Sha256Sign python script that can perform test signing or custom signing of PI FFS file GUIDed sections
a. Wrapper for a set of OpenSsl command line utility operations
b. OpenSsl command line tool must be installed in location that is in standard OS path or in path specified by OS environment variable called OPENSSL_PATH
c. Provides standard EDK II command line arguments for a tool that encodes/decodes guided encapsulation section
Rsa2048Sha256Sign - Copyright (c) 2013 - 2014, Intel Corporation. All rights reserved.
usage: Rsa2048Sha256Sign -e|-d [options] <input_file>
positional arguments:
input_file specify the input filename
optional arguments:
-e encode file
-d decode file
-o filename, --output filename
specify the output filename
--private-key PRIVATEKEYFILE
specify the private key filename. If not specified, a
test signing key is used.
-v, --verbose increase output messages
-q, --quiet reduce output messages
--debug [0-9] set debug level
--version display the program version and exit
-h, --help display this help text
2) BaseTools - Rsa2049Sha256GenerateKeys python script that can generate new private/public key and PCD value that is SHA 256 hash of public key using OpenSsl command line utilities.
a. Wrapper for a set of OpenSsl command line utility operations
b. OpenSsl command line tool must be installed in location that is in standard path or in path specified by OS environment variable called OPENSSL_PATH
Rsa2048Sha256GenerateKeys - Copyright (c) 2013 - 2014, Intel Corporation. All rights reserved.
usage: Rsa2048Sha256GenerateKeys [options]
optional arguments:
-o [filename [filename ...]], --output [filename [filename ...]]
specify the output private key filename in PEM format
-i [filename [filename ...]], --input [filename [filename ...]]
specify the input private key filename in PEM format
--public-key-hash PUBLICKEYHASHFILE
specify the public key hash filename that is SHA 256
hash of 2048 bit RSA public key in binary format
--public-key-hash-c PUBLICKEYHASHCFILE
specify the public key hash filename that is SHA 256
hash of 2048 bit RSA public key in C structure format
-v, --verbose increase output messages
-q, --quiet reduce output messages
--debug [0-9] set debug level
--version display the program version and exit
-h, --help display this help text
3) BaseTools\Conf\tools_def.template
a. Define GUID/Tool to perform RSA 2048 SHA 256 test signing and instructions on how to use alternate private/public key
b. GUID is EFI_CERT_TYPE_RSA2048_SHA256_GUID
c. Tool is Rsa2049Sha256Sign
4) MdeModulePkg\Library\PeiCrc32GuidedSectionExtractionLib
a. Add peer for DxeCrc32GuidedSectionExtractionLib so both PEI and DXE phases can perform basic integrity checks of PEI and DXE components
5) MdeModulePkg\Universal\SectionExtractionPei
a. Generic PEIM that can link against one or more NULL section extraction library instances to provided one or more GUIDED Section Extraction PPIs
6) MdeModulePkg\Universal\SectionExtractionDxe
a. Generic DXE Driver that can link against one or more NULL section extraction library instances to provide one or more GUIDED Section Extraction Protocols.
7) SecurityPkg\Library\PeiRsa2048Sha256GuidedSectionExtractLib
a. NULL library instances that performs PEI phase RSA 2048 SHA 256 signature verification using OpenSsl libraries from CryptoPkg.
b. Based on algorithms from SecurityPkg Authenticated Variable services
c. Uses public key from gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer.
8) SecurityPkg\Library\DxeRsa2048Sha256GuidedSectionExtractLib
a. NULL library instances that performs DXE phase RSA 2048 SHA 256 signature verification using OpenSsl libraries from CryptoPkg.
b. Based on algorithms from SecurityPkg Authenticated Variable services
c. Uses public key from gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer.
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@15799 6f19259b-4bc3-4df7-8a09-765794883524
2014-08-14 08:29:07 +02:00
|
|
|
/** @file
|
|
|
|
Section Extraction DXE Driver
|
|
|
|
|
|
|
|
Copyright (c) 2013 - 2014, Intel Corporation. All rights reserved.<BR>
|
|
|
|
This program and the accompanying materials
|
|
|
|
are licensed and made available under the terms and conditions of the BSD License
|
|
|
|
which accompanies this distribution. The full text of the license may be found at
|
|
|
|
http://opensource.org/licenses/bsd-license.php
|
|
|
|
|
|
|
|
THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
|
|
|
|
WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
|
|
|
|
|
|
|
|
**/
|
|
|
|
|
|
|
|
#include <PiDxe.h>
|
|
|
|
#include <Protocol/GuidedSectionExtraction.h>
|
|
|
|
#include <Library/DebugLib.h>
|
|
|
|
#include <Library/ExtractGuidedSectionLib.h>
|
|
|
|
#include <Library/MemoryAllocationLib.h>
|
|
|
|
#include <Library/BaseMemoryLib.h>
|
|
|
|
#include <Library/UefiBootServicesTableLib.h>
|
|
|
|
|
2014-08-19 04:44:24 +02:00
|
|
|
/**
|
|
|
|
The ExtractSection() function processes the input section and
|
|
|
|
allocates a buffer from the pool in which it returns the section
|
|
|
|
contents. If the section being extracted contains
|
|
|
|
authentication information (the section's
|
|
|
|
GuidedSectionHeader.Attributes field has the
|
|
|
|
EFI_GUIDED_SECTION_AUTH_STATUS_VALID bit set), the values
|
|
|
|
returned in AuthenticationStatus must reflect the results of
|
|
|
|
the authentication operation. Depending on the algorithm and
|
|
|
|
size of the encapsulated data, the time that is required to do
|
|
|
|
a full authentication may be prohibitively long for some
|
|
|
|
classes of systems. To indicate this, use
|
|
|
|
EFI_SECURITY_POLICY_PROTOCOL_GUID, which may be published by
|
|
|
|
the security policy driver (see the Platform Initialization
|
|
|
|
Driver Execution Environment Core Interface Specification for
|
|
|
|
more details and the GUID definition). If the
|
|
|
|
EFI_SECURITY_POLICY_PROTOCOL_GUID exists in the handle
|
|
|
|
database, then, if possible, full authentication should be
|
|
|
|
skipped and the section contents simply returned in the
|
|
|
|
OutputBuffer. In this case, the
|
|
|
|
EFI_AUTH_STATUS_PLATFORM_OVERRIDE bit AuthenticationStatus
|
|
|
|
must be set on return. ExtractSection() is callable only from
|
|
|
|
TPL_NOTIFY and below. Behavior of ExtractSection() at any
|
|
|
|
EFI_TPL above TPL_NOTIFY is undefined. Type EFI_TPL is
|
|
|
|
defined in RaiseTPL() in the UEFI 2.0 specification.
|
|
|
|
|
|
|
|
|
|
|
|
@param This Indicates the
|
|
|
|
EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL instance.
|
|
|
|
@param InputSection Buffer containing the input GUIDed section
|
|
|
|
to be processed. OutputBuffer OutputBuffer
|
|
|
|
is allocated from boot services pool
|
|
|
|
memory and contains the new section
|
|
|
|
stream. The caller is responsible for
|
|
|
|
freeing this buffer.
|
|
|
|
@param OutputBuffer *OutputBuffer is allocated from boot services
|
|
|
|
pool memory and contains the new section stream.
|
|
|
|
The caller is responsible for freeing this buffer.
|
|
|
|
@param OutputSize A pointer to a caller-allocated UINTN in
|
|
|
|
which the size of OutputBuffer allocation
|
|
|
|
is stored. If the function returns
|
|
|
|
anything other than EFI_SUCCESS, the value
|
|
|
|
of OutputSize is undefined.
|
|
|
|
|
|
|
|
@param AuthenticationStatus A pointer to a caller-allocated
|
|
|
|
UINT32 that indicates the
|
|
|
|
authentication status of the
|
|
|
|
output buffer. If the input
|
|
|
|
section's
|
|
|
|
GuidedSectionHeader.Attributes
|
|
|
|
field has the
|
|
|
|
EFI_GUIDED_SECTION_AUTH_STATUS_VAL
|
|
|
|
bit as clear, AuthenticationStatus
|
|
|
|
must return zero. Both local bits
|
|
|
|
(19:16) and aggregate bits (3:0)
|
|
|
|
in AuthenticationStatus are
|
|
|
|
returned by ExtractSection().
|
|
|
|
These bits reflect the status of
|
|
|
|
the extraction operation. The bit
|
|
|
|
pattern in both regions must be
|
|
|
|
the same, as the local and
|
|
|
|
aggregate authentication statuses
|
|
|
|
have equivalent meaning at this
|
|
|
|
level. If the function returns
|
|
|
|
anything other than EFI_SUCCESS,
|
|
|
|
the value of AuthenticationStatus
|
|
|
|
is undefined.
|
|
|
|
|
|
|
|
|
|
|
|
@retval EFI_SUCCESS The InputSection was successfully
|
|
|
|
processed and the section contents were
|
|
|
|
returned.
|
|
|
|
|
|
|
|
@retval EFI_OUT_OF_RESOURCES The system has insufficient
|
|
|
|
resources to process the
|
|
|
|
request.
|
|
|
|
|
|
|
|
@retval EFI_INVALID_PARAMETER The GUID in InputSection does
|
|
|
|
not match this instance of the
|
|
|
|
GUIDed Section Extraction
|
|
|
|
Protocol.
|
|
|
|
|
|
|
|
**/
|
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Feng Tian <feng.tian@intel.com>
Add support for RSA 2048 SHA 256 signing and verification encoded in a PI FFS GUIDED Encapsulation Section. The primary use case of this feature is in support of signing and verification of encapsulated FVs for Recovery and Capsule Update, but can potentially be used for signing and verification of any content that can be stored in a PI conformant FFS file. Signing operations are performed from python scripts that wrap OpenSsl command line utilities. Verification operations are performed using the OpenSsl libraries in the CryptoPkg.
The guided encapsulation sections uses the UEFI 2.4 Specification defined GUID called EFI_CERT_TYPE_RSA2048_SHA256_GUID. The data layout for the encapsulation section starts with the UEFI 2.4 Specification defined structure called EFI_CERT_BLOCK_RSA_2048_SHA256 followed immediately by the data. The signing tool included in these patches performs encode/decode operations using this data layout. HashType is set to the UEFI 2.4 Specification defined GUID called EFI_HASH_ALGORITHM_SHA256_GUID.
MdePkg/Include/Guid/WinCertificate.h
=================================
//
// WIN_CERTIFICATE_UEFI_GUID.CertType
//
#define EFI_CERT_TYPE_RSA2048_SHA256_GUID \
{0xa7717414, 0xc616, 0x4977, {0x94, 0x20, 0x84, 0x47, 0x12, 0xa7, 0x35, 0xbf } }
///
/// WIN_CERTIFICATE_UEFI_GUID.CertData
///
typedef struct {
EFI_GUID HashType;
UINT8 PublicKey[256];
UINT8 Signature[256];
} EFI_CERT_BLOCK_RSA_2048_SHA256;
MdePkg/Include/Protocol/Hash.h
=================================
#define EFI_HASH_ALGORITHM_SHA256_GUID \
{ \
0x51aa59de, 0xfdf2, 0x4ea3, {0xbc, 0x63, 0x87, 0x5f, 0xb7, 0x84, 0x2e, 0xe9 } \
}
The verification operations require the use of public key(s). A new PCD called gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer is added to the SecurityPkg that supports one or more SHA 256 hashes of the public keys. A SHA 256 hash is performed to minimize the FLASH overhead of storing the public keys. When a verification operation is performed, a SHA 256 hash is performed on EFI_CERT_BLOCK_RSA_2048_SHA256.PublicKey and a check is made to see if that hash matches any of the hashes in the new PCD. It is recommended that this PCD always be configured in the DSC file as storage type of [PcdsDynamixExVpd], so the public keys are stored in a protected read-only region.
While working on this feature, I noticed that the CRC32 signing and verification feature was incomplete. It only supported CRC32 based verification in the DXE Phase, so the attached patches also provide support for CRC32 based verification in the PEI Phase.
I also noticed that the most common method for incorporating guided section extraction libraries was to directly link them to the DXE Core, which is not very flexible. The attached patches also add a generic section extraction PEIM and a generic section extraction DXE driver that can each be linked against one or more section extraction libraries. This provides a platform developer with the option of providing section extraction services with the DXE Core or providing section extraction services with these generic PEIM/DXE Drivers.
Patch Summary
==============
1) BaseTools - Rsa2049Sha256Sign python script that can perform test signing or custom signing of PI FFS file GUIDed sections
a. Wrapper for a set of OpenSsl command line utility operations
b. OpenSsl command line tool must be installed in location that is in standard OS path or in path specified by OS environment variable called OPENSSL_PATH
c. Provides standard EDK II command line arguments for a tool that encodes/decodes guided encapsulation section
Rsa2048Sha256Sign - Copyright (c) 2013 - 2014, Intel Corporation. All rights reserved.
usage: Rsa2048Sha256Sign -e|-d [options] <input_file>
positional arguments:
input_file specify the input filename
optional arguments:
-e encode file
-d decode file
-o filename, --output filename
specify the output filename
--private-key PRIVATEKEYFILE
specify the private key filename. If not specified, a
test signing key is used.
-v, --verbose increase output messages
-q, --quiet reduce output messages
--debug [0-9] set debug level
--version display the program version and exit
-h, --help display this help text
2) BaseTools - Rsa2049Sha256GenerateKeys python script that can generate new private/public key and PCD value that is SHA 256 hash of public key using OpenSsl command line utilities.
a. Wrapper for a set of OpenSsl command line utility operations
b. OpenSsl command line tool must be installed in location that is in standard path or in path specified by OS environment variable called OPENSSL_PATH
Rsa2048Sha256GenerateKeys - Copyright (c) 2013 - 2014, Intel Corporation. All rights reserved.
usage: Rsa2048Sha256GenerateKeys [options]
optional arguments:
-o [filename [filename ...]], --output [filename [filename ...]]
specify the output private key filename in PEM format
-i [filename [filename ...]], --input [filename [filename ...]]
specify the input private key filename in PEM format
--public-key-hash PUBLICKEYHASHFILE
specify the public key hash filename that is SHA 256
hash of 2048 bit RSA public key in binary format
--public-key-hash-c PUBLICKEYHASHCFILE
specify the public key hash filename that is SHA 256
hash of 2048 bit RSA public key in C structure format
-v, --verbose increase output messages
-q, --quiet reduce output messages
--debug [0-9] set debug level
--version display the program version and exit
-h, --help display this help text
3) BaseTools\Conf\tools_def.template
a. Define GUID/Tool to perform RSA 2048 SHA 256 test signing and instructions on how to use alternate private/public key
b. GUID is EFI_CERT_TYPE_RSA2048_SHA256_GUID
c. Tool is Rsa2049Sha256Sign
4) MdeModulePkg\Library\PeiCrc32GuidedSectionExtractionLib
a. Add peer for DxeCrc32GuidedSectionExtractionLib so both PEI and DXE phases can perform basic integrity checks of PEI and DXE components
5) MdeModulePkg\Universal\SectionExtractionPei
a. Generic PEIM that can link against one or more NULL section extraction library instances to provided one or more GUIDED Section Extraction PPIs
6) MdeModulePkg\Universal\SectionExtractionDxe
a. Generic DXE Driver that can link against one or more NULL section extraction library instances to provide one or more GUIDED Section Extraction Protocols.
7) SecurityPkg\Library\PeiRsa2048Sha256GuidedSectionExtractLib
a. NULL library instances that performs PEI phase RSA 2048 SHA 256 signature verification using OpenSsl libraries from CryptoPkg.
b. Based on algorithms from SecurityPkg Authenticated Variable services
c. Uses public key from gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer.
8) SecurityPkg\Library\DxeRsa2048Sha256GuidedSectionExtractLib
a. NULL library instances that performs DXE phase RSA 2048 SHA 256 signature verification using OpenSsl libraries from CryptoPkg.
b. Based on algorithms from SecurityPkg Authenticated Variable services
c. Uses public key from gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer.
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@15799 6f19259b-4bc3-4df7-8a09-765794883524
2014-08-14 08:29:07 +02:00
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
|
|
|
CustomGuidedSectionExtract (
|
|
|
|
IN CONST EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL *This,
|
|
|
|
IN CONST VOID *InputSection,
|
|
|
|
OUT VOID **OutputBuffer,
|
|
|
|
OUT UINTN *OutputSize,
|
|
|
|
OUT UINT32 *AuthenticationStatus
|
|
|
|
);
|
|
|
|
|
|
|
|
//
|
|
|
|
// Module global for the Section Extraction Protocol handle
|
|
|
|
//
|
|
|
|
EFI_HANDLE mSectionExtractionHandle = NULL;
|
|
|
|
|
|
|
|
//
|
|
|
|
// Module global for the Section Extraction Protocol instance
|
|
|
|
//
|
|
|
|
EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL mCustomGuidedSectionExtractionProtocol = {
|
|
|
|
CustomGuidedSectionExtract
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
The ExtractSection() function processes the input section and
|
|
|
|
allocates a buffer from the pool in which it returns the section
|
|
|
|
contents. If the section being extracted contains
|
|
|
|
authentication information (the section's
|
|
|
|
GuidedSectionHeader.Attributes field has the
|
|
|
|
EFI_GUIDED_SECTION_AUTH_STATUS_VALID bit set), the values
|
|
|
|
returned in AuthenticationStatus must reflect the results of
|
|
|
|
the authentication operation. Depending on the algorithm and
|
|
|
|
size of the encapsulated data, the time that is required to do
|
|
|
|
a full authentication may be prohibitively long for some
|
|
|
|
classes of systems. To indicate this, use
|
|
|
|
EFI_SECURITY_POLICY_PROTOCOL_GUID, which may be published by
|
|
|
|
the security policy driver (see the Platform Initialization
|
|
|
|
Driver Execution Environment Core Interface Specification for
|
|
|
|
more details and the GUID definition). If the
|
|
|
|
EFI_SECURITY_POLICY_PROTOCOL_GUID exists in the handle
|
|
|
|
database, then, if possible, full authentication should be
|
|
|
|
skipped and the section contents simply returned in the
|
|
|
|
OutputBuffer. In this case, the
|
|
|
|
EFI_AUTH_STATUS_PLATFORM_OVERRIDE bit AuthenticationStatus
|
|
|
|
must be set on return. ExtractSection() is callable only from
|
|
|
|
TPL_NOTIFY and below. Behavior of ExtractSection() at any
|
|
|
|
EFI_TPL above TPL_NOTIFY is undefined. Type EFI_TPL is
|
|
|
|
defined in RaiseTPL() in the UEFI 2.0 specification.
|
|
|
|
|
|
|
|
|
|
|
|
@param This Indicates the
|
|
|
|
EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL instance.
|
|
|
|
@param InputSection Buffer containing the input GUIDed section
|
|
|
|
to be processed. OutputBuffer OutputBuffer
|
|
|
|
is allocated from boot services pool
|
|
|
|
memory and contains the new section
|
|
|
|
stream. The caller is responsible for
|
|
|
|
freeing this buffer.
|
|
|
|
@param OutputBuffer *OutputBuffer is allocated from boot services
|
|
|
|
pool memory and contains the new section stream.
|
|
|
|
The caller is responsible for freeing this buffer.
|
|
|
|
@param OutputSize A pointer to a caller-allocated UINTN in
|
|
|
|
which the size of OutputBuffer allocation
|
|
|
|
is stored. If the function returns
|
|
|
|
anything other than EFI_SUCCESS, the value
|
|
|
|
of OutputSize is undefined.
|
|
|
|
|
|
|
|
@param AuthenticationStatus A pointer to a caller-allocated
|
|
|
|
UINT32 that indicates the
|
|
|
|
authentication status of the
|
|
|
|
output buffer. If the input
|
|
|
|
section's
|
|
|
|
GuidedSectionHeader.Attributes
|
|
|
|
field has the
|
|
|
|
EFI_GUIDED_SECTION_AUTH_STATUS_VAL
|
|
|
|
bit as clear, AuthenticationStatus
|
|
|
|
must return zero. Both local bits
|
|
|
|
(19:16) and aggregate bits (3:0)
|
|
|
|
in AuthenticationStatus are
|
|
|
|
returned by ExtractSection().
|
|
|
|
These bits reflect the status of
|
|
|
|
the extraction operation. The bit
|
|
|
|
pattern in both regions must be
|
|
|
|
the same, as the local and
|
|
|
|
aggregate authentication statuses
|
|
|
|
have equivalent meaning at this
|
|
|
|
level. If the function returns
|
|
|
|
anything other than EFI_SUCCESS,
|
|
|
|
the value of AuthenticationStatus
|
|
|
|
is undefined.
|
|
|
|
|
|
|
|
|
|
|
|
@retval EFI_SUCCESS The InputSection was successfully
|
|
|
|
processed and the section contents were
|
|
|
|
returned.
|
|
|
|
|
|
|
|
@retval EFI_OUT_OF_RESOURCES The system has insufficient
|
|
|
|
resources to process the
|
|
|
|
request.
|
|
|
|
|
|
|
|
@retval EFI_INVALID_PARAMETER The GUID in InputSection does
|
|
|
|
not match this instance of the
|
|
|
|
GUIDed Section Extraction
|
|
|
|
Protocol.
|
|
|
|
|
|
|
|
**/
|
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
|
|
|
CustomGuidedSectionExtract (
|
|
|
|
IN CONST EFI_GUIDED_SECTION_EXTRACTION_PROTOCOL *This,
|
|
|
|
IN CONST VOID *InputSection,
|
|
|
|
OUT VOID **OutputBuffer,
|
|
|
|
OUT UINTN *OutputSize,
|
|
|
|
OUT UINT32 *AuthenticationStatus
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EFI_STATUS Status;
|
|
|
|
VOID *ScratchBuffer;
|
|
|
|
VOID *AllocatedOutputBuffer;
|
|
|
|
UINT32 OutputBufferSize;
|
|
|
|
UINT32 ScratchBufferSize;
|
|
|
|
UINT16 SectionAttribute;
|
|
|
|
|
|
|
|
//
|
|
|
|
// Init local variable
|
|
|
|
//
|
|
|
|
ScratchBuffer = NULL;
|
|
|
|
AllocatedOutputBuffer = NULL;
|
|
|
|
|
|
|
|
//
|
|
|
|
// Call GetInfo to get the size and attribute of input guided section data.
|
|
|
|
//
|
|
|
|
Status = ExtractGuidedSectionGetInfo (
|
|
|
|
InputSection,
|
|
|
|
&OutputBufferSize,
|
|
|
|
&ScratchBufferSize,
|
|
|
|
&SectionAttribute
|
|
|
|
);
|
|
|
|
|
|
|
|
if (EFI_ERROR (Status)) {
|
|
|
|
DEBUG ((DEBUG_ERROR, "GetInfo from guided section Failed - %r\n", Status));
|
|
|
|
return Status;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ScratchBufferSize > 0) {
|
|
|
|
//
|
|
|
|
// Allocate scratch buffer
|
|
|
|
//
|
|
|
|
ScratchBuffer = AllocatePool (ScratchBufferSize);
|
|
|
|
if (ScratchBuffer == NULL) {
|
|
|
|
return EFI_OUT_OF_RESOURCES;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (OutputBufferSize > 0) {
|
|
|
|
//
|
|
|
|
// Allocate output buffer
|
|
|
|
//
|
|
|
|
AllocatedOutputBuffer = AllocatePool (OutputBufferSize);
|
|
|
|
if (AllocatedOutputBuffer == NULL) {
|
|
|
|
FreePool (ScratchBuffer);
|
|
|
|
return EFI_OUT_OF_RESOURCES;
|
|
|
|
}
|
|
|
|
*OutputBuffer = AllocatedOutputBuffer;
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// Call decode function to extract raw data from the guided section.
|
|
|
|
//
|
|
|
|
Status = ExtractGuidedSectionDecode (
|
|
|
|
InputSection,
|
|
|
|
OutputBuffer,
|
|
|
|
ScratchBuffer,
|
|
|
|
AuthenticationStatus
|
|
|
|
);
|
|
|
|
if (EFI_ERROR (Status)) {
|
|
|
|
//
|
|
|
|
// Decode failed
|
|
|
|
//
|
|
|
|
if (AllocatedOutputBuffer != NULL) {
|
|
|
|
FreePool (AllocatedOutputBuffer);
|
|
|
|
}
|
|
|
|
if (ScratchBuffer != NULL) {
|
|
|
|
FreePool (ScratchBuffer);
|
|
|
|
}
|
|
|
|
DEBUG ((DEBUG_ERROR, "Extract guided section Failed - %r\n", Status));
|
|
|
|
return Status;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (*OutputBuffer != AllocatedOutputBuffer) {
|
|
|
|
//
|
|
|
|
// OutputBuffer was returned as a different value,
|
|
|
|
// so copy section contents to the allocated memory buffer.
|
|
|
|
//
|
|
|
|
CopyMem (AllocatedOutputBuffer, *OutputBuffer, OutputBufferSize);
|
|
|
|
*OutputBuffer = AllocatedOutputBuffer;
|
|
|
|
}
|
|
|
|
|
|
|
|
//
|
|
|
|
// Set real size of output buffer.
|
|
|
|
//
|
|
|
|
*OutputSize = (UINTN) OutputBufferSize;
|
|
|
|
|
|
|
|
//
|
|
|
|
// Free unused scratch buffer.
|
|
|
|
//
|
|
|
|
if (ScratchBuffer != NULL) {
|
|
|
|
FreePool (ScratchBuffer);
|
|
|
|
}
|
|
|
|
|
|
|
|
return EFI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
Main entry for the Section Extraction DXE module.
|
|
|
|
|
|
|
|
This routine registers the Section Extraction Protocols that have been registered
|
|
|
|
with the Section Extraction Library.
|
|
|
|
|
|
|
|
@param[in] ImageHandle The firmware allocated handle for the EFI image.
|
|
|
|
@param[in] SystemTable A pointer to the EFI System Table.
|
|
|
|
|
|
|
|
@retval EFI_SUCCESS The entry point is executed successfully.
|
|
|
|
@retval other Some error occurs when executing this entry point.
|
|
|
|
|
|
|
|
**/
|
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
|
|
|
SectionExtractionDxeEntry (
|
|
|
|
IN EFI_HANDLE ImageHandle,
|
|
|
|
IN EFI_SYSTEM_TABLE *SystemTable
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EFI_STATUS Status;
|
|
|
|
EFI_GUID *ExtractHandlerGuidTable;
|
|
|
|
UINTN ExtractHandlerNumber;
|
|
|
|
|
|
|
|
//
|
|
|
|
// Get custom extract guided section method guid list
|
|
|
|
//
|
|
|
|
ExtractHandlerNumber = ExtractGuidedSectionGetGuidList (&ExtractHandlerGuidTable);
|
|
|
|
|
|
|
|
//
|
|
|
|
// Install custom guided extraction protocol
|
|
|
|
//
|
|
|
|
while (ExtractHandlerNumber-- > 0) {
|
|
|
|
Status = gBS->InstallMultipleProtocolInterfaces (
|
|
|
|
&mSectionExtractionHandle,
|
|
|
|
&ExtractHandlerGuidTable [ExtractHandlerNumber], &mCustomGuidedSectionExtractionProtocol,
|
|
|
|
NULL
|
|
|
|
);
|
|
|
|
ASSERT_EFI_ERROR (Status);
|
|
|
|
}
|
|
|
|
|
|
|
|
return EFI_SUCCESS;
|
|
|
|
}
|