Gusted fe3b294f7b [GITEA] rework long-term authentication ... - The current architecture is inherently insecure, because you can construct the 'secret' cookie value with values that are available in the database. Thus provides zero protection when a database is dumped/leaked. - This patch implements a new architecture that's inspired from: [Paragonie Initiative](https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies). - Integration testing is added to ensure the new mechanism works. - Removes a setting, because it's not used anymore. (cherry picked from commit eff097448b1ebd2a280fcdd55d10b1f6081e9ccd) [GITEA] rework long-term authentication (squash) add migration Reminder: the migration is run via integration tests as explained in the commit "[DB] run all Forgejo migrations in integration tests" (cherry picked from commit 4accf7443c1c59b4d2e7787d6a6c602d725da403) (cherry picked from commit 99d06e344ebc3b50bafb2ac4473dd95f057d1ddc) (cherry picked from commit d8bc98a8f021d381bf72790ad246f923ac983ad4) (cherry picked from commit 6404845df9a63802fff4c5bd6cfe1e390076e7f0) (cherry picked from commit 72bdd4f3b9f6509d1ff3f10ecb12c621a932ed30) (cherry picked from commit 4b01bb0ce812b6c59414ff53fed728563d8bc9cc) (cherry picked from commit c26ac318162b2cad6ff1ae54e2d8f47a4e4fe7c2) (cherry picked from commit 8d2dab94a6) Conflicts: routers/web/auth/auth.go https://codeberg.org/forgejo/forgejo/issues/2158		2024-01-16 14:14:46 +00:00
..
v1_20	[GITEA] rework long-term authentication	2024-01-16 14:14:46 +00:00
migrate.go	[GITEA] rework long-term authentication	2024-01-16 14:14:46 +00:00