roll: third_party/pigweed/src b9b6730..7f189f2 (50 commits) 7f189f2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/422812 roll: luci edcdd96:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/422772 roll: fuchsia-infra-bazel-rules e054d67..1281548 (50 commits) a3ecc1a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/422732 roll: rust-analyzer 4cf013e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/415137 pw_tokenizer: Correctly handle negative width/precision in Python ad35431:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/416872 pw_tokenizer: Expand detokenization data-driven test cases 4de0e92:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/422132 pw_containers: Resolve pw_allocator co-dependencies in Android.bp 876420b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420732 pw_assert: Promote pw_assert from pw_kernel 1ccbe94:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/415633 docs: Update changelog for May 2026 2862ae5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/422192 pw_rp2350: Use new rust #[entry] macro c98af40:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/414492 pw_tokenizer: Correctly handle * width/precision in C++ 26099c0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421362 pw_bluetooth_sapphire: Fix hci::Connection disconnection callback move 05d77b6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417652 pw_bluetooth_proxy: Add configurable runtime filtering a07c185:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421992 pw_containers: Avoid % in PW_ASSERT condition 50d7679:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421812 pw_bluetooth_sapphire: Fix pathloss overflow in discovery filter 859b464:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420232 pw_trace_tokenized: Decode tokenized event labels 70a2552:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421492 targets: Add pw_rp2350 freertos target bc6d1da:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421612 pw_kernel: Restructure the scheduler's submodules 3a5e3c2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421674 OWNERS: Add leonardteng, sychiu f2b6e0f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421493 pw_kernel: Gate syscall_defs deps on userspace_build_enabled 6a20594:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417632 cmake: Support Python protobuf codegen d284622:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/414941 pw_rpc: Hold the RPC lock when services unregister themselves 4933de4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420555 rust: Reformat all rust files as 2021 edition 5043331:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/421252 pw_enum: Fix builds with Zephyr 10b6150:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/414333 pw_preprocessor: More attributes for lifetime safety b592e33:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417914 roll: Roll more packages necessary for Bazel 9 cd75e1a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420573 pw_ide: Fix compile commands integration test failure 2cde7d6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420112 pw_kernel: Use harware fence around RISC-V spinlock 6a5ffd8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420172 rust: Use edition 2021 for core pigweed rust modules acba7bd:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417912 various: Squash various warnings that appear with Bazel 9 cf08cdf:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/420552 pw_software_update: Fix facade deps a7630fb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/418112 Reland "pw_sync_freertos: Disable ISL scheduler lock on Cortex-M" 6f756c1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419773 pw_bluetooth_sapphire: Fix crash on undersized HCI Mode Change event 3427e5c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417212 pw_tokenizer: Support Rust error output parity with C++ version 6d19412:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419732 pw_bluetooth_sapphire: Prevent double-closing IsoStream 89f0865:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419772 pw_bluetooth_sapphire: Fix crash on undersized ISO packet c5a69a6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417952 pw_bluetooth_sapphire: Harden ISO transport 104dd9a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/403512 pw_trace: Add support for plugin data format string c9687b5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/413792 pw_bluetooth_sapphire: Gracefully reject LE pairing 27bb68f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419455 pw_build: Allow flag options to appear as workflows arguments 6304e49:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417913 bazel: Add target_compatible_with in more places 390cca6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417972 pw_bluetooth_sapphire: Fix crash on invalid LE address type 89ecfab:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/413452 pw_elf: Add Python CoredumpBuilder class 44d79e3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/413112 pw_elf: Add Python ELF image builder 711aa64:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/410732 pw_ide: Force generation of headers in aspect 3933390:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419473 pw_ide: Release v1.10.4 6481562:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419492 pw_spi: Add jrreinhart@google.com to OWNERS c5968b4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/411332 [owners] Remove markslevinsky@google.com from pw_spi/OWNERS a5243af:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/417832 pw_kernel: bitwise-OR interrupt signal bits 084a886:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/411152 pw_i2c_zephyr: Fix header inclusion c00b3ec:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/419172 roll: go Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: b9b67304f8575e..7f189f25227743 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8678972402137934721 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia1f58974ae5a905f4af6b47af8fef14d6359c270 Reviewed-on: https://pigweed-review.googlesource.com/c/open-dice/+/423032
This repository contains the specification for the Open Profile for DICE along with production-quality code. This profile is a specialization of the Hardware Requirements for a Device Identifier Composition Engine and DICE Layering Architecture specifications published by the Trusted Computing Group (TCG). For readers already familiar with those specs, notable distinctives of this profile include:
You can find us (and join us!) at https://groups.google.com/g/open-profile-for-dice. We're happy to answer questions and discuss proposed changes or features.
The specification can be found here. It is versioned using a major.minor scheme. Compatibility is maintained across minor versions but not necessarily across major versions.
Production quality, portable C code is included. The main code is in dice.h and dice.c. Cryptographic and certificate generation operations are injected via a set of callbacks. Multiple implementations of these operations are provided, all equally acceptable. Integrators should choose just one of these, or write their own.
Tests are included for all code and the build files in this repository can be used to build and run these tests.
Disclaimer: This is not an officially supported Google product.
Different implementations use different third party libraries. The third_party directory contains build files and git submodules for each of these. The submodules must be initialized once after cloning the repo, using git submodule update --init, and updated after pulling commits that roll the submodules using git submodule update.
To setup the build environment the first time:
$ git submodule update --init --recursive $ source bootstrap.sh $ gn gen out
To build and run tests:
$ ninja -C out
The easiest way, and currently the only supported way, to build and run tests is from a Pigweed environment on Linux. Pigweed does support other host platforms so it shouldn't be too hard to get this running on Windows for example, but we use Linux.
There are two scripts to help set this up:
bootstrap.sh will initialize submodules, bootstrap a Pigweed environment, and generate build files. This can take some time and may download on the order of 1GB of dependencies so the normal workflow is to just do this once.
activate.sh quickly reactivates an environment that has been previously bootstrapped.
These scripts must be sourced into the current session: source activate.sh.
In the environment, from the base directory of the dice-profile checkout, run ninja -C out to build everything and run all tests. You can also run pw watch which will build, run tests, and continue to watch for changes.
This will build and run tests on the host using the clang toolchain. Pigweed makes it easy to configure other targets and toolchains. See toolchains/BUILD.gn and the Pigweed documentation.
The code is designed to be portable and should work with a variety of modern toolchains and in a variety of environments. The main code in dice.h and dice.c is C99; it uses uint8_t, size_t, and memcpy from the C standard library. The various ops implementations are as portable as their dependencies (often not C99 but still very portable). Notably, this code uses designated initializers for readability. This is a feature available in C since C99 but missing from C++ until C++20 where it appears in a stricter form.
The Google C++ Style Guide is used. A .clang-format file is provided for convenience.
To incorporate the code into another project, there are a few options:
Copy only the necessary code. For example:
Take the main code as is: include/dice/dice.h, src/dice.c
Choose an implementation for crypto and certificate generation or choose to write your own. If you choose the boringssl implementation, for example, take include/dice/utils.h, include/dice/boringssl_ops.h, src/utils.c, and src/boringssl_ops.c. Taking a look at the library targets in BUILD.gn may be helpful.
Add this repository as a git submodule and integrate into the project build, optionally using the gn library targets provided.
Integrate into a project already using Pigweed using the gn build files provided.
The build reports code size using Bloaty McBloatface via the pw_bloat Pigweed module. There are two reports generated:
Library sizes - This report includes just the library code in this repository. It shows the baseline DICE code with no ops selected, and it shows the delta introduced by choosing various ops implementations. This report does not include the size of the third party dependencies.
Executable sizes - This report includes sizes for the library code in this repository plus all dependencies linked into a simple main function which makes a single DICE call with all-zero input. It shows the baseline DICE code with no ops (and therefore no dependencies other than libc), and it shows the delta introduced by choosing various ops implementations. This report does include the size of the third party dependencies. Note that rows specialized from ‘Boringssl Ops’ use that as a baseline for sizing.
The reports will be in the build output, but you can also find the reports in .txt files in the build output. For example, cat out/host_optimized/gen/*.txt | less will display all reports.
This code does not itself use mutable global variables, or any other type of shared data structure so there is no thread-safety concerns. However, additional care is needed to ensure dependencies are configured to be thread-safe. For example, the current boringssl configuration defines OPENSSL_NO_THREADS_CORRUPT_MEMORY_AND_LEAK_SECRETS_IF_THREADED, and that would need to be changed before running in a threaded environment.
This code makes a reasonable effort to clear memory holding sensitive data. This may help with a broader strategy to clear sensitive data but it is not sufficient on its own. Here are a few things to consider.