3 commits

Author	SHA1	Message	Date
Loïc Dachary	e41c2241ba	[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 e1038faee8) (cherry picked from commit 5804aae16a) (cherry picked from commit c1d6665919)	2023-07-03 10:58:32 +02:00
wxiaoguang	b2359f3df6	Fix various bugs for "install" page (#23194) ... ## TLDR * Fix the broken page / broken image problem when click "Install" * Close #20089 * Fix the Password Hash Algorithm display problem for #22942 * Close #23183 * Close #23184 ## Details ### The broken page / broken image problem when click "Install" (Redirect failed after install gitea #23184) Before: when click "install", all new requests will fail, because the server has been restarted. Users just see a broken page with broken images, sometimes the server is not ready but the user would have been redirect to "/user/login" page, then the users see a new broken page (connection refused or something wrong ...) After: only check InstallLock=true for necessary handlers, and sleep for a while before restarting the server, then the browser has enough time to load the "post-install" page. And there is a script to check whether "/user/login" is ready, the user will only be redirected to the login page when the server is ready. ### During new instance setup make 'Gitea Base URL' filled from window.location.origin #20089 If the "app_url" input contains `localhost` (the default value from config), use current window's location href as the `app_url` (aka ROOT_URL) ### Fix the Password Hash Algorithm display problem for "Provide the ability to set password hash algorithm parameters #22942" Before: the UI shows `pbkdf2$50000$50` <details>  </details> After: the UI shows `pbkdf2` <details>  </details> ### GET data: net::ERR_INVALID_URL #23183 Cause by empty `data:` in `<link rel="manifest" href="data:{{.ManifestData}}">` --------- Co-authored-by: Jason Song <i@wolfogre.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io>	2023-03-04 10:12:02 +08: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