From: Craig T. <ctr...@co...> - 2014-05-15 23:47:13
|
At 4:59 PM -0500 5/15/14, Ron Johnson wrote: >On 05/15/2014 04:44 PM, Michael Tiernan wrote: >> On 5/15/14 5:04 PM, Ron Johnson wrote: >>> How difficult would it be to integrate encryption into the backup process? >> I would be inclined to suggest developing a workflow using a TrueCrypt >> (http://www.truecrypt.org/) volume as the target for the backups. It >> seems to be smoother for most people's systems and until a more >> consistant process can be integrated into the application this would >> give people a secured target for their backups. > >What do you mean by "more consistent process"? > >AKAICT, TrueCrypt does not have *any* API, much less a Python modules, >whereas with the Python crypto module and API, the gzip "packets" are fed >directly into the encryption functions right there in the Gramps python code. I trust that this encryption would be an _optional_ feature. I, for one, like the idea that my backups are easily readable. The former software package I used for genealogy stopped working after a system upgrade and the fact that the backup was human-readable was my ace-in-the-hole. Craig |