DR SAN authentication and growth lab, 2026-10-04

This original lab extends the earlier runtime experiment. Run only in a new
RAM-root, diskless disposable Linux VM with no unrelated storage sessions.
The script refuses pre-existing data disks, maps and storage daemons. It creates
one 64-MiB RAM file, grows it to 96 MiB, and authenticates two guest-loopback
iSCSI sessions to the same resource. All credentials in run.py and evidence are
PUBLIC SYNTHETIC TRAINING VALUES. They protect no real system and must never be
reused in one. This is not a production security configuration or runbook.

Fourteen groups passed twice with Alpine 3.24.2, Linux 6.18.52-0-virt aarch64,
Open-iSCSI 2.1.12-r0, multipath-tools 0.13.0-r0 and TGT 1.0.97-r0.
The target authenticates the initiator. Mutual authentication, encrypted
transport, real secret rotation and enterprise algorithm policy were not tested.
The target is taken offline and its grown backing file reopened while lab I/O
is quiesced. No online physical-array expansion is claimed. No filesystem,
application workload, independent fabric, abrupt failure, benchmark or crash
durability is tested. Primary rolling documentation is distinct from the actual
package versions recorded in each report.

Use a fresh temporary host share only. Guest networking is user NAT without
forwarded ports. iSCSI uses guest loopback. No host disks are attached. The old
verified Alpine ISO was reused after comparing its SHA-256 again; the original
official checksum had matched. No signature verification is claimed.

Recorded macOS bootstrap
The included boot.py and guest.py retain the exact temporary work path used:
/tmp/dr-san-growth-work. They are evidence/replay helpers, not an installer.
Do not overwrite that path if it exists or belongs to another execution.
For a fresh replay, change both helpers' w paths to a NEW empty temporary
directory, and put setup.sh and run.py into its share/ subdirectory.
The host used an already installed UTM QEMU 7.2.0 framework. This is the tested
emulator, not a recommendation of the latest release. qemu-launch.c is an
original minimal CLI loader. It does not start UTM user VMs or modify UTM state.
On the recorded host it was compiled using:
clang -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX26.5.sdk qemu-launch.c -Wl,-rpath,/Applications/UTM.app/Contents/Frameworks -o qemu-launch
Copy that executable to the selected work directory; review the framework paths
in boot.py. A normal qemu-system-aarch64 executable can replace the loader and
framework argument, but that alternative bootstrap was not executed here.

ISO preparation
Download the ISO and checksum URLs from acquisition.json over HTTPS into the
new work directory. Compare SHA-256 with both the official checksum and the
recorded hash. Preserve any mismatch and stop. Extract boot/vmlinuz-virt and
boot/initramfs-virt from the ISO using an ISO reader (macOS bsdtar was used).
The recorded kernel is EFI zboot. For this QEMU direct boot, its gzip payload
was extracted with Python: read offset,length using struct.unpack_from('<II',
kernel_bytes,8), then gzip.decompress(kernel_bytes[offset:offset+length]).
Check the resulting bytes at [56:60] equal b'ARM\x64', and compare SHA-256 with
acquisition.json.kernelExtraction.uncompressedSha256. Save as boot/Image.
Do not apply this format-specific extraction blindly to a different kernel.

Execution
Run boot.py to start the owned VM, log into its ephemeral root console, mount
only the temporary share and run setup.sh. Inspect share/setup.txt and require
successful installation and the marker /run/dr-san-disposable. Repositories are
Alpine v3.24 official main/community; replay at a later date may resolve newer
packages. Record actual versions and do not relabel them as the recorded run.
Then, using the included serial helper:
python3 guest.py 'python3 /mnt/dr/run.py --output /mnt/dr/evidence.json > /mnt/dr/run.txt 2>&1' 90
Require the DR_DONE marker to end in :0, no Python traceback, passed=14, failed=0,
and failure=null in the output JSON. The helper prints remote status; its own
exit code alone is not a guest-success assertion. Repeat with a separate output
filename. Compare the script hash, explicit CHAP denial, capacity sequence and all fourteen groups. sdX names and timestamps may differ. Require wrongChapRejected.returncode=24, no sessions/disks after denial, one-path sizes 96/64 MiB, both-path sizes 96/96 MiB with map still 64 MiB, resized map 96 MiB, old marker preserved, new marker at 80 MiB and two authenticated paths after rejoin. Inspect stderr as well as exit status.

Cleanup and review
The script closes the map, logs out the exact owned sessions, deletes its target,
account and node records, stops its daemons in separate process sessions,
restores three saved configuration files (including remembered WWIDs), and
removes its backing directory. Each report confirms no sessions/disks/map and
ownedAccountRemoved/configurationRestored=true. Existing directories may remain
inside the disposable VM. Do not use broad delete or logout commands elsewhere.
If a command times out, inspect the same owned VM and keep failure evidence;
do not blindly restart it or bypass the preconditions. After collecting evidence,
check the three owned daemons and map are absent, issue poweroff in the guest
and confirm the exact QEMU PID from vm.json exited. The recorded PID was 60980.

Learning tasks
Use worksheet.txt to predict the capacity transitions, interpret authentication
failure, plan per-portal rotation and prepare an English RUN handover. The
worksheet is authored, not a record of a human workshop. Independent specialist
review and representative platform/application acceptance remain outstanding.
