bvandeusenandClaude Opus 5.5
327d49428f
test-web / test (push) Successful in 2m4s
test-go / test (push) Successful in 2m23s
test-go / integration (push) Successful in 5m28s
release / Build signed APK (releases and dev) (push) Successful in 6m29s
release / Build + push container image (push) Successful in 29s
release / Verify release artifacts (tag releases only) (push) Skipped
users.api_token held each user's apiKey in plaintext and was looked up by equality, so a leaked row or backup handed out working keys. Migration 0063 replaces it with api_token_hash (sha256, hex), computed in place from the existing keys so every Subsonic client keeps working. The key can no longer be read back: GET /api/me/api-token is gone, and POST returns the new key once. Settings shows it right after Regenerate with a copy button and a "won't be shown again" note. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 lines
458 B
SQL
8 lines
458 B
SQL
-- The keys cannot be recovered from their hashes. Rolling back gives every
|
|
-- user a new random key; Subsonic clients using apiKey need the new one.
|
|
ALTER TABLE users ADD COLUMN api_token text;
|
|
UPDATE users SET api_token = md5(random()::text || id::text || clock_timestamp()::text);
|
|
ALTER TABLE users ALTER COLUMN api_token SET NOT NULL;
|
|
ALTER TABLE users ADD CONSTRAINT users_api_token_key UNIQUE (api_token);
|
|
ALTER TABLE users DROP COLUMN api_token_hash;
|