-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix retrieval of attestation challenge in Java #18867
Fix retrieval of attestation challenge in Java #18867
Conversation
PR #18867: Size comparison from 3956a9d to cdca933 Full report (37 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
When not using the auto-commissioning flow, the mDeviceBeingCommissioned proxy is no longer assigned, so the default behavior of retrieving the attestation challenge fails. Since at the time of use we already have a reference to the correct DeviceProxy, added an overload to pass the proxy along to retrieve the challenge.
cdca933
to
5705d4d
Compare
PR #18867: Size comparison from d2a6470 to 5705d4d Increases (37 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
Decreases (4 builds for cc13x2_26x2, efr32)
Full report (37 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
*/ | ||
virtual CHIP_ERROR GetAttestationChallenge(ByteSpan & attestationChallenge) | ||
{ | ||
Optional<SessionHandle> secureSessionHandle; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be better to put the implementation in the .cpp...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems no updates in a while on this PR. Assuming this can be done as a followup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andy31415 Is there an issue tracking tahg followup assigned to this PR's author?
I am fine with followups, but I want them to actually happen, and except for a few people our track record at them is very poor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followup is here: #19058
When not using the auto-commissioning flow, the mDeviceBeingCommissioned
proxy is no longer assigned, so the default behavior of retrieving the
attestation challenge fails.
Since at the time of use we already have a reference to the correct
DeviceProxy, added an overload to pass the proxy along to retrieve the
challenge.