forgejo/routers
Earl Warren 913e3b536e
fix(sec): permission check for project issue
- Do an access check when loading issues for a project board, currently
this is not done and exposes the title, labels and existence of a
private issue that the viewer of the project board may not have access
to.
- The number of issues cannot be calculated in a efficient manner
and stored in the database because their number may vary depending on
the visibility of the repositories participating in the project. The
previous implementation used the pre-calculated numbers stored in each
project, which did not reflect that potential variation.
- The code is derived from https://github.com/go-gitea/gitea/pull/22865

(cherry picked from commit 2193afaeb9954a5778f5a47aafd0e6fbbf48d000)
2025-02-05 22:05:22 +00:00
..
api fix: don't show private forks in forks list 2024-11-15 11:58:58 +01:00
common Use relative links for commits, mentions, and issues in markdown (#29427) 2024-03-20 08:46:28 +01:00
install Always load or generate oauth2 jwt secret (#30942) 2024-05-24 15:15:07 +02:00
private fix(sec): use constant time check for internal token 2024-10-28 06:17:16 +00:00
utils Improve user search display name (#29002) 2024-02-01 17:10:16 +00:00
web fix(sec): permission check for project issue 2025-02-05 22:05:22 +00:00
init.go s/Gitea/Forgejo in various log messages and comments 2024-04-22 14:41:17 +00:00