Bash Audit โ€” Step 1

STEP 1 COMPLETE AWAITING GREEN LIGHT ยท Walter ๐Ÿฆ‰ ยท March 16, 2026 17:10 UTC
Executing: plan-bash-upgrade-v2 โ†’ Step 1 (Audit all machines)
Plan: v1 (superseded) โ†’ v2 (active)

Bash Version Survey

MachineHostBash VersionStatus
๐Ÿฆ‰Walterwalter.1.foo5.2.21โœ“
๐Ÿฆ‰Walter Jrwalter-jr.1.foo5.2.15โœ“
๐ŸฆVaultvault.1.foo5.2.15โœ“
๐ŸŒธMatildamatilda.1.foo5.2.15โœ“
๐Ÿ•Jamiejamie.1.foo5.2.15โœ“
๐ŸฑAmyamy.1.fooโ€”VM stopped
๐Ÿ“‹Foremanforeman.1.fooโ€”SSH denied
๐Ÿฑ๐Ÿ‡ฎ๐Ÿ‡ฑAmy Israelamy-israel.1.fooโ€”VM stopped
๐Ÿค–RMSrms.1.fooโ€”VM stopped
๐Ÿš€Captain Kirkcaptain-kirk.1.fooโ€”VM stopped
๐Ÿ‘ปGhost Jrghost-jr.1.fooโ€”SSH timeout

Shebang Survey

Machine#!/bin/bash#!/usr/bin/env bash
Walter2 scripts (vault-snapshot.sh, snapshot-all.sh)0
Walter Jr00
Vault00
Matilda00
Jamie00

Only Walter has scripts with the old shebang โ€” two files in /home/daniel/bin/. All other reachable machines have no bash scripts or already use env bash.

Findings

VERDICT: ALL CLEAR

Every reachable machine runs Bash 5.2. No machine on Bash 3.2 or 4.x. The feared scenario did not materialize.

Walter: 5.2.21 (Ubuntu 24.04 Noble)
All others: 5.2.15 (Debian 12 Bookworm)
The version difference is cosmetic โ€” both are Bash 5.2 with different distro patches.

Remaining work (Step 3 of the plan):

Fix 2 shebangs on Walter:
โ€ข /home/daniel/bin/vault-snapshot.sh โ€” change #!/bin/bash โ†’ #!/usr/bin/env bash
โ€ข /home/daniel/bin/snapshot-all.sh โ€” change #!/bin/bash โ†’ #!/usr/bin/env bash

That's it. Two lines on one machine.

Unreachable machines (6 total) can be audited when next started. Given that every reachable machine is 5.2, the probability of a stopped Debian VM having 3.2 is effectively zero.

โธ STOP โ€” AWAITING GREEN LIGHT

Step 1 (audit) is complete. The plan says to stop here and wait.

Recommended next action: Skip Step 2 (no machines need fixing) and proceed directly to Step 3 โ€” fix the two shebangs on Walter. This is a two-line change.

Waiting for Daniel's green light to proceed.