You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.
Having Tarsnap's key and cache directory in separate locations is ugly and confusing. Plus currently the cache directory is world-readable, and that's not good as it contains plaintext filenames.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6645536-better-tarsnap-configuration?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
That tells it to follow links when archiving instead of backing them up as links. Since this is backing up the entire system, that seems like the wrong thing to do... Anything that's pointed to by the link will be backed up, and upon restoration users probably want the link, not the file. So can the -L be removed or is there a reason for it?
/root/.tarsnap
, this includes thetarsnap.key
(Get rid of roles/tarsnap/files/decrypted_tarsnap.key #53) and thecache
directory/root/.tarsnaprc
should look like so:Having Tarsnap's key and cache directory in separate locations is ugly and confusing. Plus currently the cache directory is world-readable, and that's not good as it contains plaintext filenames.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6645536-better-tarsnap-configuration?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: