Prevent deep linking to media files #376
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core#376
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Files in
/media/are generally world-readable if their URL is known. We must prevent this, as it might contain sensitive data (like person photos).There are several options, of which we should chosoe a godo combination:
assigned to @debdolph
changed the description
mentioned in merge request !2109
There is a helpful library called
django-private-storage. It supports secure file storage with a permission checker, for files linked to a model (by configuring a function that checks permissions before serving the file; we could write a check function that checks permissions on theparent_objectthat is conveniently passed to this function).Maybe we can combine this with
django-sendfilein some way (and find out whetheruwsgisupports sendfile).changed the description
mentioned in merge request !2234
assigned to @nik and unassigned @debdolph
created merge request !2255 to address this issue
mentioned in merge request !2255
mentioned in commit
27ea9e895dmentioned in commit
c6b1d66b45