fabian18

Not all, I am about to rebase this PR

@DanielLockau-MLPA FYI

@chrysn I have spent some time to reason about and answer your questions. > Are there use cases that warrant the complexity of having different back-ends "mounted" at different paths?...

> Managing them at three points in the tree (say, > `/frozen/oscore/ctx/0/key`, `/once-in-a-while/oscore/ctx/0/ssn`, > `/at-boot/oscore/ctx/0/replay` sounds hard to manage consistently. Taking `/net/coap/oscore/ctx/0/{key | replay | ssn}` I would suppose that...

> It's going back and forth between numerics and ASCII strings a lot. The concept for a configuration array is that we can know if an index is free or...

Using 64 bit SIDs now as keys. A string path is constructed on handler lookup when `configuration_strings` is used.

As of now ... `TEST_CONFIGURATION_BACKEND=configuration_backend_flashdb_mtd USEMODULE+="configuration_backend_reset_flashdb" BOARD=same54-xpro make cosy` Cosy shows about 4K ROM for the module with FlashDB backend.  and 3K ROM without strings `BOARD=same54-xpro...

# SID assignment An SID is a unique identifier for any configuration value. Every instance within an array has its own SID. To integrate a new configuration module, you have...

This does not fix our nonce reuse, true. Ways to solve would be either store the sequence counter of a used key, or use a new key on every reboot....

I think the `mqtts` module should exist in `pkg/paho-mqtt/contrib` and the `tls` module should exist in `pkg/wolfssl/sock_tls`. WolfSSL already provides something for us in `wolfio.h` which seems to be something...