Hi arman,
> Looks like the subject was: "[PATCH v3 1/4] src/shared/att: Introduce struct bt_att."
> We basically talked about the need for bt_att to somehow obtain the CSRK (through
> bt_att_new maybe?) and internally keep the local+remote sign counters to be able
> to calculate the authentication signature. Basically, the authentication signature
> should get calculated by bt_att given all the data that it needs.
The 3-days Mid-autumn festival is right around the corner. So there is no much time left to implement it.
So I investigate the source code, there are some difference between old att stack and new shared/att stack.
In the old stack, doing encode/decode PDU split with sending att protocol command to remote device.
However, in the new stack , bt_att_send do more things than old did including encode pdu with opcode.
Because Att pdu signed process include whole data pdu, so in my mind, if we keep consistent style in code,
we have to do sign att pdu in bt_att_send function. We have to expand bt_att struct to store CSRK and
so on stuff. So that's the only implementation make sense for signed write command.
BTW, compared with signing the outgoing, verifying incoming ATT PDUs would be more complex. I am not
Sure which file to implement it.
Thanks
Chaojie
��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
