1
0
Fork 0
forgejo/models
Gusted 5f113bb611
[GITEA] Use restricted sanitizer for repository description
- Currently the repository description uses the same sanitizer as a
normal markdown document. This means that element such as heading and
images are allowed and can be abused.
- Create a minimal restricted sanitizer for the repository description,
which only allows what the postprocessor currently allows, which are
links and emojis.
- Added unit testing.
- Resolves https://codeberg.org/forgejo/forgejo/issues/1202
- Resolves https://codeberg.org/Codeberg/Community/issues/1122

(cherry picked from commit a8afa4cd18)
(cherry picked from commit 0238587c51)
(cherry picked from commit a8c7bbf728)
(cherry picked from commit 80e05a8245)
(cherry picked from commit f5af5050b3)
(cherry picked from commit 608f981e55)
(cherry picked from commit f40cff9263)
2023-10-30 14:37:04 +01:00
..
actions
activities
admin
asymkey
auth
avatars
db
dbfs
fixtures
forgejo/semver
forgejo_migrations
git
issues [GITEA] enable system users for comment.LoadPoster 2023-10-30 14:37:04 +01:00
migrations
organization
packages
perm
project
pull
repo [GITEA] Use restricted sanitizer for repository description 2023-10-30 14:37:04 +01:00
secret
shared/types
system
unit
unittest
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go