Skip to content

Conversation

@gozora
Copy link
Member

@gozora gozora commented Oct 21, 2016

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

Prune now only affects archives with BORGBACKUP_ARCHIVE_PREFIX
…uring_borg

Conflicts:
	usr/share/rear/conf/default.conf
@gozora
Copy link
Member Author

gozora commented Oct 21, 2016

@jsmeix
Hope this one is better.

@gozora
Copy link
Member Author

gozora commented Oct 23, 2016

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 jsmeix merged commit 08bf274 into rear:master Oct 24, 2016
@jsmeix jsmeix added enhancement Adaptions and new features fixed / solved / done labels Oct 24, 2016
@jsmeix jsmeix added this to the Rear v1.20 milestone Oct 24, 2016
@jsmeix jsmeix self-assigned this Oct 24, 2016
@jsmeix
Copy link
Member

jsmeix commented Oct 24, 2016

@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 #845
and #859
where the password either must be manually entered
several times during "rear mkbackup" and "rear recover"
see #859 (comment)
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
Copy link
Member Author

gozora commented Oct 24, 2016

@jsmeix,
Thanks, I'll check that!

@gozora gozora deleted the securing_borg branch October 25, 2016 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Adaptions and new features fixed / solved / done

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants