Verify-dns answers for the present, not for a stored flag

FixSecurityService
Ya
23 Agosti 2026, 05:31 UTC
Mwandishi
Kamo
Ahadi ya
5d17106

The endpoint skipped probing entirely when ssl_confirmed was already true, on the reasoning that under the all-hosts rule it could only have been set when every host was live. That is only true of rows written by the new rule. Rows written by the old any-one-host rule carry a true flag over hosts that never had a certificate, and certificates lapse on their own afterwards — so the shortcut handed /setup/dns a green light for exactly the domains most likely to be broken, and Enter Workspace is gated on it. Probe every host on every check and report what is actually live. Hosts found bare are re-seeded, which heals a stale-confirmed domain the moment someone opens the page instead of waiting for the next drift sweep. The probes are concurrent and capped, so this costs about a second. A false is reported but never written back: one probe run is thin evidence for withdrawing a tenant's confirmation, and reverifyConfirmed() already does that from a corroborated verdict. The response is honest either way, and the response is what gates the button.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei