[riot-notifications] [RIOT-OS/RIOT] pkg/tinydtls: DTLS process gets completly borked (#15842)
notifications at github.com
Sun Jan 24 20:27:11 CET 2021
That really helped me, thank you :)
The line `ALRT No security context for epoch: 0` gave me a hint and I found it in the RFC again. If I understand it correctly, my scenario is perfectly described [here](https://tools.ietf.org/html/rfc6347#section-4.2.8). The conditions are the same: Client silently abandons the session and starts a new handshake which epoch 0. I do not think this scenario is unusual. IMHO this should not be handled on application layer.
The fix I've hinted in my first post actually fixes this problem on client side (when the peer is already known but not connected). I have to do a bit more reading though...
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications