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

sys no-std liboscore

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

7 releases

new 0.2.4 Feb 14, 2025
0.2.3 Feb 14, 2025
0.2.2 Dec 6, 2024
0.2.1 Nov 25, 2024
0.1.0 Apr 17, 2024

#774 in Embedded development

Download history 2/week @ 2024-11-02 119/week @ 2024-11-09 17/week @ 2024-11-16 205/week @ 2024-11-23 268/week @ 2024-11-30 576/week @ 2024-12-07 164/week @ 2024-12-14 18/week @ 2024-12-21 2/week @ 2024-12-28 233/week @ 2025-01-04 111/week @ 2025-01-11 374/week @ 2025-01-18 173/week @ 2025-01-25 142/week @ 2025-02-01 1526/week @ 2025-02-08

2,252 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
~112K SLoC