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

[feat] Allow configuring argon2id parameters #4291

Open
wants to merge 40 commits into
base: develop
Choose a base branch
from

Conversation

elland
Copy link
Contributor

@elland elland commented Oct 10, 2024

https://wearezeta.atlassian.net/browse/WPB-9746

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@echoes-hq echoes-hq bot added the echoes: security Security related changes or defects label Oct 10, 2024
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Oct 10, 2024
Comment on lines -392 to -402
(Data.reauthenticate uid Nothing) `catchE` \case
ReAuthMissingPassword -> pure ()
ReAuthCodeVerificationRequired -> pure ()
ReAuthCodeVerificationNoPendingCode -> pure ()
ReAuthCodeVerificationNoEmail -> pure ()
ReAuthError e -> case e of
AuthInvalidUser -> throwE LoginFailed
AuthInvalidCredentials -> pure ()
AuthSuspended -> throwE LoginSuspended
AuthEphemeral -> throwE LoginEphemeral
AuthPendingInvitation -> throwE LoginPendingActivation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change is extremely hard to understand, and i think it has at least one error hidden deep inside: BadCredentials and InvalidUser are flipped.

are all the changes in names, order, and structure really necessary?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akshaymankar akshaymankar changed the title [feat] Make Argon parameters configurable through Brig environment variables. [feat] Make Argon parameters configurable through config options Oct 16, 2024
- passwordHashingOptions are no longer optional in settings, expect helm
  chart to have set the right defaults.
- Brig.Provider.DB no longer hashes password, it expects hashed password
  to be passed in. Functions at higher level call HashPassword effect.
  These will eventually move to AuthenticationSubsystem (or something
  similar for providers)
Optimize for test run time, not security.
Was here to inspect CI env.
@akshaymankar akshaymankar changed the title [feat] Make Argon parameters configurable through config options [feat] Allow configuring argon2id parameters Oct 16, 2024
Reorg changelog, so important things go on top.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
echoes: security Security related changes or defects ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants