Siddharth Chandrasekaran

> In osdp_phy.c line 311, seq-repeat reply-resend feature not supported! When cp resend the last time request, the feature not supported. Yes. To close this issue both features will be...

@GaspardRig, a zero length block for decryption is not a valid packet as the encrypted block needs to be terminated by 0x80 which implies, at least one byte of data...

@GaspardRig, allowing a zero length block may have more severe effect such as introducing a new attack vector that could compromise the session keys and render the whole thing pointless...

@IDmachines, thanks for the list of approved devices, I didn't know one existed. I wonder if we can get library implementations approved. I'll write an email to the folks SEA.

@wcmohler @knyzorg what is the status of this PR? Do let me know if any work is needed to close this. I have some bandwidth to spare. @mylselgan, what you...

@schmida2 will take a another look at this. A lot of things have changed since this ticket was created so it might be easier to support this now. > The...

> Wrt SC what commands/responses are ok in the clear? None of them. The only exception is when a KEYSET command is ACK-ed in plain text because the PD has...

Yes, that is the case now. What I meant was you cannot mix modes: when SC is active, a PD will not allow non-SC messages and respond with NACK(6) for...

@schmida2 I am looking into this now. Looks to me the re-send and re-response is an implementation detail that application doesn't need to know about. What is you idea behind...

Another option is to keep a full copy of the last reply that we constructed last. This makes the response to re-sent commands faster (without going back to the app...