thanhnvandClaude Opus 4.8
664bd1f00c
Physically move the pure-code subtrees out of .specify into the package, leaving compat symlinks at the old .specify/<dir> paths so every existing reference (internal CASAN_HARNESS_ROOT + external CI/docker/mjs) keeps resolving. Runtime state stays put. Moved (git mv): scripts/ tests/ security/ templates/ config/ governance/ memory/ .specify/<dir> -> packages/casan-harness/<dir> (+ .specify/<dir> symlink) Stays in .specify (state/governance/domain, handled later): logs/ agentops/ level5/ init-options.json traceability-map.json Python `.resolve()` self-location followed the compat symlink into packages and lost the app root; generate-casan-demo-context.py, generate-agentops-dashboard.py and dashboard-server.py now walk UP for the `.specify` state marker instead of a fixed parent depth (fixes "missing trace files" in run-casan4). Full gate: PASS=64 FAIL=0 SKIP=3 (CASAN_CI_STEP_TIMEOUT_SEC=1200 — track-a ~450s runs close to the 600s default and can tip over under load; this is timing variance, not a regression — it passed cleanly with headroom). Runtime log/audit artifacts kept unstaged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
65 lines
2.2 KiB
Bash
65 lines
2.2 KiB
Bash
#!/usr/bin/env bash
|
|
set -uo pipefail
|
|
|
|
# CASAN Plan-16 SEC-20 (ARCH-04 / ARCH-09) — verify the required toolchain.
|
|
#
|
|
# Gate verdicts depend on external binaries (python/openssl/grep/sha256sum...). If
|
|
# one is MISSING the control can silently no-op (ARCH-09); if one is PATH-SHADOWED
|
|
# by an attacker-planted copy (ARCH-04, e.g. a fake `grep` that always matches
|
|
# nothing) the attacker controls the verdict. This fails CLOSED:
|
|
# * a required tool that is not found -> refuse,
|
|
# * a tool resolving INSIDE the workspace / cwd -> refuse (planted binary),
|
|
# * with CASAN_TOOLCHAIN_TRUSTED_DIRS set, a tool outside those dirs -> refuse.
|
|
#
|
|
# Usage: toolchain-verify.sh [tool ...] (default: python3 openssl grep awk sed)
|
|
# Env: CASAN_TOOLCHAIN_TRUSTED_DIRS=/usr/bin:/bin:... (opt-in allowlist; prod sets it)
|
|
# Exit: 0 ok, 1 missing/shadowed/untrusted.
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
PROJECT_ROOT="$(cd "$SCRIPT_DIR/../../.." && pwd)"
|
|
|
|
REQUIRED=("$@")
|
|
if [[ ${#REQUIRED[@]} -eq 0 ]]; then
|
|
REQUIRED=(python3 openssl grep awk sed)
|
|
fi
|
|
|
|
IFS=':' read -r -a TRUSTED <<< "${CASAN_TOOLCHAIN_TRUSTED_DIRS:-}"
|
|
|
|
fail=0
|
|
for tool in "${REQUIRED[@]}"; do
|
|
path="$(command -v "$tool" 2>/dev/null || true)"
|
|
if [[ -z "$path" ]]; then
|
|
echo "TOOLCHAIN_MISSING tool=$tool (fail-closed)" >&2
|
|
fail=1; continue
|
|
fi
|
|
# Resolve to a real, absolute path (follow the symlink dir).
|
|
dir="$(cd "$(dirname "$path")" 2>/dev/null && pwd -P || echo "")"
|
|
real="$dir/$(basename "$path")"
|
|
|
|
# A required tool resolving inside the repo / cwd is a planted-binary red flag.
|
|
case "$real" in
|
|
"$PROJECT_ROOT"/*|"$PWD"/*|./*)
|
|
echo "TOOLCHAIN_SHADOWED tool=$tool path=$real (fail-closed)" >&2
|
|
fail=1; continue ;;
|
|
esac
|
|
|
|
# Opt-in allowlist: in prod the tool MUST live under a trusted system dir.
|
|
if [[ -n "${CASAN_TOOLCHAIN_TRUSTED_DIRS:-}" ]]; then
|
|
ok=0
|
|
for pfx in "${TRUSTED[@]}"; do
|
|
[[ -n "$pfx" ]] || continue
|
|
case "$real" in "$pfx"/*) ok=1; break ;; esac
|
|
done
|
|
if [[ "$ok" -ne 1 ]]; then
|
|
echo "TOOLCHAIN_UNTRUSTED_PATH tool=$tool path=$real (not under CASAN_TOOLCHAIN_TRUSTED_DIRS)" >&2
|
|
fail=1
|
|
fi
|
|
fi
|
|
done
|
|
|
|
if [[ "$fail" -eq 0 ]]; then
|
|
echo "TOOLCHAIN_OK tools=${#REQUIRED[@]}"
|
|
exit 0
|
|
fi
|
|
exit 1
|