preflight.sh — the live-URL checks nobody runs #9
Labels
No Label
P0
P1
P2
release-blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Project-Template#9
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Four checks that are mechanical, take minutes, and are absent here: security headers present (a CSP and a frame policy), TLS with nothing served over plain HTTP, authentication rate-limited under repeated bad credentials, and login or reset responses that do not confirm whether an account exists.
They belong in a script rather than a page nobody re-reads. Exit 0 clean, 1 findings each named, 2 the site could not be reached -- which is not a pass.
One piece of care the source of this list does not have. Two of the checks -- repeated bad logins, and probing whether an account exists -- are indistinguishable from an attack in a log. It must refuse to run against a host that is not named in its own configuration, in the same spirit as status.sh having no --host flag: a one-keystroke mistake must not point it at somebody else's site.
(precautionary): externally evidenced, no incident here.
Verify: preflight.sh refuses a host it is not configured for, exits 2 when the host is unreachable, names each finding rather than counting them, and has its row in docs/architecture/README.md.