Filter
Top Products
Extensible Firmware Interface Specification
15-88 12/01/02 Version 1.10
Related Definitions
//**********************************************************
// Manifest Syntax
//**********************************************************
The Signed Manifest consists of three parts grouped together into an Electronic Shrink Wrap
archive as described in [SM spec]: a manifest file, a signer’s information file, and a signature
block file. These three parts, along with examples are described in the following sections. In
these examples, text in parentheses is a description of the text that would appear in the signed
manifest. Text outside of parentheses must appear exactly as shown. Also note that manifest
files and signer’s information files must conform to a 72-byte line-length limit. Continuation
lines (lines beginning with a single “space” character) are used for lines longer than 72 bytes.
The examples given here follow this rule for continuation lines.
Note that the manifest file and signer’s information file parts of a Signed Manifest are ASCII (not
Unicode) text files. In cases where these files contain a base-64 encoded string, the string is an
ASCII (not Unicode) string before base-64 encoding.
//**********************************************************
// Manifest File Example
//**********************************************************
The manifest file must include a section referring to a memory-type data object with the reserved
name as shown in the example below. This data object is a zero-length object whose sole purpose
in the manifest is to serve as a named collection point for the attributes that carry the details of the
requested update. The attributes are also contained in the manifest file. An example manifest file
is shown below.
Manifest-Version: 2.0
ManifestPersistentId: (base-64 representation of a unique GUID)
Name: memory:UpdateRequestParameters
Digest-Algorithms: SHA-1
SHA-1-Digest: (base-64 representation of a SHA-1 digest of zero-length
buffer)
X-Intel-BIS-ParameterSet: (base-64 representation of
BootObjectAuthorizationSetGUID)
X-Intel-BIS-ParameterSetToken: (base-64 representation of the current
update token)
X-Intel-BIS-ParameterId: (base-64 representation of
“BootObjectAuthorizationCertificate” or
“BootAuthorizationCheckFlag”)
X-Intel-BIS-ParameterValue: (base-64 representation of
certificate or
single-byte boolean flag)
A line-by-line description of this manifest file is as follows.
Manifest-Version: 2.0
This is a standard header line that all signed manifests have. It must appear exactly as shown.
ManifestPersistentId: (base-64 representation of a unique GUID)