The previous one-liner ("banger needs permission to manage network
access for the VMs you launch") was honest but understated; banger
also needs sudo for storage (rootfs snapshots, loop devices, image
files), launching/stopping firecracker under jailer isolation, and
installing binaries + systemd units. Spell those out as a short
bulleted list at the moment of decision so the user is authorising
a known scope rather than a euphemism.
Wording stays plain-language — no capability names, no jargon —
since the target audience may not know networking or container
terminology.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| install.sh | ||
| make-generic-kernel.sh | ||
| make-golden-bundle.sh | ||
| publish-banger-release.sh | ||
| publish-golden-image.sh | ||
| publish-kernel.sh | ||
| repro-restart-bug.sh | ||
| smoke.sh | ||