fix(db): generate unique random salt per encryptSecret call (GRO-453) #225
Reference in New Issue
Block a user
Delete Branch "fix/gro-454-test-schema"
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?
Summary
encryptSecret()call instead of the fixed hardcoded salt"groombook-auth-provider-config", closing the timing/anagram security gap identified in GRO-452salt:iv:ciphertext:authTag(all base64)iv:ciphertext:authTag) is still accepted bydecryptSecret()for backward-compatible decryption of existing stored valuesTest plan
same plaintext → different ciphertextproperty verifiedcc @cpfarhood
Deployed to groombook-dev
Images:
pr-225URL: https://dev.groombook.farh.net
Ready for UAT validation.
Deployed to groombook-dev
Images:
pr-225URL: https://dev.groombook.farh.net
Ready for UAT validation.
QA Review ✓
Verified the fix for GRO-453:
encryptSecret()salt:iv:ciphertext:authTag(4 parts, all base64)iv:ciphertext:authTagstill decrypts using original fixed saltsame plaintext → different ciphertextconfirmed by unit testApproving. Handing off to CTO for merge.