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?
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: