Release keys

Every Whitesmoke SMP release, the list of releases and the installer are signed with one of these keys. The installer refuses anything that isn't.

Key	Role	Fingerprint
`r_20261021_ydnetk`	active: signs releases	`SHA256:5ZLU2cN3c9GbRgSjbpVdD6m9Ix9pR5CTp4IRdynO+C4`
`r_20261021_u4y29j`	standby: kept offline, used only if the active key is lost	`SHA256:Lcu0nozrhu5BM9cxdobMY7mQgbPSaj/NzsGjPUy+cRA`

The same keys as an allowed_signers file, for ssh-keygen -Y verify:

whitesmoke-release namespaces="whitesmoke-release" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEs4Vd12oiDxgHoJEwmQokjCOlA910ALSCU56KDWjdOJ r_20261021_ydnetk
whitesmoke-release namespaces="whitesmoke-release" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKkh1BnfQVlmkfFvcgr2zFe0A1l4eJZQRQkJHbRsKC7N r_20261021_u4y29j

Check them against what your server trusts with cat /etc/whitesmoke/allowed_signers.

Key changes

A planned change: a release signed with the current key adds the new key. For at least 90 days after that, everything is signed with both, so every server can follow. Updating at least every couple of months is all you need to do; a server that misses those 90 days needs the manual path below.
A lost or stolen key: the standby key, which every server already trusts, signs a release that drops the old key. This page says which key was retired and when. Update at once.

"This update is signed with a newer key than this server knows"

Your server missed a key change. Update by hand, checking the installer yourself:

Download install.sh and its signature, and check it with the keys printed on this page, as in the careful install.

Run the checked file with --update:

sudo bash install.sh --update --accept-eula

From then on, sudo smp-update works again.