mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[PR #403] [CLOSED] docs: Do not expose media directory #585
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#585
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?
📋 Pull Request Information
Original PR: https://github.com/ciur/papermerge/pull/403
Author: @maxtruxa
Created: 7/19/2021
Status: ❌ Closed
Base:
master← Head:patch-1📝 Commits (1)
dd516e8docs: Do not expose media directory📊 Changes
1 file changed (+0 additions, -9 deletions)
View changed files
📝
docs/source/setup/server_configurations.rst(+0 -9)📄 Description
Description
Do not instruct users to expose the media directory unprotected. This is unsafe and as far as I can tell not necessary for normal operation of a Papermerge instance.
Serving the media directory straight through the webserver circumvents all access controls present in the web frontend and the REST API, leaving user data unprotected. Anyone who gets access to a valid document link can access that document.
If the user's webserver has directory listings enabled, this turns into a complete disaster, as all files are immediately discoverable and accessible.
My only guess is, that this might have been required in previous versions of Papermerge?
Type of change
How Has This Been Tested?
n/a
Checklist:
I have formatted this PR according to PEP8 rulesI have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationMy changes generate no new warningsI have added tests that prove my fix is effective or that my feature worksNew and existing unit tests pass locally with my changes🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.