[riot-notifications] [RIOT-OS/RIOT] pkg/tinydtls: async event SOCK_ASYNC_CONN_FIN does not indicate which session has been finished (#15517)

János Brodbeck notifications at github.com
Fri Nov 27 18:04:03 CET 2020


<!--
====================================
IF YOUR ISSUE IS RELATED TO SECURITY
====================================
please submit it to the security mailing-list security at riot-os.org.

If your issue is a question related to the usage of RIOT, please submit it to
the user mailing-list users at riot-os.org or to the developer mailing-list
devel at riot-os.org.
-->

#### Description
<!--
Example: Cannot build gnrc_networking application for samr21-xpro board.
-->
When using tinyDTLS with asynchronous sockets the event for a finished session does not indicate which session has been closed. You have 0 information which connection has been finished. It makes it impossible to keep the session for a long time because you cannot track sessions properly without touching the internals of tinydtls.

#### Steps to reproduce the issue
<!--
Try to describe as precisely as possible here the steps required to reproduce
the issue. Here you can also describe your hardware configuration, the network
setup, etc.
-->

#### Expected results
Argument of the callback event points to the closed session.

#### Actual results
The argument is currently null.
#### Versions
<!--
Operating system: Mac OSX, Linux, Vagrant VM
Build environment: GCC, CLang versions (you can run the following command from
the RIOT base directory: make print-versions).
-->

<!-- Thanks for contributing! -->


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/15517
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201127/f86662f5/attachment.htm>


More information about the notifications mailing list