Files
s390-tools/rust/pvattest/man/pvattest-verify.1
T
Jan Höppner c93b74b527 pvattest: Fix various man page issues
The pvattest man pages are generated mostly from the rust doc entries
within the tool. Some escape sequences and whatis-entries are incorrect
as found by different linter:

$ man --warnings -E UTF-8 -l -Tutf8 -Z ./rust/pvattest/man/pvattest-create.1
troff:<standard input>:23: warning: macro 'create'' not defined

$ lexgrog -w -m rust/pvattest/man/pvattest-verify.1
rust/pvattest/man/pvattest-verify.1: parse failed

Fix this by regenerating the man pages with correct escape sequences and
whatis-entries.

Github-ID: https://github.com/ibm-s390-linux/s390-tools/issues/170
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
2025-03-19 16:35:05 +01:00

121 lines
3.3 KiB
Groff
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
.\" Copyright 2024, 2025 IBM Corp.
.\" s390-tools is free software; you can redistribute it and/or modify
.\" it under the terms of the MIT license. See LICENSE for details.
.\"
.TH "PVATTEST-VERIFY" "1" "2025-03-12" "s390-tools" "Attestation Manual"
.nh
.ad l
.SH NAME
pvattest-verify \- Verify an attestation response
.SH SYNOPSIS
.nf
.fam C
pvattest verify [OPTIONS] --input <FILE> --hdr <FILE> --arpk <FILE>
.fam C
.fi
.SH DESCRIPTION
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. The verify command
solely verifies that the Attestation measurement is correct. It does not check
for the content of additional data or user data. See `pvattest check` for policy
checks after you verified the Attestation measurement.
.SH OPTIONS
.PP
\-i, \-\-input <FILE>
.RS 4
Specify the attestation response to be verified.
.RE
.RE
.PP
\-o, \-\-output <FILE>
.RS 4
Specify the output for the verification result.
.RE
.RE
.PP
\-\-hdr <FILE>
.RS 4
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.
.RE
.RE
.PP
\-a, \-\-arpk <FILE>
.RS 4
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.
.RE
.RE
.PP
\-\-format <FORMAT>
.RS 4
Define the output format.
[default: 'yaml']
Possible values:
.RS 4
\- \fByaml\fP: Use yaml format.
.RE
.RE
.PP
\-u, \-\-user\-data <FILE>
.RS 4
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.
.RE
.RE
.PP
\-h, \-\-help
.RS 4
Print help (see a summary with \fB\-h\fR).
.RE
.RE
.SH EXIT STATUS
.TP 8
.B 0 - Attestation Verified
Attesatation measurement verified successfully. Measured guest is in Secure Execution mode.
.RE
.TP 8
.B 1 - Program Error
Something went wrong during the local calculation or receiving of the measurement value. Refer to the error message.
.RE
.TP 8
.B 2 - Attestation NOT Verified
Attesation measurement calculation does not match the received value. Measured guest is very likely not in Secure Execution mode.
.RE
.SH EXAMPLES
To verify a measurement in 'measurement.bin' with the protection key 'arp.kep' and SE-guest header 'se_guest.hdr'.
.PP
.nf
.fam C
$ pvattest verify --input attresp.bin --arpk arp.key --hdr se_guest.hdr
.fam T
.fi
If the verification was successful the program exists with zero.
If the verification failed it exists with 2 and prints the following to stderr:
.PP
.nf
.fam C
ERROR: Attestation measurement verification failed:
Calculated and received attestation measurement are not the same.
.fam T
.fi
.SH "SEE ALSO"
.sp
\fBpvattest\fR(1)