Summary: | Running of koha-* scripts should be logged | ||
---|---|---|---|
Product: | Koha | Reporter: | Michal Denar <black23> |
Component: | Command-line Utilities | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | josef.moravec, magnus, paul.poulain, rbit, robin |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 18081 |
Description
Michal Denar
2018-01-18 09:50:23 UTC
Hi Mike, can you give an example of a script to be logged? Hi Katrin, especially koha-dump. Because we need to know when Koha made backup and who run it. It contains personal data. If someone has the information to run koha-dump, wouldn't they also be able to get the dump using a tool like mysqldump? I agree, but Koha use CROn for automatic backup, logs make documented records about it. Direct export from db via CL tool or GUI tools should be logged manually. |