oscore-demo

This is a demonstration of protecting CoAP with OSCORE on embedded devices. It's using the STM32F303VCT6 (server), the STM32F407VGT6U (client) and the W5500 Ethernet controller and is therefore pretty specific to the hardware. But of course the EDHOC/OSCORE library is completely hardware independent. There is also a simple CoAP proxy (built for a std environment, can run on a Raspberry Pi for example) between the client and server, to demonstrate that OSCORE can protect sensitive data end-to-end, but still allows proxying.

Dependencies

To build this you'll need (in your nightly toolchain):

• rust-std components (pre-compiled core crate) for the ARM Cortex-M target. Run:

$ rustup target add thumbv7em-none-eabihf

Hardware setup

This is the wiring:

W5500       STM32F303/407
-----       -------------
VCC         3V
GND         GND
MISO        PB4
MOSI        PB5
SCK         PB3
CS          PA15

And for getting serial debug output (using the SparkFun FTDI Basic Breakout as USB to Serial IC):

FTDI        STM32F303/407
----        -------------
GND         GND
RXI         PB6

Building

We're using minicom for serial output, so you need to create .minirc.dfl in your home with this configuration:

pu baudrate 115200
pu bits 8
pu parity N
pu stopbits 1
pu rtscts No
pu xonxoff No
pu linewrap Yes

To exit minicom, use CTRL+A+X.

Use OpenOCD to connect to the board

$ openocd -f interface/stlink-v2-1.cfg -f target/stm32f3x.cfg   # For the F303
$ openocd -f interface/stlink-v2-1.cfg -f target/stm32f4x.cfg   # For the F407

In a different terminal, open minicom to see serial output

$ minicom -D /dev/ttyUSB0

In yet another terminal, build and enter GDB. We're using the release flag since the debug build might be too large for the flash memory.

$ cargo run --release

This will break at the main function, so you need to

(gdb) continue

License

Licensed under either of

• Apache License, Version 2.0
• MIT license

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.