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.
This commit is contained in:
+4
-4
@@ -425,10 +425,10 @@ shadow entry and OpenSSH password policy with `debugfs`. Firecracker only sees
|
||||
the resulting private copy. Never change that to a shared writable rootfs.
|
||||
|
||||
Guest images must provide `/etc/passwd`, `/etc/shadow`, OpenSSH's
|
||||
`/etc/ssh/sshd_config`, the requested account, and their own first-boot SSH
|
||||
host-key generation. UVM does not create missing users. The known public demo
|
||||
key in Firecracker's bionic image is removed from private VM disks. A shared
|
||||
template must never contain reusable SSH host private keys.
|
||||
`/etc/ssh/sshd_config`, and the requested account. UVM does not create missing
|
||||
users. It replaces conventional RSA, ECDSA, and Ed25519 host keys in each
|
||||
private disk and removes the known public login key from Firecracker's bionic
|
||||
image. A VM must never rely on reusable SSH private keys from a shared template.
|
||||
|
||||
### Integrity Model
|
||||
|
||||
|
||||
Reference in New Issue
Block a user