Repository navigation
YuCe 0.1.1
Use 0.1.2. With this release's exit code, the tamper-attack experiment of the benchmark suite (
run_sbgk_suite.py --only 6) stops at its first tampered container; 0.1.2 fixes the suite. The binaries are the same in behaviour.
YuCe 0.1.1: sbgk verify now fails with exit code 1 when a check fails.
In 0.1.0, sbgk verify <container> printed "ok": false for a tampered container but still exited 0, so a script or a CI
step that reads only the exit code would take a tampered container for a sound one. From 0.1.1 it exits 1 when a check
fails, as sbgk audit-verify already did. The exit codes are now: 0 verified, 1 a check failed, 2 usage error. A new test
covers all three: the quickstart container, the same container with one bit flipped, and no container.
Nothing else changed: the kernel, the audit server, the demo and the benchmark results are the same as in 0.1.0. See
CHANGELOG.md.
Assets
- Binaries:
yuce-v0.1.1-<target>for Linux x86_64, Windows x86_64 and macOS (arm64, x86_64), each withsbgk, its aliasyuce, LICENSE, NOTICE, THIRD_PARTY_LICENSES.md and
README;SHA256SUMS-<platform>.txt. - The recorded runs of BENCHMARKS section 1 (journals, gradings, manifests) stay in the
v0.1.0 release: they were recorded with 0.1.0, and this
fix does not change them.
Check a download with sha256sum -c SHA256SUMS-<platform>.txt.