Skip to content

Comments

fix: send_device_attestation encoding of attestation objects#255

Merged
djc merged 1 commit intodjc:mainfrom
christianhoelzl:attestation_fix_cbor_encoding
Feb 16, 2026
Merged

fix: send_device_attestation encoding of attestation objects#255
djc merged 1 commit intodjc:mainfrom
christianhoelzl:attestation_fix_cbor_encoding

Conversation

@christianhoelzl
Copy link
Contributor

@christianhoelzl christianhoelzl commented Feb 12, 2026

This pull request fixes the function send_device_attestation. Any binary (CBOR encoded) attestation object DeviceAttestation::att_obj is 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 public DeviceAttestation struct.

@djc
Copy link
Owner

djc commented Feb 12, 2026

Thanks! Is this from a lack of testing before or has the spec changed? (Same question for your other PR.)

@christianhoelzl
Copy link
Contributor Author

This was a lack of testing with a real CA, not a change in the ACME specs.
My private ACME test server did accept an array and the bug was overlooked.

@cpu
Copy link
Collaborator

cpu commented Feb 16, 2026

@djc OK to merge this & #254 now or did you want to wait to hear back about Pebble support?

@djc djc merged commit 0b63f6b into djc:main Feb 16, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants