KN4CK3R c6c829fe3f Enhanced auth token / remember me (#27606) ... Closes #27455 > The mechanism responsible for long-term authentication (the 'remember me' cookie) uses a weak construction technique. It will hash the user's hashed password and the rands value; it will then call the secure cookie code, which will encrypt the user's name with the computed hash. If one were able to dump the database, they could extract those two values to rebuild that cookie and impersonate a user. That vulnerability exists from the date the dump was obtained until a user changed their password. > > To fix this security issue, the cookie could be created and verified using a different technique such as the one explained at https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies. The PR removes the now obsolete setting `COOKIE_USERNAME`.		2023-10-14 00:56:41 +00:00
..
e2e	Require MySQL 8.0, PostgreSQL 12, MSSQL 2012 (#27337)	2023-10-03 13:27:57 -04:00
fuzz
gitea-lfs-meta
gitea-repositories-meta	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00
integration	Enhanced auth token / remember me (#27606)	2023-10-14 00:56:41 +00:00
testdata/data/attachments/a/0	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00
mssql.ini.tmpl
mysql.ini.tmpl
pgsql.ini.tmpl
sqlite.ini.tmpl
test_utils.go	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00