fe3b294f7b
- 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 |
||
|---|---|---|
| .. | ||
| avatar.go | ||
| badge.go | ||
| block.go | ||
| block_test.go | ||
| email_address.go | ||
| email_address_test.go | ||
| error.go | ||
| external_login_user.go | ||
| follow.go | ||
| follow_test.go | ||
| list.go | ||
| main_test.go | ||
| must_change_password.go | ||
| openid.go | ||
| openid_test.go | ||
| redirect.go | ||
| redirect_test.go | ||
| search.go | ||
| setting.go | ||
| setting_keys.go | ||
| setting_test.go | ||
| user.go | ||
| user_system.go | ||
| user_test.go | ||
| user_update.go | ||