The Killswitch — The Single Most Valuable Button

Every layer in this quest serves one moment: the day you realize a device is gone. The killswitch is what you do in that moment. It must be: fast (one click), complete (kills every cookie), recoverable (you can log back in), and reachable from any other device.

What "killswitch" means in concrete terms

Action	What it affects	SQL
Revoke All Sessions	Every browser session everywhere is logged out on next request	`DELETE FROM security_sessions`
Disable PIN globally (DON'T)	Sets a flag that bypasses auth entirely	NEVER — this is the inverse of what you want
Add specific IP to blacklist	That source IP can't even attempt login	`INSERT INTO security_blacklist`
Tighten retry limit temporarily	Lower max_retry from 5 to 2 during incident	`UPDATE security_config SET max_retry = 2`

The UI — make it big and red

The button needs to be findable in panic. Hide it behind one confirm dialog ("Revoke all 3 active sessions?") so a misclick doesn't blow up your day, but no further — every extra click is a second when your stuff is exposed.

Code

The endpoint (with audit logging)·python

@app.post("/admin/security/revoke-all")
async def revoke_all(request: Request):
    require_admin(request)
    cur = db.execute("DELETE FROM security_sessions")
    db.commit()
    audit_log("revoke_all", actor_ip=client_ip(request), count=cur.rowcount)
    return {"revoked": cur.rowcount}

The button — big, red, one-confirm·html

<button
  class="btn-danger"
  onclick="if(confirm('Revoke ALL active sessions? Every device must re-PIN.')) revokeAll()"
>
  🚨 Revoke All Sessions
</button>

The Killswitch — The Single Most Valuable Button

What "killswitch" means in concrete terms

The UI — make it big and red

Code

External links

Exercise

Progress

Comments 0