2 commits

Author	SHA1	Message	Date
Loïc Dachary	db86c93b0b	[SECURITY] default to pbkdf2 with 320,000 iterations ... (cherry picked from commit 3ea0b287d7) (cherry picked from commit db8392a8ac) (cherry picked from commit bd2a5fa292) (cherry picked from commit 2436acb3d9) (cherry picked from commit 62f50e1c52) (cherry picked from commit dba1892521) (cherry picked from commit 4b58e3b6d4) (cherry picked from commit 1247056856) (cherry picked from commit afbaea7009) (cherry picked from commit dcd4813d96) (cherry picked from commit b51dc963d1) (cherry picked from commit 611e895efd) (cherry picked from commit fd492a03f5) (cherry picked from commit 2c99991f44) (cherry picked from commit 7426c1edb4) (cherry picked from commit 373244f8b2) (cherry picked from commit 4f6efecdb9) (cherry picked from commit 61d500808e) (cherry picked from commit 65f8384b63) (cherry picked from commit 12ed28e734) (cherry picked from commit ec6cdc9e1a) (cherry picked from commit 08653ba051) (cherry picked from commit d5847c87cb) (cherry picked from commit 640a96e19b) (cherry picked from commit 46177814a9) (cherry picked from commit b0098f5a80) (cherry picked from commit ce5ddeeca9) (cherry picked from commit 5736fa1025) (cherry picked from commit c43ca210fc) (cherry picked from commit 7f92906bf3) (cherry picked from commit f726525d2d)	2023-10-02 17:06:22 +02:00
zeripath	61b89747ed	Provide the ability to set password hash algorithm parameters (#22942) ... This PR refactors and improves the password hashing code within gitea and makes it possible for server administrators to set the password hashing parameters In addition it takes the opportunity to adjust the settings for `pbkdf2` in order to make the hashing a little stronger. The majority of this work was inspired by PR #14751 and I would like to thank @boppy for their work on this. Thanks to @gusted for the suggestion to adjust the `pbkdf2` hashing parameters. Close #14751 --------- Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: John Olheiser <john.olheiser@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	2023-02-19 15:35:20 +08:00