fix: send_device_attestation encoding of attestation objects#255
Merged
fix: send_device_attestation encoding of attestation objects#255
Conversation
Owner
|
Thanks! Is this from a lack of testing before or has the spec changed? (Same question for your other PR.) |
djc
reviewed
Feb 12, 2026
Contributor
Author
|
This was a lack of testing with a real CA, not a change in the ACME specs. |
djc
approved these changes
Feb 12, 2026
cpu
approved these changes
Feb 12, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes the function
send_device_attestation. Any binary (CBOR encoded) attestation objectDeviceAttestation::att_objis now sent as an base64 encoded string to the ACME CA, not as an array anymore. I successfully tested this change with Step CA. Some obsolete annotations are removed from the publicDeviceAttestationstruct.