#1046 PR merged: Borg as back end, now accepts options for repository encryption (take 2)¶

Labels: enhancement, fixed / solved / done

gozora opened issue at 2016-10-21 12:53:¶

• borg as back end, now accepts options for repository encryption.
• prune now only affects archives with BORGBACKUP_ARCHIVE_PREFIX

gozora commented at 2016-10-21 13:00:¶

@jsmeix
Hope this one is better.

gozora commented at 2016-10-23 15:32:¶

Today I've discovered some useful Borg environment variables, that allows automatic launch of backup to encrypted repository (sending pass-phrases from ReaR to Borg in non-interactive session should not be a problem any longer).
I'll prepare pull request with this enhancement.

Btw. Do we have some preferred way of storing sensitive information like passwords?

V.

jsmeix commented at 2016-10-24 08:30:¶

@gozora
off the top of my head I don't know a preferred way of
storing sensitive information like passwords.
For example I implemented an optional password
for ftpfs, see https://github.com/rear/rear/issues/845
and https://github.com/rear/rear/pull/859
where the password either must be manually entered
several times during "rear mkbackup" and "rear recover"
see https://github.com/rear/rear/pull/859#issuecomment-223540169
but this way it is the secure method or alternatively
the password can be (optionally) specified as plain text
in the BACKUP_URL variable and then it is up to
the user how to protect that info in /etc/rear/local.conf

gozora commented at 2016-10-24 08:33:¶

@jsmeix,
Thanks, I'll check that!

---

[Export of Github issue for rear/rear.]