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

162 lines
6.0 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
# 构建 syvault TA + CA(armv7 / armhf),签名并校验
#
# 与 build_ta_ca.sh 的差别:
# 1. 多一个内部 crate `syvault-core`(纯 no_std 逻辑),TA 和 CA 都要用,
# 所以两边各拷一份进 SDK —— path 依赖必须落在同一个 workspace 树里。
# 2. TA 有 `board` feature:默认(不带)= 模拟设备身份,便于在 QEMU 里做
# 「两台设备互相解不开」的实验;带 `board` = 从 SLCR 读 Device DNA。
# 3. 顺带把 CA 也编出来。
#
# 用法:
# # QEMU / 模拟设备 A(注意 VAULT_SIM_DEV 是**编译期**常量,换值要重编)
# VAULT_SIM_DEV=dev-A bash build/build_vault.sh
#
# # 模拟设备 B(拿到 A 的 blob 去解,应当失败)
# VAULT_SIM_DEV=dev-B OUT_PREFIX=syvault-devB bash build/build_vault.sh
#
# # 真板:从 SLCR 读 DNA
# TA_FEATURES=board bash build/build_vault.sh
#
# 必需环境变量:
# OPTEE_OS optee_os 源码目录(已按 PLATFORM=zynq7k 或 qemu 构建过,有 export-ta_arm32)
# SDK_DIR teaclave-trustzone-sdk 目录
# OPTEE_CLIENT_EXPORT optee_client 的 out/export(CA 链接 libteec 用;不给就用 $OPTEE_OS/../optee_client/out/export)
set -euo pipefail
REPO="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
OPTEE_OS="${OPTEE_OS:?需要指向 optee_os 源码目录}"
SDK_DIR="${SDK_DIR:?需要指向 teaclave-trustzone-sdk 目录}"
OPTEE_CLIENT_EXPORT="${OPTEE_CLIENT_EXPORT:-$(dirname "$OPTEE_OS")/optee_client/out/export}"
UUID="3f7a1c92-5d84-4b6e-8f21-9c0d5e6b7a31"
TA_PKG="syvault-rs-ta"
CA_PKG="syvault-rs"
TARGET="arm-unknown-linux-gnueabihf"
TA_FEATURES="${TA_FEATURES:-}"
OUT_PREFIX="${OUT_PREFIX:-syvault}"
OUT_DIR="${OUT_DIR:-$REPO/artifacts/vault}"
SIGN_KEY="${SIGN_KEY:-}" # 留空 = 开发密钥 default_ta.pem
# ---- TA dev kit ----
DK=""
for cand in "$OPTEE_OS/out/zynq7k/export-ta_arm32" "$OPTEE_OS/out/arm/export-ta_arm32"; do
[ -d "$cand" ] && DK="$cand" && break
done
[ -n "$DK" ] || { echo "找不到 TA dev kit(先编 optee_os:PLATFORM=zynq7k)" >&2; exit 1; }
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}"
# 板级 DNA 读取:编译期注入模拟身份,只在非 board 模式有意义
if [ -n "${VAULT_SIM_DEV:-}" ]; then
export VAULT_SIM_DEV
echo "== 模拟设备身份 VAULT_SIM_DEV=$VAULT_SIM_DEV(编译期常量)=="
fi
echo "== 0. 把源码摆进 SDK 的 workspace =="
# 幂等:先删后拷,避免上一轮的残留影响判断
for ws in ta ca; do
rm -rf "$SDK_DIR/examples/$ws/syvault-core"
cp -a "$REPO/src/vault-core" "$SDK_DIR/examples/$ws/syvault-core"
rm -rf "$SDK_DIR/examples/$ws/syvault-core/target"
rm -rf "$SDK_DIR/examples/$ws/syvault-core/.git"
done
rm -rf "$SDK_DIR/examples/ta/syvault-rs-ta" "$SDK_DIR/examples/ca/syvault-rs"
cp -a "$REPO/src/ta-vault" "$SDK_DIR/examples/ta/syvault-rs-ta"
cp -a "$REPO/src/ca-vault" "$SDK_DIR/examples/ca/syvault-rs"
# members 注入(显式列表的话才需要;通配的话这一步是 no-op)
python3 - "$SDK_DIR/examples/ta/Cargo.toml" syvault-core "$TA_PKG" <<'PY'
import sys
path = sys.argv[1]
for name in sys.argv[2:]:
s = open(path).read()
if f'"{name}"' not in s and "members" in s:
s = s.replace("members = [", f'members = [\n "{name}",', 1)
open(path, "w").write(s)
print(f" members += {name}")
else:
print(f" members 已含 {name}(或该 workspace 用通配),跳过")
PY
python3 - "$SDK_DIR/examples/ca/Cargo.toml" syvault-core "$CA_PKG" <<'PY'
import sys
path = sys.argv[1]
for name in sys.argv[2:]:
s = open(path).read()
if f'"{name}"' not in s and "members = [" in s:
s = s.replace("members = [", f'members = [\n "{name}",', 1)
open(path, "w").write(s)
print(f" members += {name}")
else:
print(f" members 已含 {name}(或该 workspace 用通配),跳过")
PY
# ---- dyn_list:绕过 cargo-optee 就得自己放 ----
cd "$SDK_DIR/examples/ta"
[ -f dyn_list ] || cat > dyn_list <<'EOF'
{
__elf_phdr_info;
trace_ext_prefix;
trace_level;
ta_head;
};
EOF
echo "== 1. 编 TA(features: ${TA_FEATURES:-<none>})=="
if [ -n "$TA_FEATURES" ]; then
cargo build -p "$TA_PKG" --target "$TARGET" --release --features "$TA_FEATURES"
else
cargo build -p "$TA_PKG" --target "$TARGET" --release
fi
ELF="$SDK_DIR/examples/ta/target/$TARGET/release/$TA_PKG"
[ -f "$ELF" ] || { echo "没找到 TA 产物 $ELF" >&2; exit 1; }
file "$ELF"
echo "== 2. 编 CA =="
cd "$SDK_DIR/examples/ca"
[ -d "$OPTEE_CLIENT_EXPORT" ] || { echo "找不到 OPTEE_CLIENT_EXPORT=$OPTEE_CLIENT_EXPORT" >&2; exit 1; }
OPTEE_CLIENT_EXPORT="$OPTEE_CLIENT_EXPORT" \
cargo build -p "$CA_PKG" --target "$TARGET" --release
CA_ELF="$SDK_DIR/examples/ca/target/$TARGET/release/$CA_PKG"
[ -f "$CA_ELF" ] || { echo "没找到 CA 产物 $CA_ELF" >&2; exit 1; }
file "$CA_ELF"
echo "== 3. 签名 + 校验 =="
mkdir -p "$OUT_DIR"
TA_OUT="$OUT_DIR/$OUT_PREFIX.ta"
CA_OUT="$OUT_DIR/${OUT_PREFIX}_ca"
KEY="${SIGN_KEY:-$DK/keys/default_ta.pem}"
[ -f "$KEY" ] || { echo "找不到签名密钥 $KEY" >&2; exit 1; }
python3 "$DK/scripts/sign_encrypt.py" sign-enc \
--uuid "$UUID" --in "$ELF" --out "$TA_OUT" --key "$KEY"
python3 "$DK/scripts/sign_encrypt.py" verify \
--uuid "$UUID" --in "$TA_OUT" --key "$KEY"
cp -f "$CA_ELF" "$CA_OUT"
sha256sum "$TA_OUT" "$CA_OUT" > "$OUT_DIR/SHA256SUMS" 2>/dev/null || \
shasum -a 256 "$TA_OUT" "$CA_OUT" > "$OUT_DIR/SHA256SUMS"
cat <<EOT
产物:
$TA_OUT
$CA_OUT
$OUT_DIR/SHA256SUMS
部署到目标机:
cp $TA_OUT /lib/optee_armtz/$UUID.ta
cp $CA_OUT /usr/bin/$OUT_PREFIX
tee-supplicant -d /dev/teepriv0 &
$OUT_PREFIX selftest # 期望最后一行:VAULT_ALL_OK
⚠️ 默认用的是开发签名密钥。量产要换 SIGN_KEY,并把 TA 签名公钥编进 tee.bin,
否则 TA 可被替换(见 docs/05 §4)。
EOT