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

[1.0] attestation elements and signature are not available during opcert signing #22419

Closed
chrisdecenzo opened this issue Sep 6, 2022 · 2 comments · Fixed by #22369
Closed
Assignees

Comments

@chrisdecenzo
Copy link
Contributor

Reproduction steps

1.Configure Android ChipDeviceController for opcert signing callback
2.AttestationElements and Signature object are often corrupted since these are not deep copied into the CommissioningParameters object (so the memory is freed after the AttestationValidation step). 
3.The AttestationElements and Signature objects provided to the opcert signing callback are often corrupted

Bug prevalence

Memory corruption if often

GitHub hash of the SDK that was being used

master

Platform

android

Platform Version(s)

No response

Type

Core SDK Memory Issue

Anything else?

No response

@andy31415
Copy link
Contributor

@chrisdecenzo - 1.Configure Android ChipDeviceController for opcert signing callback could you share code or commands to do this?

How does a developer reproduce the bug?

@chrisdecenzo
Copy link
Contributor Author

hi @andy31415 - in ChipDeviceController.java, assign a NOCChainIssuer (using setNOCChainIssuer).

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 a pull request may close this issue.

2 participants