mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-11-24 02:36:10 +01:00
f5e78e4c20
- 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 |
||
---|---|---|
.. | ||
access_token.go | ||
access_token_scope.go | ||
access_token_scope_test.go | ||
access_token_test.go | ||
auth_token.go | ||
main_test.go | ||
oauth2.go | ||
oauth2_list.go | ||
oauth2_test.go | ||
session.go | ||
source.go | ||
source_test.go | ||
twofactor.go | ||
webauthn.go | ||
webauthn_test.go |