roll: third_party/pigweed/src 62bd30d..25daf7f (51 commits) 25daf7f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446972 roll: luci 71e5af4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446932 roll: fuchsia-infra-bazel-rules 07bb99a..d3c6712 (3 commits) 29e7333:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446892 roll: rust-analyzer c14c119:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444612 pw_web: Update nodejs deps 7dc3b46:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446293 pw_bluetooth: Add remaining ATT PDU schemas to att.emb d2f4835:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/434645 pw_bluetooth_sapphire: Cache serialized SDP payloads 6256be7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446272 roll: gn 5b1ddd0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/446012 crates_io: Update alias_hub 534798d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444775 bazel: Update CIPD deps 751a4b0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445992 docs: Update security bulletin commit hashes e372084:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/442033 pw_kernel: Add QEMU-specific physical memory mode to gdb client 6890a37:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445615 docs: Update security bulletin 2026-07 ed4e552:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445614 pw_protobuf: Skip field after partial streamed Find read 2a731ae:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445872 crates_io: Remove unnecessary embedded crates from crates_std 7c29e52:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445613 pw_transfer: Enforce start chunk structure 3031090:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/442032 pw_kernel: Implement gdb register read and write commands 0ae7f0c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/436516 pw_kernel: Add control-C interrupt command to gdb client 74dbc69:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/436515 pw_kernel: Implement gdb memory write command ecd7f14:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440093 pw_bluetooth_proxy: Replace monolithic dep with granular clock target a2f0a66:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/436293 docs: Add workflow for creating security bulletins 6f39e06:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/415612 docs: Add security_note aliases and an example 9c95c90:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445252 third_party/perfetto: Copybara import ebf9d43:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445192 pw_chre: Add integer overflow guards to array memory allocation APIs 63998b2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441612 pw_metric: Deprecate Metric alias and helpers f0928d2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/429752 pw_metric: Add bool, int32, double, and token metrics 1b83b90:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444992 pw_build: Handle HTML-escaped paths in gn_resolver 7ca57d6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/445232 third_party/fuchsia: Copybara import 28e8fbe:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444955 pw_kernel: Update adventure MODULE.bazel.lock 14897e7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444954 crates_io: Update rp235x-hal to 0.4.0 753020b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444672 pw_grpc: Add deferred processing for data frames 5bf5fbb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444953 crates_io: Update riscv-semihosting to 0.2.1 2e20158:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444952 crates_io: Update riscv to 0.16.1 ca6a0c7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/416853 docs: Add threat model docs ddedb45:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444492 pw_presubmit: Exclude reST templates from copyright_notice 3530088:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/442673 zephyr: Remove unnecessary @zephyr dependencies 9e61531:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/440872 pw_kernel: Allow missing annotation linker sections 3bcdb7c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/436514 pw_kernel: Pull out image parsing to lib/pw_kernel_annotations 98bcbfc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/434512 pw_kernel: Allow annotations from userspace apps 2db35da:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/444192 roll: ninja aa7ded4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/430612 pw_toolchain: Update warning_exceptions.txt 4779fa7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/433958 pw_bluetooth_proxy: Call GATT delegates outside lock 7de1e3c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/416852 docs: Add vuln reporting instructions c2c00d8:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/443635 pw_env_setup: Switch to 3pp bloaty fe4cce9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/442672 zephyr: Migrate zephyr_cc_library to cc_library with @zephyr dep 59d6ea6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441452 pw_grpc: Fix uint32 overflow in HpackIntegerDecode e976805:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/416975 pw_async2: Add ValueListProvider 7579337:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/415132 pw_async2: Allow derived ValueFutures e7ae54b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/443513 pw_log: Minor docs fixes a19bcbb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/443312 pw_protobuf: Support submessages larger than 16KiB in BufferEncoder 20c74df:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/434569 pw_protobuf: Migrate C/C++ API reference a08c1f5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/442412 pw_containers: Add [[maybe_unused]] to IntrusiveItemType using alias Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 62bd30d9d8a0f9..25daf7f2266bd1 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8674533152306313905 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0238938b2bd756c77869a8fa676a4b157f00a4c1 Reviewed-on: https://pigweed-review.googlesource.com/c/open-dice/+/447132
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.