-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No static cookieSecret default #2882
Conversation
🦋 Changeset is good to goLatest commit: 774efeb We got this. This PR includes changesets to release 24 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Additional idea: should we throw an error if a short secret is provided? Less than 10 length, maybe? |
This looks great!
You can still fit 160 bits of entropy in a 10 char string though (if you're trying hard enough), and that's not too bad. Maybe warning rather than error is better? We can shepherd people in the right direction but if they're explicitly setting the secret to a short string, it's not really our place to stop them. Additionally, I'm tempted to suggest checking against a blacklist, like we do for the Password field. This tends to catch more silly stuff than pure length checks... might be overkill though. For now I'd be happy either:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
Actually, I think I'll give a little more thought before adding any additional warnings. 🤔 It might be annoying to someone who wants to use a short secret to always get the warnings. Will handle separately. |
Resolves #2880 as @molomby proposed. Random secret generation taken from his code in WestpacGEL/GEL#379.