A fresh Server is now reachable by someone who has never made an SSH key. The field report behind this release is exactly that: people new to Linux, and Windows admins coming in with a password, could not get into a new Server at all, because the installer's key import assumes you already have a key. Key-only is still the default, and it is still the recommended answer. What changed is that there is a visible choice, taken with a warning, and it can be undone.
The console installer has an SSH login page with two answers: Keys only (recommended) or Keys or password. The Desktop installer has an Allow SSH logins with a password switch on its account screen, off by default. Both say plainly that a password can be guessed by anyone who can reach port 22.
Later, pengyos-ssh-password status | on | off decides it. on writes
/etc/ssh/sshd_config.d/50-pengyos-ssh-password.conf, validates it with sshd -t, and reloads
sshd; the Server's sshd.service gained an ExecReload for exactly that (sshd -t, then SIGHUP).
Every login then shows a reminder in /etc/motd.d/. status lists the keys each account has and,
while passwords are on, the commands that fix that: ssh-keygen, ssh-copy-id, and the PowerShell
line for Windows. off refuses while no account has a key, because then SSH would work for nobody;
--force overrides that.
None of it edits a file the image owns. The image's /etc/ssh/sshd_config now begins with
Include /etc/ssh/sshd_config.d/*.conf, which matters because sshd keeps the first value it reads,
so a drop-in can override PasswordAuthentication no cleanly. The drop-in lives in the /etc
overlay on the data partition, so it survives an update. Root never logs in with a password:
PermitRootLogin prohibit-password is unchanged.
One fix came in on the way: the line-by-line installer skipped its SSH page after you pressed Enter to skip Wi-Fi, so it never asked for a key.
This release also landed a build guard, invisible in the image. The post-build kernel-config check
read whichever linux-*/ build directory it found first, which after a version bump is often the
directory of the kernel you just replaced, so it could report a clean config for a kernel that was
not in the image. It now reads the .config of the kernel the image is configured to build. The
password drop-in in this release also set PerSourcePenalties authfail:15s, which broke
ssh-copy-id; that one is fixed in 26.11.7.