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 eff097448b) [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 4accf7443c) (cherry picked from commit 99d06e344ebc3b50bafb2ac4473dd95f057d1ddc) (cherry picked from commit d8bc98a8f0) (cherry picked from commit 6404845df9) (cherry picked from commit 72bdd4f3b9) (cherry picked from commit 4b01bb0ce8) (cherry picked from commit c26ac31816) (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.go	[DB] forgejo migration v1: add blocked user migration	2023-11-13 12:33:48 +01:00
v2.go	[DB] forgejo migration v2: create the forgejo_sem_ver table	2023-11-13 12:33:48 +01:00
v3.go	[GITEA] rework long-term authentication	2024-01-16 14:14:46 +00:00