#!/usr/bin/env bash # Tests for the shutdown-schedule ratchet. # # This ratchet had no test at all, which is how MORNING_END_HOUR went # unchecked for months while the two evening hours were guarded. The direction # cases below are the point of the file: "stricter" means SMALLER for the # evening hours and LARGER for the morning end. # # Nothing here touches /etc: SHUTDOWN_CONFIG_FILE points at a tmpdir, and # chattr/guardctl are shimmed on PATH because chattr cannot mark a file # immutable on tmpfs and would abort the write. set -uo pipefail SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" readonly SCRIPT_DIR readonly TARGET="${SCRIPT_DIR}/../../adjust_shutdown_schedule.sh" PASS=0 FAIL=0 _t_pass() { PASS=$((PASS + 1)) printf ' OK: %s\n' "$1" } _t_fail() { FAIL=$((FAIL + 1)) printf ' FAIL: %s\n' "$1" } # The ratchet returns 0 to allow a write and 1 to block it. Which way it fails # is the entire point, so assert on the exit status explicitly. _t_allows() { local what="$1" shift if "$@" >/dev/null 2>&1; then _t_pass "$what" else _t_fail "$what (blocked when it should have allowed)" fi } _t_blocks() { local what="$1" shift if "$@" >/dev/null 2>&1; then _t_fail "$what (allowed when it should have blocked)" else _t_pass "$what" fi } _t_has() { local haystack="$1" needle="$2" what="$3" if [[ "$haystack" == *"$needle"* ]]; then _t_pass "$what" else _t_fail "$what (want substring '${needle}')" fi } TMP="$(mktemp -d)" trap 'rm -rf "$TMP"' EXIT # Shim the two commands that need root or a real filesystem. mkdir -p "$TMP/bin" cat >"$TMP/bin/chattr" <<'EOF' #!/bin/bash exit 0 EOF cat >"$TMP/bin/guardctl" <<'EOF' #!/bin/bash printf '%s' "${FAKE_CANONICAL:-}" EOF chmod +x "$TMP/bin/chattr" "$TMP/bin/guardctl" export PATH="$TMP/bin:$PATH" export SHUTDOWN_CONFIG_FILE="$TMP/shutdown-schedule.conf" export FAKE_CANONICAL="$TMP/canonical" write_config() { cat >"$SHUTDOWN_CONFIG_FILE" <"$SHUTDOWN_CONFIG_FILE" _t_allows "falls back to the loosest defaults rather than rejecting" \ check_stricter_only 23 23 0 echo "end to end" write_config 23 23 5 if (main 21 21 5 >/dev/null 2>&1); then _t_pass "a stricter write succeeds" else _t_fail "a stricter write succeeds" fi _t_has "$(cat "$SHUTDOWN_CONFIG_FILE")" "MON_WED_HOUR=21" "config was rewritten" _t_has "$(cat "$FAKE_CANONICAL")" "MON_WED_HOUR=21" "canonical copy was written too" write_config 21 21 5 if (main 23 23 5 >/dev/null 2>&1); then _t_fail "a looser write is refused" else _t_pass "a looser write is refused" fi _t_has "$(cat "$SHUTDOWN_CONFIG_FILE")" "MON_WED_HOUR=21" "config was left untouched" # --restore still bypasses the ratchet on purpose: the workout reward pushes the # schedule later than shutdown_base.json, so bounding it here would break a # daily flow. Bounding it is a separate, open decision. write_config 21 21 5 if (main --restore 23 23 5 >/dev/null 2>&1); then _t_pass "--restore still loosens (deliberately unchanged)" else _t_fail "--restore still loosens (deliberately unchanged)" fi echo printf 'passed: %d, failed: %d\n' "$PASS" "$FAIL" [[ $FAIL -eq 0 ]]