[security] Store auth tokens as SHA-256 hashes instead of plaintext #34

Open
opened 2026-03-04 12:20:00 +01:00 by clawbot · 0 comments
Collaborator

From QA Audit (#25 comment)

Severity: SHOULD-FIX

The clients.token column stores the raw 64-character hex token. If the database file is compromised, all active session tokens are immediately usable.

Suggested fix: Store SHA-256(token) in the database; compare against the hash on lookup.

## From QA Audit ([#25 comment](https://git.eeqj.de/sneak/chat/issues/25#issuecomment-10914)) **Severity: SHOULD-FIX** The `clients.token` column stores the raw 64-character hex token. If the database file is compromised, all active session tokens are immediately usable. **Suggested fix:** Store `SHA-256(token)` in the database; compare against the hash on lookup.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/chat#34
No description provided.