mirrors/forgejo

19,156 commits 22 branches 265 tags 223 MiB

Author	SHA1	Message	Date
TheFox0x7	072dd9f8bc	enable linter testifylint on v7 (#4572 ) Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4572 Co-authored-by: TheFox0x7 <thefox0x7@gmail.com> Co-committed-by: TheFox0x7 <thefox0x7@gmail.com>	2024-07-30 19:42:06 +00:00
Lunny Xiao	df1e7d0067	Use db.Find instead of writing methods for every object (#28084 ) For those simple objects, it's unnecessary to write the find and count methods again and again.	2023-11-24 03:49:41 +00:00
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

Author

SHA1

Message

Date

TheFox0x7

072dd9f8bc

enable linter testifylint on v7 (#4572 )

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4572
Co-authored-by: TheFox0x7 <thefox0x7@gmail.com>
Co-committed-by: TheFox0x7 <thefox0x7@gmail.com>

2024-07-30 19:42:06 +00:00

Lunny Xiao

df1e7d0067

Use db.Find instead of writing methods for every object (#28084 )

For those simple objects, it's unnecessary to write the find and count
methods again and again.

2023-11-24 03:49:41 +00:00

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

Renamed from models/auth/token_test.go (Browse further)

3 commits