Bug 20024 - Backup files should be encrypted
Summary: Backup files should be encrypted
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
Depends on:
Blocks: 18081
  Show dependency treegraph
Reported: 2018-01-18 09:47 UTC by Michal Denar
Modified: 2018-07-10 08:49 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Note You need to log in before you can comment on or make changes to this bug.
Description Michal Denar 2018-01-18 09:47:36 UTC
File produced by koha-dump should be encrypted. It contents personal data. It's GDPR related stuff.
Comment 1 Jonathan Druart 2018-02-26 20:18:34 UTC
I do not think it is Koha's job to deal with that.
We could create a wiki page to explain people how to encrypt their dump if they do not know how to.

I am sure good sysadmins will use their own workflow and will not trust any --encrypt flags we are going to provide them.
Comment 2 Mirko Tietgen 2018-07-10 08:18:34 UTC
If there is an elegant way to do that, I'm not opposed to somebody providing a patch.

I don't see how this would work in an automated process. I guess there would be a passphrase and/or key file on the same server. Not to speak of the actual Koha installation and database running on that server. If somebody has access to the server, they don't need the backup files to access personal data?

Everything that happens afterwards (transferring backups to a different server etc.) is a custom workflow anyway, sysadmins could apply encryption during that process.
Comment 3 Michal Denar 2018-07-10 08:49:00 UTC
It can be option (parameter) in backup cronjob. I thing that really relevant for cases when backups are tranfering on on other servers/storage.