Skip to content
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

security: make the bcrypt cost configurable #12699

Open
cockroach-teamcity opened this issue Jan 10, 2022 · 0 comments
Open

security: make the bcrypt cost configurable #12699

cockroach-teamcity opened this issue Jan 10, 2022 · 0 comments

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jan 10, 2022

Exalate commented:

cockroachdb/cockroach#74582 --- Release note (security update): For context, when configuring passwords for SQL users, if the client presents the password in cleartext via ALTER/CREATE USER/ROLE WITH PASSWORD, CockroachDB is responsible for hashing this password before storing it. By default, this hashing uses CockroachDB's bespoke crdb-bcrypt algorithm, itself based off the standard Bcrypt algorithm. The cost of this hashing function is now configurable via the new cluster setting server.user_login.password_hashes.default_cost.crdb_bcrypt. Its default value is 10, which corresponds to an approximate password check latency of 50-100ms on modern hardware. This value should be increased over time to reflect improvements to CPU performance: the latency should not become so small that it becomes feasible to bruteforce passwords via repeated login attempts. Future versions of CockroachDB will likely update the default accordingly.

Jira Issue: DOC-2278

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants