commit | 8054ce281a2e530eb83acb46eb9a5d9f5b7c6aaf | [log] [tgz] |
---|---|---|
author | David Brown <david.brown@linaro.org> | Tue Jul 11 12:12:09 2017 -0600 |
committer | David Brown <davidb@davidb.org> | Wed Jul 12 15:00:57 2017 -0600 |
tree | c7cc509f66812bfc54c5f51421a0f251995e3ffb | |
parent | 187dd889dc603ffa612e97c012b10514ca1084b9 [diff] |
sim: Change to `ring` instead of `rust-crypto` The ring crate's SHA256 is slightly slower than the one from rust-crypto, but is much cleaner to use. It also has all of the hashing operations we need. This crate is somewhat opinionated, e.g. will not sign messages without also performing the signature itself. Unfortunately, this means we'll end up computing signatures of the same data many times, and perhaps this should be improved, since we're always using the same data. Signed-off-by: David Brown <david.brown@linaro.org>
MCUBoot is a secure bootloader for 32-bit MCUs. The goal of MCUBoot is to define a common infrastructure for the bootloader, system flash layout on microcontroller systems, and to provide a secure bootloader that enables easy software upgrade.
MCUboot is operating system and hardware independent, and relies on hardware porting layers from the operating system it works with. Currently mcuboot works with both the Apache Mynewt, and Zephyr operating systems, but more ports are planned in the future.
The MCUBoot project was originally taken from the Apache Mynewt operating system, which had secure boot and software upgrade functionality instrinsic to it. Currently development is heads down on a first release of MCUboot that works across both the Zephyr operating system and Apache Mynewt operating system.
For more information on what's being planned, and worked on, please visit:
https://runtimeco.atlassian.net/projects/MCUB/summary
Information and documentation on the bootloader is stored within the source, and on confluence:
https://runtimeco.atlassian.net/wiki/discover/all-updates
For more information in the source, here are some pointers:
Developers welcome! To join in the discussion, please join the developer mailing list:
http://lists.runtime.co/mailman/listinfo/dev-mcuboot_lists.runtime.co