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

Turn default hash password algorightm back to pbkdf2 from argon2 until we found a better one (#14673) #14675

Merged
merged 3 commits into from
Feb 13, 2021

Conversation

lunny
Copy link
Member

@lunny lunny commented Feb 13, 2021

backport from #14673

  • Turn default hash password algorightm back to pbkdf2 from argon2 until we found a better one
  • Add a warning on document

…l we found a better one (go-gitea#14673)

* Turn default hash password algorightm back to pbkdf2 from argon2 until we found a better one

* Add a warning on document
@lunny lunny added the pr/breaking Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it! label Feb 13, 2021
@lunny lunny added this to the 1.13.3 milestone Feb 13, 2021
@lunny lunny mentioned this pull request Feb 13, 2021
6 tasks
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Feb 13, 2021
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Feb 13, 2021
@6543
Copy link
Member

6543 commented Feb 13, 2021

.

@6543 6543 merged commit c032006 into go-gitea:release/v1.13 Feb 13, 2021
@lunny lunny deleted the lunny/default_hash_pbkdf2_2 branch February 15, 2021 03:20
@6543 6543 added the topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! label Mar 21, 2021
@go-gitea go-gitea locked and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. pr/breaking Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it! topic/security Something leaks user information or is otherwise vulnerable. Should be fixed!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants