e6c17461a3
Provide and use a `workspace.lints` table. This makes it easier to maintain and to enforce one coding style. Let's explicitly disable the `missing_docs` linting rule for tests. MSRV for the lints table is 1.74 [1] [1] https://doc.rust-lang.org/cargo/reference/workspaces.html#the-lints-table Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com> Reviewed-by: Steffen Eiden <seiden@linux.ibm.com> Acked-by: Finn Callies <fcallies@linux.ibm.com> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
pvattest
Synopsis
pvattest [OPTIONS] <COMMAND>
Description
create, perform, and verify attestation measurements Create, perform, and verify attestation measurements for IBM Secure Execution guest systems.
Commands Overview
- create
-
Create an attestation measurement request
- perform
-
Send the attestation request to the Ultravisor
- verify
-
Verify an attestation response
- version
-
Print version information and exit
Options
-v, --verbose
-
Provide more detailed output
--version
-
Print version information and exit
-h, --help
-
Print help (see a summary with '-h')
pvattest create
Synopsis
pvattest create [OPTIONS] --host-key-document <FILE> --output <FILE> --arpk <FILE> <--no-verify|--cert <FILE>>
Description
Create an attestation measurement request Create attestation measurement requests to attest an IBM Secure Execution guest. Only build attestation requests in a trusted environment such as your Workstation. To avoid compromising the attestation do not publish the attestation request protection key and shred it after verification. Every 'create' will generate a new, random protection key.
Options
-k, --host-key-document <FILE>
-
Use FILE as a host-key document. Can be specified multiple times and must be
used at least once.
--no-verify
-
Disable the host-key document verification. Does not require the host-key
documents to be valid. Do not use for a production request unless you verified
the host-key document beforehand.
-C, --cert <FILE>
-
Use FILE as a certificate to verify the host key or keys. The certificates are
used to establish a chain of trust for the verification of the host-key
documents. Specify this option twice to specify the IBM Z signing key and the
intermediate CA certificate (signed by the root CA).
--crl <FILE>
-
Use FILE as a certificate revocation list. The list is used to check whether a
certificate of the chain of trust is revoked. Specify this option multiple times
to use multiple CRLs.
--offline
-
Make no attempt to download CRLs
--root-ca <ROOT_CA>
-
Use FILE as the root-CA certificate for the verification. If omitted, the system
wide-root CAs installed on the system are used. Use this only if you trust the
specified certificate.
-o, --output <FILE>
-
Write the generated request to FILE
--arpk <FILE>
-
Save the protection key as unencrypted GCM-AES256 key in FILE Do not publish
this key, otherwise your attestation is compromised.
--add-data <FLAGS>
-
Specify-additional data for the request. Additional data is provided by the
Ultravisor and returned during the attestation request and is covered by the
attestation measurement. Can be specified multiple times. Optional.
Possible values:
- **phkh-img**: Request the public host-key-hash of the key that decrypted the SE-image as additional-data
- **phkh-att**: Request the public host-key-hash of the key that decrypted the attestation request as additional-data
-v, --verbose
-
Provide more detailed output
-h, --help
-
Print help (see a summary with '-h')
pvattest perform
Synopsis
pvattest perform [OPTIONS] [INPUT] [OUTPUT]
Description
Send the attestation request to the Ultravisor Run a measurement of this system through ’/dev/uv’. This device must be accessible and the attestation Ultravisor facility must be present. The input must be an attestation request created with ’pvattest create’. Output will contain the original request and the response from the Ultravisor.
Arguments
<INPUT>
-
Specify the request to be sent
<OUTPUT>
-
Write the result to FILE
Options
-u, --user-data <File>
-
Provide up to 256 bytes of user input User-data is arbitrary user-defined data
appended to the Attestation measurement. It is verified during the Attestation
measurement verification. May be any arbitrary data, as long as it is less or
equal to 256 bytes
-v, --verbose
-
Provide more detailed output
-h, --help
-
Print help (see a summary with '-h')
pvattest verify
Synopsis
pvattest verify [OPTIONS] --input <FILE> --hdr <FILE> --arpk <FILE>
Description
Verify an attestation response Verify that a previously generated attestation measurement of an IBM Secure Execution guest is as expected. Only verify attestation requests in a trusted environment, such as your workstation. Input must contain the response as produced by ’pvattest perform’. The protection key must be the one that was used to create the request by ’pvattest create’. Shred the protection key after the verification. The header must be the IBM Secure Execution header of the image that was attested during ’pvattest perform’
Options
-i, --input <FILE>
-
Specify the attestation request to be verified
-o, --output <FILE>
-
Specify the output for the verification result
--hdr <FILE>
-
Specifies the header of the guest image. Can be an IBM Secure Execution image
created by genprotimg or an extracted IBM Secure Execution header. The header
must start at a page boundary.
--arpk <FILE>
-
Use FILE as the protection key to decrypt the request Do not publish this key,
otherwise your attestation is compromised. Delete this key after verification.
--format <FORMAT>
-
Define the output format
Default value: 'yaml'
Possible values:
- **yaml**: Use yaml format
-u, --user-data <FILE>
-
Write the user data to the FILE if any. Writes the user data, if the response
contains any, to FILE The user-data is part of the attestation measurement. If
the user-data is written to FILE the user-data was part of the measurement and
verified. Emits a warning if the response contains no user-data
-v, --verbose
-
Provide more detailed output
-h, --help
-
Print help (see a summary with '-h')