docs(security): 2.4.0 at-rest encryption key advisory + --encryption-key - #79
Open
lakhansamani wants to merge 1 commit into
Open
docs(security): 2.4.0 at-rest encryption key advisory + --encryption-key#79lakhansamani wants to merge 1 commit into
lakhansamani wants to merge 1 commit into
Conversation
The at-rest key was keyed to --jwt-secret, which RSA/ECDSA installs legitimately leave empty, so TOTP seeds and OTP digests were protected by a publicly computable constant. Documents affected versions (2.2.1-rc.2 through 2.4.0-rc.13), who is and is not affected, and the remediation. Also corrects the existing at-rest and key-rotation sections, which still named --jwt-secret as the encryption key, and adds the --encryption-key flag reference.
✅ Deploy Preview for authorizerdev-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the security advisory and breaking change from authorizerdev/authorizer#742.
2.2.1-rc.2→2.4.0-rc.13, RSA/ECDSA only, with an affected/not-affected table and remediation steps.--jwt-secretkeys the encryption. It doesn't any more, and the runtime error message they quoted was stale.--encryption-keyreference in server-config, with the three-state behaviour table (set / falls back / refuses to start).Also advises setting
--encryption-keyexplicitly even on HMAC installs: while it and--jwt-secretare the same value, rotating the JWT secret — routine on its own — silently destroys every TOTP enrolment, because the at-rest key has no re-encryption path.Verified with
npm run build; new anchors resolve.