Enhance security by ensuring unique SSH host keys for VMs and protecting registry credentials. Update documentation to reflect changes in SSH key management and improve state file permissions.

2026-09-04 21:31:54 +00:00
parent 1022f24c34
commit a8dbc704e9
7 changed files with 147 additions and 16 deletions
@@ -306,7 +306,9 @@ UVM provisions a password for an existing account. The default credentials are

 - An SSH server.
 - The requested login user plus standard passwd and shadow files.
- Unique SSH host keys generated at first boot.
+
+UVM replaces conventional RSA, ECDSA, and Ed25519 SSH host keys in the private
+disk during creation and removes Firecracker's publicly known demo login key.

 This is applied only while creating a new VM. Existing VM disks and legacy
 registry entries are not changed retroactively.
@@ -747,7 +749,7 @@ Before relying on a VM for useful work:

 1. Use strict checksums for installed artifacts.
 2. Confirm `/dev/kvm` and nested virtualization are available.
-3. Use a guest image with unique first-boot SSH host keys and set a non-default password.
+3. Confirm UVM generated unique guest SSH host keys and set a non-default password.
 4. Test guest egress and SSH on the actual host network.
 5. Back up guest data before destroy operations.
 6. Keep the API loopback-only unless you have a strong remote-access need.