Files
ssw 60b6fa6f7b vault: 设备绑定密钥 + 密封存储(宿主 16 用例 / QEMU VAULT_ALL_OK / 签名验收通过)
- src/vault-core: no_std 密码学核心(HKDF 派生、AES-256-GCM、两条水位线防回滚)
- src/ta-vault / src/ca-vault: TA 薄壳与 selftest 客户端
- build/p1_vault_qemu.sh: QEMU 全链,判据 VAULT_ALL_OK
- build/p2_ta_keys_qemu.sh: TA 公钥编进 tee.bin,默认密钥签的被拒
- build/gen_ta_keys.sh: 自建签名密钥
- docs/07-VAULT-TA.md: 设计 + 已验证/未验证清单
- CLAUDE.md 雷区 11-16:user_ta_header、嵌套 workspace、ARCH=arm、SIGPIPE、TA_PUBLIC_KEY、heredoc 变量
2026-10-28 14:37:04 +08:00

77 lines
2.5 KiB
Bash
Executable File
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
#!/usr/bin/env bash
# 构建 Rust TA(armv7 / OP-TEE)+ 签名
#
# ⚠️ 下面的命令是 2026-10-27 在容器里**逐条跑通**的版本(见 P0-RESULTS.md §3)。
# 与 SDK 自带的 Makefile 不同:**故意绕过 `cargo-optee`**(它因 edition2024 编不过)。
#
# 用法:
# ./build.sh # 构建 hello_rust-rs-ta 并签名
# PKG=hello_world-rs-ta ./build.sh # 构建 SDK 官方示例做对照
#
# 必须先准备好的环境(缺一个都会报错,报错信息见 P0-RESULTS §2):
# OPTEE_OS optee_os 源码目录(已按 PLATFORM=zynq7k 构建过)
# SDK_DIR Teaclave TrustZone SDK 目录
# TA_DIR 你的 TA crate 所在目录(必须是 <SDK_DIR>/examples/ta 的成员)
set -euo pipefail
OPTEE_OS="${OPTEE_OS:?需要指向 optee_os 源码目录}"
SDK_DIR="${SDK_DIR:?需要指向 teaclave-trustzone-sdk 目录}"
TA_DIR="${TA_DIR:-$SDK_DIR/examples/ta}"
PKG="${PKG:-hello_rust-rs-ta}"
UUID="${UUID:-0f9c2b1a-7c1e-4d7e-9a4b-3f5c8d2e6a10}"
TARGET="arm-unknown-linux-gnueabihf"
DK="$OPTEE_OS/out/zynq7k/export-ta_arm32"
[ -d "$DK" ] || { echo "找不到 TA dev kit: $DK(先按 PLATFORM=zynq7k 编 optee_os)"; exit 1; }
# ---- 必需环境变量(这 4 个是踩坑得来的,一个都不能少)----
export TA_DEV_KIT_DIR="$DK"
export CROSS_COMPILE="${CROSS_COMPILE:-arm-linux-gnueabihf-}"
export CARGO_TARGET_ARM_UNKNOWN_LINUX_GNUEABIHF_LINKER="${CROSS_COMPILE}gcc"
export CC_arm_unknown_linux_gnueabihf="${CROSS_COMPILE}gcc"
export RUSTUP_TOOLCHAIN="${RUSTUP_TOOLCHAIN:-nightly-2026-08-05}" # 跟 SDK 的 rust-toolchain.toml 走
cd "$TA_DIR"
# ---- dyn_list:cargo-optee 才会生成,绕过它就得自己放一份 ----
[ -f dyn_list ] || cat > dyn_list <<'EOF'
{
__elf_phdr_info;
trace_ext_prefix;
trace_level;
ta_head;
};
EOF
echo "== 1. 编译 TA =="
cargo build -p "$PKG" --target "$TARGET" --release
ELF="target/$TARGET/release/$PKG"
[ -f "$ELF" ] || { echo "没找到产物 $ELF"; exit 1; }
echo " 产物: $ELF"
file "$ELF"
echo "== 2. 签名 =="
OUT="${OUT:-$PWD/$PKG.ta}"
python3 "$DK/scripts/sign_encrypt.py" sign-enc \
--uuid "$UUID" \
--in "$ELF" \
--out "$OUT" \
--key "$DK/keys/default_ta.pem"
echo " 产出: $OUT"
echo "== 3. 校验 =="
python3 "$DK/scripts/sign_encrypt.py" verify \
--uuid "$UUID" --in "$OUT" --key "$DK/keys/default_ta.pem"
python3 "$DK/scripts/sign_encrypt.py" display --in "$OUT" | head -8
cat <<EOT
部署到目标机:
mkdir -p /lib/optee_armtz
cp $OUT /lib/optee_armtz/$UUID.ta
tee-supplicant &
./hello_ca
EOT