From b7db7c8d6ad5b9f49db409b10ec3ac35029e6383 Mon Sep 17 00:00:00 2001 From: Mariano Cano Date: Mon, 6 Feb 2023 15:13:49 -0800 Subject: [PATCH] Clarify attest command help --- cmd/attest.go | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/cmd/attest.go b/cmd/attest.go index 024d72c..07a7fdd 100644 --- a/cmd/attest.go +++ b/cmd/attest.go @@ -47,10 +47,10 @@ is set, an attestation object. Currently this command is only supported on YubiKeys. An attestation object can be used to resolve an ACME device-attest-01 challenge. -To pass this challenge the client needs to show prove of possession of a private -key by signing the ACME key authorization, the format is defined by RFC 8555 as -a string that concatenates the token for the challenge with a key fingerprint -separated by a "." character: +To pass this challenge, the client needs proof of possession of a private key by +signing the ACME key authorization. The format is defined in RFC 8555 as a +string that concatenates the challenge token for the challenge with the ACME +account key fingerprint separated by a "." character: keyAuthorization = token || '.' || base64url(Thumbprint(accountKey))`, Example: ` # Get the attestation certificate from a YubiKey: