Skip to content

update bcrypt-cost comments to also add highest possible value#2311

Closed
rys wants to merge 1 commit intoergochat:masterfrom
rys:config-comments-bcrypt
Closed

update bcrypt-cost comments to also add highest possible value#2311
rys wants to merge 1 commit intoergochat:masterfrom
rys:config-comments-bcrypt

Conversation

@rys
Copy link
Copy Markdown

@rys rys commented Dec 20, 2025

While configuring a new server I mistakenly set bcrypt-cost in my server config to something much higher than allowed.

The error propagation for the passphrase checking logic returns the same error code for multiple paths out of that logic, so it took a good while to work out exactly why new account registration was failing after my misconfiguration.

Hopefully adding a note to the comments above bcrypt-cost in the config examples will help others discover their mistake in the same situation.

@slingamn
Copy link
Copy Markdown
Member

This should be a config validation error, I'll make a PR for that later :-)

@slingamn slingamn added this to the 2.18 milestone Dec 21, 2025
@slingamn slingamn added the bug label Dec 21, 2025
@slingamn
Copy link
Copy Markdown
Member

Out of curiosity, what cost did you end up using? We default to the minimum cost to speed up reconnection, especially for mobile clients. I'm interested in how operators are seeing those tradeoffs.

slingamn added a commit to slingamn/ergo that referenced this pull request Dec 22, 2025
Validate bcrypt-cost config value to prevent silent errors
@slingamn slingamn closed this in 462e568 Dec 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants