T

Restrict ssh-keyscan to -t rsa to avoid tripping rate limiting

Latest diagnostic run showed aquaria's OpenSSH responding fine on the
first of several near-simultaneous connections ssh-keyscan opens (one
per default-probed key type), then hanging on the rest with no
response — a rate-limiting signature, not an outright ban. Both hosts
confirmed to offer an RSA host key, so scan just that type: one
connection per host instead of ~4 at once. Left the diagnostic step in
to confirm before removing it. Dropped -v now that the cause is known.

2026-08-13 15:44:15 +00:00

.gitea/workflows

Restrict ssh-keyscan to -t rsa to avoid tripping rate limiting

2026-08-13 15:44:15 +00:00

content

Theme update

2026-08-13 15:00:56 +02:00

themes

Theme update

2026-08-13 16:02:08 +02:00

.gitignore

Site update