72bdd4f3b9
- 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_log.go | ||
api.go | ||
api_org.go | ||
api_test.go | ||
base.go | ||
captcha.go | ||
context.go | ||
context_cookie.go | ||
context_model.go | ||
context_request.go | ||
context_response.go | ||
context_template.go | ||
context_test.go | ||
csrf.go | ||
org.go | ||
package.go | ||
pagination.go | ||
permission.go | ||
private.go | ||
repo.go | ||
response.go | ||
utils.go | ||
xsrf.go | ||
xsrf_test.go |