Repository navigation
YuCe 0.1.2
Use 0.1.3: it fixes silent flag typos,
applyexit codes and a damaged journal end, and states the results as far as they go.
YuCe 0.1.2: the benchmark suite reads sbgk verify's verdict again when a check fails.
0.1.1 made sbgk verify exit 1 when a check fails. The CLI wrappers of the benchmark suite took every non-zero exit for a
crash, so the tamper-attack experiment (python benchmarks/run_sbgk_suite.py --only 6), which verifies hundreds of tampered
containers and counts the ones caught, stopped at the first one. From 0.1.2 the wrappers take exit 1 from verify, with its
verdict on stdout, as the answer; every other non-zero exit is still a failure. A new test runs that experiment and checks
that every attack is caught.
The binaries behave as in 0.1.1 (verify: 0 verified, 1 a check failed, 2 usage error); the kernel, the audit server, the
demo and the benchmark results are unchanged. See CHANGELOG.md.
Assets
- Binaries:
yuce-v0.1.2-<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 neither
fix changes them.
Check a download with sha256sum -c SHA256SUMS-<platform>.txt.