Gusted c6a53c3172 [SECURITY] Rework long-term authentication ... - This is a 'front-port' of the already existing patch on v1.21 and v1.20, but applied on top of what Gitea has done to rework the LTA mechanism. Forgejo will stick with the reworked mechanism by the Forgejo Security team for the time being. The removal of legacy code (AES-GCM) has been left out. - 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 e3d6622a63) (cherry picked from commit fef1a6dac5) (cherry picked from commit b0c5165145) (cherry picked from commit 7ad51b9f8d) (cherry picked from commit 64f053f383) (cherry picked from commit f5e78e4c20) Conflicts: services/auth/auth_token_test.go https://codeberg.org/forgejo/forgejo/pulls/2069 (cherry picked from commit f69fc23d4b) (cherry picked from commit d955ab3ab0) (cherry picked from commit 9220088f90) (cherry picked from commit c73ac63696) (cherry picked from commit 747a176048) Conflicts: models/user/user.go routers/web/user/setting/account.go https://codeberg.org/forgejo/forgejo/pulls/2295		2024-02-05 15:06:15 +01:00
..
v1.go	[DB] forgejo migration v1: add blocked user migration	2024-02-05 14:44:33 +01:00
v2.go	[DB] forgejo migration v2: create the forgejo_sem_ver table	2024-02-05 14:44:33 +01:00
v3.go	[SECURITY] Rework long-term authentication	2024-02-05 15:06:15 +01:00