Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for creating attestation object #36

Merged
merged 3 commits into from
Feb 7, 2023
Merged

Conversation

maraino
Copy link
Contributor

@maraino maraino commented Feb 6, 2023

Description

This PR adds support to creating attestation objects, this can be used to resolve ACME device-attest-01 challenges.

Attestation objects can be used to resolve ACME device-attest-01
challenges.
@maraino maraino requested a review from hslatman February 6, 2023 18:04
@maraino maraino marked this pull request as ready for review February 6, 2023 18:05
cmd/attest.go Outdated
Comment on lines 49 to 53
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
An attestation object can be used to resolve an ACME device-attest-01 challenge.
To pass this challenge, the client needs proof 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 with the ACME account key fingerprint
separated by a "." character:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed with b7db7c8

@hslatman
Copy link
Member

hslatman commented Feb 6, 2023

I did approve it, but I think the command may be doing too many different things; may be too smart with just flags. More explicit might be better. Don't have better suggestions at the moment, though. Given that the plugin is still considered beta, I think we're good if we need to break the command later, so let's keep it like this for now?

@maraino maraino requested review from areed and dopey and removed request for areed February 6, 2023 23:14
@maraino maraino merged commit df45304 into main Feb 7, 2023
@maraino maraino deleted the attestation-object branch February 7, 2023 01:43
@maraino maraino removed the request for review from dopey February 7, 2023 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants