#coap #oscore #no-alloc #linker #build

sys no-std liboscore

Rust wrapper around the libOSCORE implementation of OSCORE (RFC8613), a security layer for CoAP

5 releases

0.2.2 Dec 6, 2024
0.2.1 Nov 25, 2024
0.2.0 Nov 11, 2024
0.1.0 Apr 17, 2024

#1498 in Embedded development

Download history 13/week @ 2024-09-09 20/week @ 2024-09-23 4/week @ 2024-09-30 6/week @ 2024-10-14 2/week @ 2024-11-04 128/week @ 2024-11-11 10/week @ 2024-11-18 214/week @ 2024-11-25 349/week @ 2024-12-02 519/week @ 2024-12-09

1,097 downloads per month

BSD-3-Clause

165KB
3K SLoC

Rust 1.5K SLoC // 0.1% comments C 1.5K SLoC // 0.2% comments

This is the main crate of libOSCORE when accessing libOSCORE through Rust.

It performs different tasks that are relatively tightly coupled:

  • It builds the C header files for the Rust backend implementations using cbindgen.
  • It configures and builds Rust "header" files from the C header files (excluding types that are already native Rust types), as a -sys crate would do.
  • It compiles the C files of liboscore directly for static linking.
  • It implements coap-message on top of OSCORE protected messages.

At present, it pulls in both the cryptography and the message backends written in Rust (liboscore-cryptobackend and liboscore-msgbackend). Making the cryptography backend optional would be simple and straightforward (and is just waiting for an application to need it). Using an non-Rust message backend would be possible in theory, but the author fails to imagine when that would be useful. Some extra constructors for protected messages might be needed.

Dependencies

~3–6.5MB
~111K SLoC