Summary: | koha-dump set permissions correct | ||
---|---|---|---|
Product: | Koha | Reporter: | Muri Nicanor <muri+koha> |
Component: | Packaging | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | robin |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: | patch for the koha-dump script |
Description
Muri Nicanor
2015-10-30 07:41:19 UTC
This deliberately isn't done as there's no reason to have the webserver able to read these files, generally. They contain server configs and database passwords, and so on so exposure of them should be kept very limited. The reason it's done for the database dump is that this permits users of hosted solutions to download their data at any time, but the $metadump file isn't really data. ah, oke, good to know. i use rsync to backup those files to another server (logging in using the webserver user) but i can find another way to get the backups or set the permission ; ) marking as resolved |