EDHOC, the lightweight key exchange for #IoT devices, is now published as #RFC 9528. It enables state of the art elliptic curve based security after exchanging 3 messages of only a bit over 100 bytes in total, thus fitting in even the lowest power networks such as #6LoWPAN and #LoRA. Thanks and congratulations to Göran, John and Francesca for making security more affordable. https://www.rfc-editor.org/rfc/rfc9528.html
@dalias I'm not arguing its exclusion, but that it's getting this prominent a place in the language instead of a namespaced extension point. The point on system interfaces is true for Unix based OSes, but on embedded and WASM systems I don't know of any interfaces where nul-terminated strings are meaningful.
@thejpster I'm conflicted about this. Sure it's nice ergonomics, but `cstr!(...)` wasn't that bad, and it feels like it's giving a foreign language construct more weight in the language than it should have. Yeah it's used widely, but so is `hexlit!(...)`, and where do we stop.
@HerraBRE I should probably not be talking given my NGI application was not granted, but an itemized dump of "what's in your head" with a little sorting can already make a good base roadmap.
Technology enthusiast with a focus on Free Software and embedded systems. Science fiction promised us general purpose electronics, let's build them! (And get their security properties right.)