Using tinydtls on RIOT OS is not limited to GNRC as network stack.
It is also working with e.g. lwIP, see: https://github.com/RIOT-OS/RIOT/pull/17552
Therefore the name WITH_RIOT_GNRC is misleading.
- Removes `TINYDTLS_LOG` because it is redundant with `TINYDTLS_LOG_LVL`
- Remove check for using tinydtls module because the Makefile will only
be included if the tinydtls module is used
When WITH_RIOT_GNRC is set in CFLAGS, tinydtls will use a more
compact address representation based on ipv6_addr_t instead of
POSIX-style sockaddr_in6 to identify sessions (cf. struct session_t).
When posix_sockets are used (as in libcoap, e.g.), the POSIX
address representation should be selected automatically for
consistency. This change adds -DWITH_RIOT_GNRC to CFLAGS only
when the module posix_sockets is not selected.
Due to all the changes, this is basically a new version for this
example. The main benefit is the use of sock_udp but also the client
side is now more robust and reliable.
The parameters required for the PSK and ECC (e.g. keys) modes are moved
to an unique header.
The integration of TinyDTLS for RIOT has been merged into the
development branch of the official repository.
It will be officially available on the master branch in the next
release of tinyDTLS.
Other minor updates:
- Support for the RIOT's memarray
- tinydtls/sha2 is removed from the compilation for giving priority
to RIOT's sha2 functions.
