Dear All,
Within [ https://datatracker.ietf.org/doc/html/draft-ietf-acme-dns-account-label-02 | draft-ietf-acme-dns-account-label-02 ] , Section 3.2 ( Challenge Fulfillment ), the processing steps state that the client: * constructs the key authorization as defined in RFC 8555 Section 8.1, and * computes the SHA-256 digest of the key authorization. However, the example DNS record that follows appears to contain the full key authorization value (<token>.<thumbprint>) rather than the SHA-256 digest derived from it: _ujmmovf2vn55tgye._acme- [ http://challenge.example.org/ | challenge.example.org ] 300 IN TXT "LoqXcYV8...jxAjEuX0.9jg46WB3...fm21mqTI" Could the authors please review whether the example is consistent with the processing steps described in this section? Thank you for your consideration. Best Regards, Meltem SEYİRT
_______________________________________________ Acme mailing list -- [email protected] To unsubscribe send an email to [email protected]
