mirror of
https://github.com/HaschekSolutions/pictshare.git
synced 2026-04-26 23:45:52 +03:00
[GH-ISSUE #103] csv files in /data are accessible #78
Labels
No labels
Feature request
Feature request
bug
cant reproduce
enhancement
help wanted
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pictshare#78
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?
Originally created by @thomasdeurloo on GitHub (Nov 13, 2019).
Original GitHub issue: https://github.com/HaschekSolutions/pictshare/issues/103
Hi,
The folder "data" contains the sha1.csv which is containing the hashes. My folder is also containing a file called "uploads.csv" containing the logged uploads.. (I assume that the presence of this file is dependend on the parameter to log uploads). The csv files are publicly accessible to everyone. So if one knows that this system is used, he can request a full overview of the sha1 hashes, and in case of the logged uploads also the ipadresses.
To prevent this i created an .htacces file in the data folder containing
Which is blocking access to requests on csv files (as well as some others then uploaded content, just to be sure). Is this the best way of doing this?
@geek-at commented on GitHub (Nov 13, 2019):
Thanks, will add it to the nginx config
In the install example I use this as the default:
location ~ /(data|tmp|bin|content-controllers|inc|interfaces|storage-controllers|templates|tools) {
deny all;
return 404;
}